draft-ietf-tsvwg-sctp-udp-encaps-02.txt   draft-ietf-tsvwg-sctp-udp-encaps-03.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: June 10, 2012 Adara Networks Expires: September 12, 2012 Adara Networks
December 8, 2011 March 11, 2012
UDP Encapsulation of SCTP Packets UDP Encapsulation of SCTP Packets
draft-ietf-tsvwg-sctp-udp-encaps-02.txt draft-ietf-tsvwg-sctp-udp-encaps-03.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 1, line 36 skipping to change at page 1, line 36
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 June 10, 2012. This Internet-Draft will expire on September 12, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 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
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. SCTP over UDP . . . . . . . . . . . . . . . . . . . . . . . . 4
4.1. Architectural Considerations . . . . . . . . . . . . . . . 4 4.1. Architectural Considerations . . . . . . . . . . . . . . . 4
4.2. Packet Format . . . . . . . . . . . . . . . . . . . . . . 4 4.2. Packet Format . . . . . . . . . . . . . . . . . . . . . . 4
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 . . . . . . . . . . . . . . . . . . . 6
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 . . . . . . . . . . . . 7
4.8. ECN considerations . . . . . . . . . . . . . . . . . . . . 7 4.8. ECN Considerations . . . . . . . . . . . . . . . . . . . . 7
5. Socket API Considerations . . . . . . . . . . . . . . . . . . 7 5. Socket API Considerations . . . . . . . . . . . . . . . . . . 7
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) . . . . . . . . . . . . . . 7 (SCTP_REMOTE_UDP_ENCAPS_PORT) . . . . . . . . . . . . . . 7
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
7. Security Considerations . . . . . . . . . . . . . . . . . . . 8 7. Security Considerations . . . . . . . . . . . . . . . . . . . 8
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
9.1. Normative References . . . . . . . . . . . . . . . . . . . 8 9.1. Normative References . . . . . . . . . . . . . . . . . . . 8
9.2. Informative References . . . . . . . . . . . . . . . . . . 9 9.2. Informative References . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10
skipping to change at page 4, line 5 skipping to change at page 4, line 5
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-land is controlling the A crucial point for implementing SCTP in user-land is controlling the
source address of outgoing packets. This is not an issue when using source address of outgoing packets. This is not an issue when using
all available addresses. However, this is not the case when also all available addresses. However, this is not the case 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 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]). It is
important to realize that for single homed associations it is only important to realize that for single homed associations it is only
necessary that no IP addresses are listed in the INIT and INIT-ACK necessary that no IP addresses are listed in the INIT and 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 with reconfiguration extension described in [RFC5061] MUST be used with
wildcard addresses in combination with [RFC4895]. wildcard addresses in combination with [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.
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
skipping to change at page 5, line 5 skipping to change at page 5, line 5
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.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Header | | IPv4 Header |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| UDP Header | | UDP Header |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCTP Common Header | | SCTP Common Header |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCTP Chunk #1 | | SCTP Chunk #1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCTP Chunk #n | | SCTP Chunk #n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1 Figure 1: An SCTP/UDP/IPv4 packet
The packet format for an encapsulated SCTP packet when using IPv6 as The packet format for an encapsulated SCTP packet when using IPv6 as
defined in [RFC2460] is shown in Figure 2. Please note the the defined in [RFC2460] is shown in Figure 2. Please note the the
number m of IPv6 extension headers can be 0. number m of IPv6 extension headers can be 0.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Base Header | | IPv6 Base Header |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Extension Header #1 | | IPv6 Extension Header #1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Extension Header #m | | IPv6 Extension Header #m |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| UDP Header | | UDP Header |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCTP Common Header | | SCTP Common Header |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCTP Chunk #1 | | SCTP Chunk #1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCTP Chunk #n | | SCTP Chunk #n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2 Figure 2: An SCTP/UDP/IPv6 packet
The UDP checksum MUST NOT be zero. The UDP checksum MUST NOT be zero.
4.3. Encapsulation Procedure 4.3. Encapsulation Procedure
When inserting the UDP header, the source port is the local UDP When inserting the UDP header, the source port is the local UDP
encapsulation port number of the SCTP stack, the destination port is encapsulation port number of the SCTP stack, the destination port is
the remote UDP encapsulation port number stored for the destination the remote UDP encapsulation port number stored for the destination
address the packet is sent to (see Section 4.1). address the packet is sent to (see Section 4.1).
skipping to change at page 6, line 29 skipping to change at page 6, line 29
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 the received SCTP Then a lookup is performed to find the association the received SCTP
packet belongs to. The UDP source port is stored as the packet belongs to. The UDP source port is stored as the
encapsulation port for the destination address the SCTP packet is encapsulation port for the destination address the SCTP packet is
received from (see Section 4.1). received from (see Section 4.1).
Please note that when a non-encapsulated SCTP packet is received, the Please note that when a non-encapsulated SCTP packet is received, the
encapsulation of outgoing packets belonging to the same association encapsulation of outgoing packets belonging to the same association
and the corresponding destination address is disabled. and the corresponding destination address is 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, it MUST be discarded silently. This means in SCTP association, it MUST be discarded silently. This means in
particular that the SCTP stack MUST NOT rely on receiving ICMP or particular that the SCTP stack MUST NOT rely on receiving ICMP or
ICMPv6 messages. There MAY be implementation constraints not ICMPv6 messages. There MAY be implementation constraints not
allowing to process received ICMP or ICMPv6 messages at all. allowing to process received ICMP or ICMPv6 messages at all.
skipping to change at page 7, line 5 skipping to change at page 7, line 5
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 4.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 4.5.
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 be translated MUST NOT be put into any SCTP packet. that might require translation MUST NOT be put into any SCTP packet.
This means that an SCTP association is setup singled homed and the This means that a multi homed SCTP association is setup initially as
protocol extension [RFC5061] in combination with [RFC4895] is used to a singled homed one and the protocol extension [RFC5061] in
add other addresses. Only wildcard addresses are put into the SCTP combination with [RFC4895] is used to add the other addresses. Only
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.
4.8. ECN considerations 4.8. ECN Considerations
During encapsulation and decapsulation the ECN bits MUST NOT be During encapsulation and decapsulation the ECN bits MUST NOT be
changed. changed.
5. Socket API Considerations 5. Socket API Considerations
This section describes how the socket API defined in This section describes how the socket API defined in [RFC6458] is
[I-D.ietf-tsvwg-sctpsocket] is extended to provide a way for the extended to provide a way for the application to control the UDP
application to control the UDP encapsulation. encapsulation.
Please note that this section is informational only. Please note that this section is informational only.
A socket API implementation based on [I-D.ietf-tsvwg-sctpsocket] is A socket API implementation based on [RFC6458] is extended by
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
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;
skipping to change at page 9, line 36 skipping to change at page 9, line 36
[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
[I-D.ietf-tsvwg-sctpsocket] [RFC6458] Stewart, R., Tuexen, M., Poon, K., Lei, P., and V.
Stewart, R., Tuexen, M., Poon, K., Lei, P., and V. Yasevich, "Sockets API Extensions for the Stream Control
Yasevich, "Sockets API Extensions for Stream Control Transmission Protocol (SCTP)", RFC 6458, December 2011.
Transmission Protocol (SCTP)",
draft-ietf-tsvwg-sctpsocket-32 (work in progress),
October 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-05 (work in progress), draft-ietf-behave-sctpnat-05 (work in progress),
June 2011. June 2011.
[I-D.ietf-tsvwg-natsupp] [I-D.ietf-tsvwg-natsupp]
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
Support", draft-ietf-tsvwg-natsupp-01 (work in progress), Support", draft-ietf-tsvwg-natsupp-01 (work in progress),
June 2011. June 2011.
Authors' Addresses Authors' Addresses
Michael Tuexen Michael Tuexen
Muenster University of Applied Sciences Muenster University of Applied Sciences
Stegerwaldstr. 39 Stegerwaldstrasse 39
48565 Steinfurt 48565 Steinfurt
DE DE
Email: tuexen@fh-muenster.de Email: tuexen@fh-muenster.de
Randall R. Stewart Randall R. Stewart
Adara Networks Adara Networks
Chapin, SC 29036 Chapin, SC 29036
USA US
Email: randall@lakerest.net Email: randall@lakerest.net
 End of changes. 23 change blocks. 
70 lines changed or deleted 67 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/