Return to Answer

TCP4 or TCP6 procotols don't exist. They can be used as a shorthand to indicate respectively TCP with IPv4 and TCP with IPv6, but that's an abuse of language -- the protocol used is always TCP.

Due to the separation of layers in the ISO/OSI model, the TCP segment (level 4) is always the same whether it's accompanying a IPv4 or IPv6 packet (level 3).

The only thing that changes in the TCP segment is the Checksum field, calculated according to RFC 793 for IPv4 and RFC 2460 for IPv6, since the size of an IP address differs between the two versions of the protocol. (I am not sure whether the Options field is used differently too.) However, it's still the same ol' TCP.

And yes, ::ffff:127.0.0.1 represents an IPv4 address (loopback in this case) mapped to a IPv6 address.

TCP4 or TCP6 procotols don't exist. They can be used as a shorthand to indicate respectively TCP with IPv4 and TCP with IPv6, but that's an abuse of language -- the protocol used is always TCP.

Due to the separation of layers in the ISO/OSI model, the TCP segment (level 4) is always the same whether it's accompanying a IPv4 or IPv6 packet (level 3).

The only thing that changes in the TCP segment is the Checksum field, calculated according to RFC 793 for IPv4 and RFC 2460 for IPv6, since the size of an IP address differs between the two versions of the protocol. (I am not sure whether the Options field is used differently too.) However, it's still the same ol' TCP.

And yes, ::ffff:127.0.0.1 represents an IPv4 address (loopback in this case) mapped to a IPv6 address.

TCP4 or TCP6 procotols don't exist. They can be used as a shorthand to indicate respectively TCP with IPv4 and TCP with IPv6, but that's an abuse of language -- the protocol used is always TCP.

Due to the separation of layers in the ISO/OSI model, the TCP segment (level 4) is always the same whether it's accompanying a IPv4 or IPv6 packet (level 3).

The only thing that changes in the TCP segment is the Checksum field, calculated according to RFC 793 for IPv4 and [RFC 2460][2] for IPv6, since the size of an IP address differs between the two versions of the protocol. (I am not sure whether the Options field is used differently too.) However, it's still the same ol' TCP.

And yes, ::ffff:127.0.0.1 represents an IPv4 address (loopback in this case) mapped to a IPv6 address. [2]: https://tools.ietf.org/html/rfc2460

TCP4 or TCP6 procotols don't exist. They can be used as a shorthand to indicate respectively TCP with IPv4 and TCP with IPv6, but that's an abuse of language -- the protocol used is always TCP.

Due to the separation of layers in the ISO/OSI model, the TCP segment (level 4) is always the same whether it's accompanying a IPv4 or IPv6 packet (level 3).

The only thing that changes in the TCP segment is the Checksum field, calculated according to RFC 793 for IPv4 and RFC 2460 for IPv6, since the size of an IP address differs between the two versions of the protocol. (I am not sure whether the Options field is used differently too.) However, it's still the same ol' TCP.

And yes, ::ffff:127.0.0.1 represents an IPv4 address (loopback in this case) mapped to a IPv6 address.

TCP4 or TCP6 procotols don't exist. They can be used as a shorthand to indicate respectively TCP with IPv4 and TCP with IPv6, but that's an abuse of language -- the protocol used is always TCP.

Due to the separation of layers in the ISO/OSI model, the TCP segment (level 4) is always the same whether it's accompanying a IPv4 or IPv6 packet (level 3). The only thing that changes in the TCP segment is the checksum field, calculated according to RFC 793 for IPv4 and [RFC 2460][2] for IPv6, since the size of an IP address differs between the two versions of the protocol.

And yes, ::ffff:127.0.0.1 represents an IPv4 address (loopback in this case) mapped to a IPv6 address. [2]: https://tools.ietf.org/html/rfc2460

TCP4 or TCP6 procotols don't exist. They can be used as a shorthand to indicate respectively TCP with IPv4 and TCP with IPv6, but that's an abuse of language -- the protocol used is always TCP.

Due to the separation of layers in the ISO/OSI model, the TCP segment (level 4) is always the same whether it's accompanying a IPv4 or IPv6 packet (level 3).

The only thing that changes in the TCP segment is the Checksum field, calculated according to RFC 793 for IPv4 and [RFC 2460][2] for IPv6, since the size of an IP address differs between the two versions of the protocol. (I am not sure whether the Options field is used differently too.) However, it's still the same ol' TCP.

And yes, ::ffff:127.0.0.1 represents an IPv4 address (loopback in this case) mapped to a IPv6 address. [2]: https://tools.ietf.org/html/rfc2460