draft-ietf-tsvwg-sctp-udp-encaps-10.txt   draft-ietf-tsvwg-sctp-udp-encaps-11.txt 
Network Working Group M. Tuexen Network Working Group M. Tuexen
Internet-Draft Muenster Univ. of Appl. Sciences Internet-Draft Muenster Univ. of Appl. Sciences
Intended status: Standards Track R. Stewart Intended status: Standards Track R. Stewart
Expires: August 23, 2013 Adara Networks Expires: August 23, 2013 Adara Networks
February 19, 2013 February 19, 2013
UDP Encapsulation of SCTP Packets for End-Host to End-Host Communication UDP Encapsulation of SCTP Packets for End-Host to End-Host Communication
draft-ietf-tsvwg-sctp-udp-encaps-10.txt draft-ietf-tsvwg-sctp-udp-encaps-11.txt
Abstract Abstract
This document describes a simple method of encapsulating SCTP Packets This document describes a simple method of encapsulating SCTP Packets
into UDP packets and its limitations. This allows the usage of SCTP into UDP packets and its limitations. This allows the usage of SCTP
in networks with legacy NAT not supporting SCTP. It can also be used in networks with legacy NAT not supporting SCTP. It can also be used
to implement SCTP on hosts without directly accessing the IP-layer, to implement SCTP on hosts without directly accessing the IP-layer,
for example implementing it as part of the application without for example implementing it as part of the application without
requiring special privileges. requiring special privileges.
skipping to change at page 2, line 24 skipping to change at page 2, line 24
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Portable SCTP Implementations . . . . . . . . . . . . . . 3 3.1. Portable SCTP Implementations . . . . . . . . . . . . . . 3
3.2. Legacy NAT Traversal . . . . . . . . . . . . . . . . . . . 4 3.2. Legacy NAT Traversal . . . . . . . . . . . . . . . . . . . 4
4. SCTP over UDP . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Unilateral Self-Address Fixing (UNSAF) Considerations . . . . 4
4.1. Architectural Considerations . . . . . . . . . . . . . . . 4 5. SCTP over UDP . . . . . . . . . . . . . . . . . . . . . . . . 4
4.2. Packet Format . . . . . . . . . . . . . . . . . . . . . . 5 5.1. Architectural Considerations . . . . . . . . . . . . . . . 4
4.3. Encapsulation Procedure . . . . . . . . . . . . . . . . . 6 5.2. Packet Format . . . . . . . . . . . . . . . . . . . . . . 5
4.4. Decapsulation Procedure . . . . . . . . . . . . . . . . . 6 5.3. Encapsulation Procedure . . . . . . . . . . . . . . . . . 6
4.5. ICMP Considerations . . . . . . . . . . . . . . . . . . . 7 5.4. Decapsulation Procedure . . . . . . . . . . . . . . . . . 6
4.6. Path MTU Considerations . . . . . . . . . . . . . . . . . 7 5.5. ICMP Considerations . . . . . . . . . . . . . . . . . . . 7
4.7. Handling of Embedded IP-addresses . . . . . . . . . . . . 8 5.6. Path MTU Considerations . . . . . . . . . . . . . . . . . 7
4.8. ECN Considerations . . . . . . . . . . . . . . . . . . . . 8 5.7. Handling of Embedded IP-addresses . . . . . . . . . . . . 8
5. Socket API Considerations . . . . . . . . . . . . . . . . . . 8 5.8. ECN Considerations . . . . . . . . . . . . . . . . . . . . 8
5.1. Get or Set the Remote UDP Encapsulation Port Number 6. Socket API Considerations . . . . . . . . . . . . . . . . . . 8
6.1. Get or Set the Remote UDP Encapsulation Port Number
(SCTP_REMOTE_UDP_ENCAPS_PORT) . . . . . . . . . . . . . . 8 (SCTP_REMOTE_UDP_ENCAPS_PORT) . . . . . . . . . . . . . . 8
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 9 8. Security Considerations . . . . . . . . . . . . . . . . . . . 9
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
9.1. Normative References . . . . . . . . . . . . . . . . . . . 10 10.1. Normative References . . . . . . . . . . . . . . . . . . . 10
9.2. Informative References . . . . . . . . . . . . . . . . . . 11 10.2. Informative References . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
This document describes a simple method of encapsulating SCTP packets This document describes a simple method of encapsulating SCTP packets
into UDP packets. SCTP as defined in [RFC4960] runs directly over into UDP packets. SCTP as defined in [RFC4960] runs directly over
IPv4 or IPv6. There are two main reasons for encapsulating SCTP IPv4 or IPv6. There are two main reasons for encapsulating SCTP
packets: packets:
o Allow SCTP traffic to pass through legacy NATs, which do not o Allow SCTP traffic to pass through legacy NATs, which do not
skipping to change at page 4, line 6 skipping to change at page 4, line 6
Using UDP encapsulation makes it possible to provide an SCTP Using UDP encapsulation makes it possible to provide an SCTP
implementation as part of a user process which does not require any implementation as part of a user process which does not require any
special privileges. special privileges.
A crucial point for implementing SCTP in user space is that the A crucial point for implementing SCTP in user space is that the
source address of outgoing packets needs to be controlled. This is source address of outgoing packets needs to be controlled. This is
not an issue if the SCTP stack can use all addresses configured at not an issue if the SCTP stack can use all addresses configured at
the IP-layer as source addresses. However, it is an issue when also the IP-layer as source addresses. However, it is an issue when also
using the address management required for NAT traversal, described in using the address management required for NAT traversal, described in
Section 4.7. Section 5.7.
3.2. Legacy NAT Traversal 3.2. Legacy NAT Traversal
Using UDP encapsulation allows SCTP communication when traversing Using UDP encapsulation allows SCTP communication when traversing
legacy NATs (i.e those NATs not supporting SCTP as described in legacy NATs (i.e those NATs not supporting SCTP as described in
[I-D.ietf-behave-sctpnat] and [I-D.ietf-tsvwg-natsupp]). For single- [I-D.ietf-behave-sctpnat] and [I-D.ietf-tsvwg-natsupp]). For single-
homed associations IP addresses MUST NOT be listed in the INIT and homed associations IP addresses MUST NOT be listed in the INIT and
INIT-ACK chunks. To use multiple addresses, the dynamic address INIT-ACK chunks. To use multiple addresses, the dynamic address
reconfiguration extension described in [RFC5061] MUST be used only reconfiguration extension described in [RFC5061] MUST be used only
with wildcard addresses in the ASCONF chunks in combination with with wildcard addresses in the ASCONF chunks in combination with
[RFC4895]. [RFC4895].
For multi-homed SCTP association the address management as described For multi-homed SCTP association the address management as described
in Section 4.7 MUST be performed. in Section 5.7 MUST be performed.
SCTP sends periodic HEARTBEAT chunks on all idle paths. These can SCTP sends periodic HEARTBEAT chunks on all idle paths. These can
keep the NAT state alive. keep the NAT state alive.
4. SCTP over UDP 4. Unilateral Self-Address Fixing (UNSAF) Considerations
4.1. Architectural Considerations As [RFC3424] requires a limited scope, this document only covers SCTP
end-points dealing with legacy constraints as described in Section 3.
It doesn't cover generic tunneling end-points.
Obviously, the exit strategy is to use hosts supporting SCTP natively
and middleboxes supporting SCTP as specified in
[I-D.ietf-behave-sctpnat] and [I-D.ietf-tsvwg-natsupp]).
5. SCTP over UDP
5.1. Architectural Considerations
An SCTP implementation supporting UDP encapsulation MUST store a An SCTP implementation supporting UDP encapsulation MUST store a
remote UDP encapsulation port number per destination address for each remote UDP encapsulation port number per destination address for each
SCTP association. SCTP association.
Each SCTP stack uses a single local UDP encapsulation port number as Each SCTP stack uses a single local UDP encapsulation port number as
the destination port for all its incoming SCTP packets. UDP the destination port for all its incoming SCTP packets. UDP
encapsulated SCTP is communicated over the IANA-assigned UDP port encapsulated SCTP is communicated over the IANA-assigned UDP port
number 9899 (sctp-tunneling). However, implementations SHOULD allow number 9899 (sctp-tunneling). However, implementations SHOULD allow
other port numbers to be specified through APIs, as applications may other port numbers to be specified through APIs, as applications may
have the need to communicate over different port numbers. If there have the need to communicate over different port numbers. If there
is only a single SCTP implementation on a host (for example, a kernel is only a single SCTP implementation on a host (for example, a kernel
implementation being part of the operating system), using a single implementation being part of the operating system), using a single
UDP encapsulation port number per host can be advantageous (e.g., UDP encapsulation port number per host can be advantageous (e.g.,
this reduces the number of mappings in firewalls and NATs, among this reduces the number of mappings in firewalls and NATs, among
other things). Using a single UDP encapsulation port number per host other things). Using a single UDP encapsulation port number per host
is not possible if the SCTP stack is implemented as part of each is not possible if the SCTP stack is implemented as part of each
application, there are multiple applications, and some of the application, there are multiple applications, and some of the
applications want to use the same IP-address. applications want to use the same IP-address.
4.2. Packet Format 5.2. Packet Format
To encapsulate an SCTP packet, a UDP header as defined in [RFC0768] To encapsulate an SCTP packet, a UDP header as defined in [RFC0768]
is inserted between the IP header as defined in [RFC0791] and the is inserted between the IP header as defined in [RFC0791] and the
SCTP common header as defined in [RFC4960]. SCTP common header as defined in [RFC4960].
Figure 1 shows the packet format of an encapsulated SCTP packet when Figure 1 shows the packet format of an encapsulated SCTP packet when
IPv4 is used. IPv4 is used.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
skipping to change at page 6, line 29 skipping to change at page 6, line 29
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCTP Chunk #1 | | SCTP Chunk #1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCTP Chunk #n | | SCTP Chunk #n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: An SCTP/UDP/IPv6 packet Figure 2: An SCTP/UDP/IPv6 packet
4.3. Encapsulation Procedure 5.3. Encapsulation Procedure
Within the UDP header, the source port MUST be the local UDP Within the UDP header, the source port MUST be the local UDP
encapsulation port number of the SCTP stack, the destination port encapsulation port number of the SCTP stack, the destination port
MUST be the remote UDP encapsulation port number stored for the MUST be the remote UDP encapsulation port number stored for the
association and the destination address to which the packet is sent association and the destination address to which the packet is sent
(see Section 4.1). (see Section 5.1).
Because the SCTP packet is the UDP payload, the length of the UDP Because the SCTP packet is the UDP payload, the length of the UDP
packet MUST be the length of the SCTP packet plus the size of the UDP packet MUST be the length of the SCTP packet plus the size of the UDP
header. header.
For IPv4, the UDP checksum SHOULD be computed and the SCTP checksum For IPv4, the UDP checksum SHOULD be computed and the SCTP checksum
MUST be computed, whereas for IPv6, the UDP checksum and the SCTP MUST be computed, whereas for IPv6, the UDP checksum and the SCTP
checksum MUST be computed. checksum MUST be computed.
4.4. Decapsulation Procedure 5.4. Decapsulation Procedure
When an encapsulated packet is received, the UDP header is removed. When an encapsulated packet is received, the UDP header is removed.
Then the generic lookup is performed, as done by an SCTP stack Then the generic lookup is performed, as done by an SCTP stack
whenever a packet is received, to find the association for the whenever a packet is received, to find the association for the
received SCTP packet. After finding the SCTP association (which received SCTP packet. After finding the SCTP association (which
includes checking the verification tag), the UDP source port MUST be includes checking the verification tag), the UDP source port MUST be
stored as the encapsulation port for the destination address the SCTP stored as the encapsulation port for the destination address the SCTP
packet is received from (see Section 4.1). packet is received from (see Section 5.1).
When a non-encapsulated SCTP packet is received by the SCTP stack, When a non-encapsulated SCTP packet is received by the SCTP stack,
the encapsulation of outgoing packets belonging to the same the encapsulation of outgoing packets belonging to the same
association and the corresponding destination address MUST be association and the corresponding destination address MUST be
disabled. disabled.
4.5. ICMP Considerations 5.5. ICMP Considerations
When receiving ICMP or ICMPv6 response packets, there might not be When receiving ICMP or ICMPv6 response packets, there might not be
enough bytes in the payload to identify the SCTP association which enough bytes in the payload to identify the SCTP association which
the SCTP packet triggering the ICMP or ICMPv6 packet belongs to. If the SCTP packet triggering the ICMP or ICMPv6 packet belongs to. If
a received ICMP or ICMPv6 packet can not be related to a specific a received ICMP or ICMPv6 packet can not be related to a specific
SCTP association or the verification tag can't be verified, it MUST SCTP association or the verification tag can't be verified, it MUST
be discarded silently. This means in particular that the SCTP stack be discarded silently. This means in particular that the SCTP stack
MUST NOT rely on receiving ICMP or ICMPv6 messages. Implementation MUST NOT rely on receiving ICMP or ICMPv6 messages. Implementation
constraints could prevent processing received ICMP or ICMPv6 constraints could prevent processing received ICMP or ICMPv6
messages. messages.
skipping to change at page 7, line 36 skipping to change at page 7, line 36
1. ICMP messages with type 'Destination Unreachable' and code 'Port 1. ICMP messages with type 'Destination Unreachable' and code 'Port
Unreachable' SHOULD be treated as ICMP messages with type Unreachable' SHOULD be treated as ICMP messages with type
'Protocol Unreachable' and code 'Destination Port unreachable. 'Protocol Unreachable' and code 'Destination Port unreachable.
See [RFC0792] for more details. See [RFC0792] for more details.
2. ICMPv6 messages with type 'Destination Unreachable' and code 2. ICMPv6 messages with type 'Destination Unreachable' and code
'Port unreachable' SHOULD be treated as ICMPv6 messages with type 'Port unreachable' SHOULD be treated as ICMPv6 messages with type
'Parameter Problem' and code 'Unrecognized Next Header type 'Parameter Problem' and code 'Unrecognized Next Header type
encountered'. See [RFC4443] for more details. encountered'. See [RFC4443] for more details.
4.6. Path MTU Considerations 5.6. Path MTU Considerations
If an SCTP endpoint starts to encapsulate the packets of a path, it If an SCTP endpoint starts to encapsulate the packets of a path, it
MUST decrease the Path MTU of that path by the size of the UDP MUST decrease the Path MTU of that path by the size of the UDP
header. If it stops encapsulating them, the Path MTU SHOULD be header. If it stops encapsulating them, the Path MTU SHOULD be
increased by the size of the UDP header. increased by the size of the UDP header.
When performing Path MTU discovery as described in [RFC4820] and When performing Path MTU discovery as described in [RFC4820] and
[RFC4821] it MUST be taken into account that one cannot rely on the [RFC4821] it MUST be taken into account that one cannot rely on the
feedback provided by ICMP or ICMPv6 due to the limitation laid out in feedback provided by ICMP or ICMPv6 due to the limitation laid out in
Section 4.5. Section 5.5.
If the implementation does not allow control of the dont't fragment If the implementation does not allow control of the dont't fragment
(DF)-bit contained in the IPv4 header, then Path MTU discovery can't (DF)-bit contained in the IPv4 header, then Path MTU discovery can't
be used. In this case, an implementation specific value should be be used. In this case, an implementation specific value should be
used instead. used instead.
4.7. Handling of Embedded IP-addresses 5.7. Handling of Embedded IP-addresses
When using UDP encapsulation for legacy NAT traversal, IP addresses When using UDP encapsulation for legacy NAT traversal, IP addresses
that might require translation MUST NOT be put into any SCTP packet. that might require translation MUST NOT be put into any SCTP packet.
This means that a multi homed SCTP association is setup initially as This means that a multi homed SCTP association is setup initially as
a singled homed one and the protocol extension [RFC5061] in a singled homed one and the protocol extension [RFC5061] in
combination with [RFC4895] is used to add the other addresses. Only combination with [RFC4895] is used to add the other addresses. Only
wildcard addresses are put into the SCTP packet. wildcard addresses are put into the SCTP packet.
When addresses are changed during the lifetime of an association When addresses are changed during the lifetime of an association
[RFC5061] MUST be used with wildcard addresses only. If an SCTP end- [RFC5061] MUST be used with wildcard addresses only. If an SCTP end-
point receives an ABORT with the T-bit set, it MAY use this as an point receives an ABORT with the T-bit set, it MAY use this as an
indication that the addresses seen by the peer might have changed. indication that the addresses seen by the peer might have changed.
4.8. ECN Considerations 5.8. ECN Considerations
If the implementation supports the sending and receiving of the ECN If the implementation supports the sending and receiving of the ECN
bits for the IP protocols being used by an SCTP association, the ECN bits for the IP protocols being used by an SCTP association, the ECN
bits MUST NOT be changed during sending and receiving. bits MUST NOT be changed during sending and receiving.
5. Socket API Considerations 6. Socket API Considerations
This section describes how the socket API defined in [RFC6458] needs This section describes how the socket API defined in [RFC6458] needs
to be extended to provide a way for the application to control the to be extended to provide a way for the application to control the
UDP encapsulation. UDP encapsulation.
Please note that this section is informational only. Please note that this section is informational only.
A socket API implementation based on [RFC6458] is extended by A socket API implementation based on [RFC6458] is extended by
supporting one new read/write socket option. supporting one new read/write socket option.
5.1. Get or Set the Remote UDP Encapsulation Port Number 6.1. Get or Set the Remote UDP Encapsulation Port Number
(SCTP_REMOTE_UDP_ENCAPS_PORT) (SCTP_REMOTE_UDP_ENCAPS_PORT)
This socket option can be used to set and retrieve the UDP This socket option can be used to set and retrieve the UDP
encapsulation port number. This allows an endpoint to encapsulate encapsulation port number. This allows an endpoint to encapsulate
initial packets. initial packets.
struct sctp_udpencaps { struct sctp_udpencaps {
sctp_assoc_t sue_assoc_id; sctp_assoc_t sue_assoc_id;
struct sockaddr_storage sue_address; struct sockaddr_storage sue_address;
uint16_t sue_port; uint16_t sue_port;
skipping to change at page 9, line 16 skipping to change at page 9, line 16
in an association identifier or SCTP_FUTURE_ASSOC for this query. in an association identifier or SCTP_FUTURE_ASSOC for this query.
It is an error to use SCTP_{CURRENT|ALL}_ASSOC in sue_assoc_id. It is an error to use SCTP_{CURRENT|ALL}_ASSOC in sue_assoc_id.
sue_address: This specifies which address is of interest. If a sue_address: This specifies which address is of interest. If a
wildcard address is provided it applies only to future paths. wildcard address is provided it applies only to future paths.
sue_port: The UDP port number in network byte order used as the sue_port: The UDP port number in network byte order used as the
destination port number for UDP encapsulation. Providing a value destination port number for UDP encapsulation. Providing a value
of 0 disables UDP encapsulation. of 0 disables UDP encapsulation.
6. IANA Considerations 7. IANA Considerations
This document refers to the already assigned UDP port 9899 (sctp- This document refers to the already assigned UDP port 9899 (sctp-
tunneling). IANA is requested to update this assignment to refer to tunneling). IANA is requested to update this assignment to refer to
this document. As per [RFC6335] the Assignee should be [IESG] and this document. As per [RFC6335] the Assignee should be [IESG] and
the Contact should be [IETF_Chair]. the Contact should be [IETF_Chair].
Please note that this document does not cover TCP port 9899 (sctp- Please note that this document does not cover TCP port 9899 (sctp-
tunneling). tunneling).
7. Security Considerations 8. Security Considerations
Encapsulating SCTP into UDP does not add any additional security Encapsulating SCTP into UDP does not add any additional security
considerations to the ones given in [RFC4960] and [RFC5061]. considerations to the ones given in [RFC4960] and [RFC5061].
Firewalls inspecting SCTP packets must also be aware of the Firewalls inspecting SCTP packets must also be aware of the
encapsulation and apply corresponding rules to the encapsulated encapsulation and apply corresponding rules to the encapsulated
packets. packets.
An attacker might send a malicious UDP packet towards an SCTP end- An attacker might send a malicious UDP packet towards an SCTP end-
point to change the encapsulation port for a single remote address of point to change the encapsulation port for a single remote address of
a particular SCTP association. However, as specified in Section 4.4, a particular SCTP association. However, as specified in Section 5.4,
this requires the usage of one the two negotiated verification tags. this requires the usage of one the two negotiated verification tags.
This protects against blind attackers the same way as described in This protects against blind attackers the same way as described in
[RFC4960] for SCTP over IPv4 or IPv6. Non-blind attackers can affect [RFC4960] for SCTP over IPv4 or IPv6. Non-blind attackers can affect
SCTP association using the UDP encapsulation described in this SCTP association using the UDP encapsulation described in this
document in the same way as SCTP associations not using the UDP document in the same way as SCTP associations not using the UDP
encapsulation of SCTP described here. encapsulation of SCTP described here.
8. Acknowledgments 9. Acknowledgments
The authors wish to thank Stewart Bryant, Dave Crocker, Gorry The authors wish to thank Stewart Bryant, Dave Crocker, Gorry
Fairhurst, Tero Kivinen, Barry Leiba, Pete Resnick, Martin Fairhurst, Tero Kivinen, Barry Leiba, Pete Resnick, Martin
Stiemerling, Irene Ruengeler, and Dan Wing for their invaluable Stiemerling, Irene Ruengeler, and Dan Wing for their invaluable
comments. comments.
9. References 10. References
9.1. Normative References 10.1. Normative References
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
August 1980. August 1980.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
September 1981. September 1981.
[RFC0792] Postel, J., "Internet Control Message Protocol", STD 5, [RFC0792] Postel, J., "Internet Control Message Protocol", STD 5,
RFC 792, September 1981. RFC 792, September 1981.
skipping to change at page 11, line 5 skipping to change at page 11, line 5
Protocol (SCTP)", RFC 4895, August 2007. Protocol (SCTP)", RFC 4895, August 2007.
[RFC4960] Stewart, R., "Stream Control Transmission Protocol", [RFC4960] Stewart, R., "Stream Control Transmission Protocol",
RFC 4960, September 2007. RFC 4960, September 2007.
[RFC5061] Stewart, R., Xie, Q., Tuexen, M., Maruyama, S., and M. [RFC5061] Stewart, R., Xie, Q., Tuexen, M., Maruyama, S., and M.
Kozuka, "Stream Control Transmission Protocol (SCTP) Kozuka, "Stream Control Transmission Protocol (SCTP)
Dynamic Address Reconfiguration", RFC 5061, Dynamic Address Reconfiguration", RFC 5061,
September 2007. September 2007.
9.2. Informative References 10.2. Informative References
[RFC3424] Daigle, L. and IAB, "IAB Considerations for UNilateral
Self-Address Fixing (UNSAF) Across Network Address
Translation", RFC 3424, November 2002.
[RFC6335] Cotton, M., Eggert, L., Touch, J., Westerlund, M., and S. [RFC6335] Cotton, M., Eggert, L., Touch, J., Westerlund, M., and S.
Cheshire, "Internet Assigned Numbers Authority (IANA) Cheshire, "Internet Assigned Numbers Authority (IANA)
Procedures for the Management of the Service Name and Procedures for the Management of the Service Name and
Transport Protocol Port Number Registry", BCP 165, Transport Protocol Port Number Registry", BCP 165,
RFC 6335, August 2011. RFC 6335, August 2011.
[RFC6458] Stewart, R., Tuexen, M., Poon, K., Lei, P., and V. [RFC6458] Stewart, R., Tuexen, M., Poon, K., Lei, P., and V.
Yasevich, "Sockets API Extensions for the Stream Control Yasevich, "Sockets API Extensions for the Stream Control
Transmission Protocol (SCTP)", RFC 6458, December 2011. Transmission Protocol (SCTP)", RFC 6458, December 2011.
 End of changes. 26 change blocks. 
41 lines changed or deleted 56 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/