draft-ietf-tsvwg-sctp-udp-encaps-09.txt   draft-ietf-tsvwg-sctp-udp-encaps-10.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: July 26, 2013 Adara Networks Expires: August 23, 2013 Adara Networks
January 22, 2013 February 19, 2013
UDP Encapsulation of SCTP Packets UDP Encapsulation of SCTP Packets for End-Host to End-Host Communication
draft-ietf-tsvwg-sctp-udp-encaps-09.txt draft-ietf-tsvwg-sctp-udp-encaps-10.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.
Please note that this document does not provide all techniques
necessary for building a complete NAT-capable application using SCTP.
This document focuses on the functionality required within the SCTP
stack and making this available via an API. It does not cover
mechanism to determine whether UDP encapsulation is required to reach
the peer and, if UDP encapsulation is used, which remote UDP port
number can be used.
This document covers only end-hosts and not tunneling (egress or
ingress) end-points.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 26, 2013. This Internet-Draft will expire on August 23, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
skipping to change at page 2, line 16 skipping to change at page 2, line 26
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. SCTP over UDP . . . . . . . . . . . . . . . . . . . . . . . . 4
4.1. Architectural Considerations . . . . . . . . . . . . . . . 4 4.1. Architectural Considerations . . . . . . . . . . . . . . . 4
4.2. Packet Format . . . . . . . . . . . . . . . . . . . . . . 4 4.2. Packet Format . . . . . . . . . . . . . . . . . . . . . . 5
4.3. Encapsulation Procedure . . . . . . . . . . . . . . . . . 6 4.3. Encapsulation Procedure . . . . . . . . . . . . . . . . . 6
4.4. Decapsulation Procedure . . . . . . . . . . . . . . . . . 6 4.4. Decapsulation Procedure . . . . . . . . . . . . . . . . . 6
4.5. ICMP Considerations . . . . . . . . . . . . . . . . . . . 6 4.5. ICMP Considerations . . . . . . . . . . . . . . . . . . . 7
4.6. Path MTU Considerations . . . . . . . . . . . . . . . . . 7 4.6. Path MTU Considerations . . . . . . . . . . . . . . . . . 7
4.7. Handling of Embedded IP-addresses . . . . . . . . . . . . 7 4.7. Handling of Embedded IP-addresses . . . . . . . . . . . . 8
4.8. ECN Considerations . . . . . . . . . . . . . . . . . . . . 7 4.8. ECN Considerations . . . . . . . . . . . . . . . . . . . . 8
5. Socket API Considerations . . . . . . . . . . . . . . . . . . 7 5. Socket API Considerations . . . . . . . . . . . . . . . . . . 8
5.1. Get or Set the Remote UDP Encapsulation Port Number 5.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 . . . . . . . . . . . . . . . . . . . . . 8 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 8 7. Security Considerations . . . . . . . . . . . . . . . . . . . 9
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
9.1. Normative References . . . . . . . . . . . . . . . . . . . 9 9.1. Normative References . . . . . . . . . . . . . . . . . . . 10
9.2. Informative References . . . . . . . . . . . . . . . . . . 10 9.2. Informative References . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 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 legacy NATs, which do not provide o Allow SCTP traffic to pass through legacy NATs, which do not
native SCTP support as specified in [I-D.ietf-behave-sctpnat] and provide native SCTP support as specified in
[I-D.ietf-tsvwg-natsupp]. [I-D.ietf-behave-sctpnat] and [I-D.ietf-tsvwg-natsupp].
o Allow SCTP to be implemented on hosts which do not provide direct o Allow SCTP to be implemented on hosts which do not provide direct
access to the IP-layer. In particular, applications can use their access to the IP-layer. In particular, applications can use their
own SCTP implementation if the operating system does not provide own SCTP implementation if the operating system does not provide
one. one.
SCTP provides the necessary congestion control and reliability
service that UDP does not perform.
2. Conventions 2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. Use Cases 3. Use Cases
This section discusses two important use cases for encapsulating SCTP This section discusses two important use cases for encapsulating SCTP
into UDP. into UDP.
3.1. Portable SCTP Implementations 3.1. Portable SCTP Implementations
Some operating systems support SCTP natively. For other operating Some operating systems support SCTP natively. For other operating
systems implementations are available, but require special privileges systems implementations are available, but require special privileges
to install and/or use them. In some cases no kernel implementation to install and/or use them. In some cases no kernel implementation
might be available at all. When proving an SCTP implementation as might be available at all. When providing an SCTP implementation as
part of a user process, most operating systems require special part of a user process, most operating systems require special
privileges to access the IP layer directly. privileges to access the IP layer directly.
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 controlling A crucial point for implementing SCTP in user space is that the
the source address of outgoing packets. This is not an issue when source address of outgoing packets needs to be controlled. This is
using all available addresses. However, this is not the case when not an issue if the SCTP stack can use all addresses configured at
also using the address management required for NAT traversal the IP-layer as source addresses. However, it is an issue when also
described in Section 4.7. using the address management required for NAT traversal, described in
Section 4.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]). It is [I-D.ietf-behave-sctpnat] and [I-D.ietf-tsvwg-natsupp]). For single-
important to realize that for single homed associations it is only homed associations IP addresses MUST NOT be listed in the INIT and
necessary that no IP addresses are listed in the INIT and INIT-ACK INIT-ACK chunks. To use multiple addresses, the dynamic address
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 with with wildcard addresses in the ASCONF chunks in combination with
wildcard addresses 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 4.7 MUST be performed.
SCTP sends periodically HEARTBEAT chunks on all idle paths. These SCTP sends periodic HEARTBEAT chunks on all idle paths. These can
can be used to keep the NAT state alive. keep the NAT state alive.
4. SCTP over UDP 4. SCTP over UDP
4.1. Architectural Considerations 4.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. The IANA the destination port for all its incoming SCTP packets. UDP
assigned value of 9899 (sctp-tunneling) MAY be used as this port encapsulated SCTP is communicated over the IANA-assigned UDP port
number. If there is only a single SCTP implementation on a host (for number 9899 (sctp-tunneling). However, implementations SHOULD allow
example, a kernel implementation being part of the operating system), other port numbers to be specified through APIs, as applications may
using a single UDP encapsulation port number per host can be have the need to communicate over different port numbers. If there
advantageous (e.g., this reduces the number of mappings in firewalls is only a single SCTP implementation on a host (for example, a kernel
and NATs, among other things). Using a single UDP encapsulation port implementation being part of the operating system), using a single
number per host is not possible if the SCTP stack is implemented as UDP encapsulation port number per host can be advantageous (e.g.,
part of an application. this reduces the number of mappings in firewalls and NATs, among
other things). Using a single UDP encapsulation port number per host
is not possible if the SCTP stack is implemented as part of each
application, there are multiple applications, and some of the
applications want to use the same IP-address.
4.2. Packet Format 4.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.
skipping to change at page 6, line 7 skipping to change at page 6, line 31
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCTP Chunk #n | | SCTP Chunk #n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: An SCTP/UDP/IPv6 packet Figure 2: An SCTP/UDP/IPv6 packet
4.3. Encapsulation Procedure 4.3. Encapsulation Procedure
When inserting 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 4.1).
The length of the UDP packet MUST be the length of the SCTP packet Because the SCTP packet is the UDP payload, the length of the UDP
plus the size of the UDP header. packet MUST be the length of the SCTP packet plus the size of the UDP
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 4.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 a lookup is performed to find the association for the received Then the generic lookup is performed, as done by an SCTP stack
SCTP packet. After finding the SCTP association (which includes whenever a packet is received, to find the association for the
checking the verification tag), the UDP source port MUST be stored as received SCTP packet. After finding the SCTP association (which
the encapsulation port for the destination address the SCTP packet is includes checking the verification tag), the UDP source port MUST be
received from (see Section 4.1). stored as the encapsulation port for the destination address the SCTP
packet is received from (see Section 4.1).
Please note that when a non-encapsulated SCTP packet is received, the When a non-encapsulated SCTP packet is received by the SCTP stack,
encapsulation of outgoing packets belonging to the same association the encapsulation of outgoing packets belonging to the same
and the corresponding destination address MUST be disabled. association and the corresponding destination address MUST be
disabled.
4.5. ICMP Considerations 4.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
skipping to change at page 7, line 22 skipping to change at page 7, line 48
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 4.5.
If the implementation does not allow to control 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 4.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. [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
indication that the addresses seen by the peer might have changed.
4.8. ECN Considerations 4.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. In the other bits MUST NOT be changed during sending and receiving.
case, ECN MUST NOT be used for such an SCTP association.
5. Socket API Considerations 5. Socket API Considerations
This section describes how the socket API defined in [RFC6458] is This section describes how the socket API defined in [RFC6458] needs
extended to provide a way for the application to control the UDP to be extended to provide a way for the application to control the
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 5.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
skipping to change at page 8, line 37 skipping to change at page 9, line 18
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 6. IANA Considerations
This document does not require any actions from IANA. It refers to This document refers to the already assigned UDP port 9899 (sctp-
the already assigned UDP port 9899 (sctp-tunneling). tunneling). IANA is requested to update this assignment to refer to
this document. As per [RFC6335] the Assignee should be [IESG] and
the Contact should be [IETF_Chair].
Please note that this document does not cover TCP port 9899 (sctp-
tunneling).
7. Security Considerations 7. 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.
skipping to change at page 9, line 14 skipping to change at page 9, line 47
a particular SCTP association. However, as specified in Section 4.4, a particular SCTP association. However, as specified in Section 4.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 8. Acknowledgments
The authors wish to thank Gorry Fairhurst, Tero Kivinen, Martin The authors wish to thank Stewart Bryant, Dave Crocker, Gorry
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 9. References
9.1. Normative References 9.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.
skipping to change at page 10, line 16 skipping to change at page 11, line 7
[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 9.2. Informative References
[RFC6335] Cotton, M., Eggert, L., Touch, J., Westerlund, M., and S.
Cheshire, "Internet Assigned Numbers Authority (IANA)
Procedures for the Management of the Service Name and
Transport Protocol Port Number Registry", BCP 165,
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.
[I-D.ietf-behave-sctpnat] [I-D.ietf-behave-sctpnat]
Stewart, R., Tuexen, M., and I. Ruengeler, "Stream Control Stewart, R., Tuexen, M., and I. Ruengeler, "Stream Control
Transmission Protocol (SCTP) Network Address Translation", Transmission Protocol (SCTP) Network Address Translation",
draft-ietf-behave-sctpnat-07 (work in progress), draft-ietf-behave-sctpnat-07 (work in progress),
October 2012. October 2012.
 End of changes. 28 change blocks. 
64 lines changed or deleted 98 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/