Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 1
    What about IPv6?
    – curiousguy
    Commented Jul 18, 2012 at 1:40
  • 1
    What about IPv6? It's just IP. There interface of sending and receiving a packet remains the same. So, TCP can use the same function. OS can just replace the function pointer from IPv4 and IPv6 and it would still work. I am not sure what you are saying here ? Commented Jul 18, 2012 at 3:59
  • 3
    IPv6 and IPv4 are similar, with similar interfaces for upper layers, but certainly not the same protocol and not strictly functionally equivalent either.
    – curiousguy
    Commented Jul 18, 2012 at 4:10
  • 1
    You might as well pretend that UDP is the same protocol as IP, because they offer extremely similar interfaces to upper layers: set a local and a remote endpoint addresses, send and receive packets...
    – curiousguy
    Commented Jul 18, 2012 at 4:16
  • Yes but TCP over IPv6 is just another proof that IPv4 is not a required protocol for implementing TCP. You can as well implement TCP over a non-routing protocol, it just requires a lower layer that includes an input stream and an output stream; the lower layer does not even need to use datagrams: TCP over a bidirectional serial link or over a software I/O pipe does work as well. There are in fact many posibilities, widely used on the Internet, including TCP over HTTP or HTTPS and various VPN protocols.
    – verdy_p
    Commented Jan 12 at 5:34