1
0
mirror of https://github.com/becarpenter/book6.git synced 2024-05-07 02:54:53 +00:00

47 lines
2.0 KiB
Markdown
Raw Normal View History

## Transport protocols
2023-07-19 14:49:00 +12:00
Applications can readily be updated to work in dual stack mode, because
the transport layer is very little affected by IPv6. Therefore, IPv6
supports all the common transport protocols:
2022-11-19 16:36:53 +13:00
2023-07-19 14:49:00 +12:00
- UDP. There is no separate specification for UDP over IPv6;
[RFC768](https://www.rfc-editor.org/info/rfc768) still applies!
However, the UDP checksum is mandatory for IPv6 (since the IPv6 header
itself has no checksum), except as allowed by
[RFC6936](https://www.rfc-editor.org/info/rfc6936).
2022-11-19 16:36:53 +13:00
2023-07-19 14:49:00 +12:00
- UDP-lite \[[RFC3828](https://www.rfc-editor.org/info/rfc3828)\] also
supports IPv6. There is interesting background on UDP and UDP-lite in
[RFC8304](https://www.rfc-editor.org/info/rfc8304).
2022-11-19 16:36:53 +13:00
2023-07-19 14:49:00 +12:00
- TCP. IPv6 support is fully integrated in the latest TCP standard
\[[STD7](https://www.rfc-editor.org/info/std7)\].
2022-11-19 16:36:53 +13:00
2023-07-19 14:49:00 +12:00
- RTP fully supports IPv6
\[[RFC3550](https://www.rfc-editor.org/info/rfc3550)\].
2022-11-19 16:36:53 +13:00
2023-07-19 14:49:00 +12:00
- QUIC fully supports IPv6
\[[RFC9000](https://www.rfc-editor.org/info/rfc9000)\].
2022-11-19 16:36:53 +13:00
2023-07-19 14:49:00 +12:00
- SCTP fully supports IPv6
\[[RFC4960](https://www.rfc-editor.org/info/rfc4960)\].
2022-11-19 16:36:53 +13:00
2023-07-19 14:49:00 +12:00
- MPTCP fully supports IPv6
\[[RFC8684](https://www.rfc-editor.org/info/rfc8684)\].
2022-11-19 16:36:53 +13:00
2023-07-19 14:49:00 +12:00
Also, the secure transports TLS, DTLS and SSH all work normally with
IPv6. So does SIP (Session Initiation Protocol
\[[RFC3261](https://www.rfc-editor.org/info/rfc3261)\]), which does not
require NAT traversal support (STUN) in the case of IPv6.
2022-11-19 16:36:53 +13:00
2023-07-19 14:49:00 +12:00
All quality of service and congestion control considerations should be
approximately the same for IPv4 and IPv6. This is why
[RFC2474](https://www.rfc-editor.org/info/rfc2474) defined
differentiated services identically for both versions of IP, and the
same applies to ECN (Explicit Congestion Notification
\[[RFC3168](https://www.rfc-editor.org/info/rfc3168)\]).
<!-- Link lines generated automatically; do not delete -->
2023-07-19 14:49:00 +12:00
2022-11-19 16:36:53 +13:00
### [<ins>Previous</ins>](Routing.md) [<ins>Next</ins>](Extension%20headers%20and%20options.md) [<ins>Chapter Contents</ins>](2.%20IPv6%20Basic%20Technology.md)