draft-ietf-tsvwg-sctp-dtls-encaps-00.txt   draft-ietf-tsvwg-sctp-dtls-encaps-01.txt 
Network Working Group R. Jesup Network Working Group R. Jesup
Internet-Draft WorldGate Communications Internet-Draft WorldGate Communications
Intended status: Standards Track S. Loreto Intended status: Standards Track S. Loreto
Expires: August 20, 2013 Ericsson Expires: January 16, 2014 Ericsson
R. Stewart R. Stewart
Adara Networks Adara Networks
M. Tuexen M. Tuexen
Muenster Univ. of Appl. Sciences Muenster Univ. of Appl. Sciences
February 16, 2013 July 15, 2013
DTLS Encapsulation of SCTP Packets for RTCWEB DTLS Encapsulation of SCTP Packets
draft-ietf-tsvwg-sctp-dtls-encaps-00.txt draft-ietf-tsvwg-sctp-dtls-encaps-01.txt
Abstract Abstract
The Stream Control Transmission Protocol (SCTP) is a transport The Stream Control Transmission Protocol (SCTP) is a transport
protocol originally defined to run on top of the network protocols protocol originally defined to run on top of the network protocols
IPv4 or IPv6. This memo document specifies how SCTP can be used on IPv4 or IPv6. This document specifies how SCTP can be used on top of
top of the Datagram Transport Layer Security (DTLS) protocol. SCTP the Datagram Transport Layer Security (DTLS) protocol.
over DTLS is used by the RTCWeb protocol suite for transporting non-
media data between browsers.
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 August 20, 2013. This Internet-Draft will expire on January 16, 2014.
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
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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Encapsulation and Decapsulation Procedure . . . . . . . . . . . 3 3. Encapsulation and Decapsulation Procedure . . . . . . . . . . 3
4. DTLS Considerations . . . . . . . . . . . . . . . . . . . . . . 4 4. DTLS Considerations . . . . . . . . . . . . . . . . . . . . . 3
5. SCTP Considerations . . . . . . . . . . . . . . . . . . . . . . 4 5. SCTP Considerations . . . . . . . . . . . . . . . . . . . . . 3
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 7. Security Considerations . . . . . . . . . . . . . . . . . . . 5
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 6 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
9.1. Normative References . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
9.2. Informative References . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
1.1. Overview 1.1. Overview
The Stream Control Transmission Protocol (SCTP) as defined in The Stream Control Transmission Protocol (SCTP) as defined in
[RFC4960] is a transport protocol running on top of the network [RFC4960] is a transport protocol running on top of the network
protocols IPv4 or IPv6. This memo document specifies how SCTP can be protocols IPv4 or IPv6. This document specifies how SCTP is used on
used on top of the Datagram Transport Layer Security (DTLS) protocol. top of the Datagram Transport Layer Security (DTLS) protocol. This
SCTP over DTLS is used by the RTCWeb protocol suite (see encapsulation is used for example within the RTCWeb protocol suite
[I-D.ietf-rtcweb-overview] for an overview) for transporting non- (see [I-D.ietf-rtcweb-overview] for an overview) for transporting
media data between browsers. The architecture of this stack is non-media data between browsers. The architecture of this stack is
described in [I-D.jesup-rtcweb-data]. described in [I-D.ietf-rtcweb-data-channel].
1.2. Terminology 1.2. Terminology
This document uses the following terms: This document uses the following terms:
Association: An SCTP association. Association: An SCTP association.
Stream: A unidirectional stream of an SCTP association. It is Stream: A unidirectional stream of an SCTP association. It is
uniquely identified by a stream identifier. uniquely identified by a stream identifier.
skipping to change at page 5, line 13 skipping to change at page 4, line 26
performed by SCTP. performed by SCTP.
5.2. Padding Extension 5.2. Padding Extension
The padding extension defined in [RFC4820] MUST be supported and used The padding extension defined in [RFC4820] MUST be supported and used
for probe packets when performing path MTU discovery as specified in for probe packets when performing path MTU discovery as specified in
[RFC4821]. [RFC4821].
5.3. Dynamic Address Reconfiguration Extension 5.3. Dynamic Address Reconfiguration Extension
The SCTP implementation MUST support the Supported Extensions If the dynamic address reconfiguration extension defined in [RFC5061]
Parameter defined in [RFC5061] to signal the support of the SCTP is used, only wildcard addresses MUST be used in ASCONF chunks.
stream reset extension (see Section 5.6). The other functionality
described in [RFC5061] MUST NOT be used.
5.4. SCTP Authentication Extension 5.4. SCTP Authentication Extension
The SCTP authentication extension defined in [RFC4895] is not The SCTP authentication extension defined in [RFC4895] can be used
required. with DTLS encapsulation, but does not require any additional benefit.
5.5. Partial Reliability Extension 5.5. Partial Reliability Extension
The SCTP implementation MUST support the extension defined in Partial reliability as defined in [RFC3758] can be used in
[RFC3758]. combination with DTLS encapsulation. It is also possible to use
additional PR-SCTP policies.
The SCTP implementation SHOULD support the following PR-SCTP
policies:
o A user message is abandoned after a user specified lifetime.
o A user message is abandoned if the number of retransmissions
exceeds a user specified threshold.
5.6. Stream Reset Extension 5.6. Stream Reset Extension
The SCTP implementation MUST support the SCTP stream reset extension The SCTP stream reset extension defined in [RFC6525] can be used with
defined in [RFC6525]. It is used to reset streams and add streams DTLS encapsulation. It is used to reset streams and add streams
during the lifetime of the SCTP association. during the lifetime of the SCTP association.
5.7. Large User Message Extension 5.7. Interleaving of Large User Message
SCTP as defined in [RFC4960] does not support the multiplexing of SCTP as defined in [RFC4960] does not support the interleaving of
large user messages that need to be fragmented and reassembled by the large user messages that need to be fragmented and reassembled by the
SCTP layer. To overcome this limitation, the SCTP implementation SCTP layer. The protocol extension defined in
SHOULD support an extension, which has to be defined. [I-D.stewart-tsvwg-sctp-ndata] overcomes this limitation can can be
used with DTLS encapsulation.
5.8. Congestion Control
In addition to the TCP-like congestion control specified in
[RFC4960], other congestion control algorithms MAY be provided. For
example, it might be helpful to use a congestion control which does
not increase the queueing delay substantially (see [RFC6817] for an
example).
6. IANA Considerations 6. IANA Considerations
This document requires no actions from IANA. This document requires no actions from IANA.
7. Security Considerations 7. Security Considerations
This document does not add any additional security considerations in Security considerations for DTLS are specified in [RFC6347] and for
addition to the ones given in [RFC4960], [RFC3758], [RFC6525], and SCTP in [RFC4960], [RFC3758], and [RFC6525]. The combination of SCTP
[RFC6347]. and DTLS introduces no new security considerations.
8. Acknowledgments 8. Acknowledgments
The authors wish to thank XXX for their invaluable comments. The authors wish to thank Gorry Fairhurst for his invaluable
comments.
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3758] Stewart, R., Ramalho, M., Xie, Q., Tuexen, M., and P. [RFC3758] Stewart, R., Ramalho, M., Xie, Q., Tuexen, M., and P.
Conrad, "Stream Control Transmission Protocol (SCTP) Conrad, "Stream Control Transmission Protocol (SCTP)
Partial Reliability Extension", RFC 3758, May 2004. Partial Reliability Extension", RFC 3758, May 2004.
[RFC4820] Tuexen, M., Stewart, R., and P. Lei, "Padding Chunk and [RFC4820] Tuexen, M., Stewart, R., and P. Lei, "Padding Chunk and
Parameter for the Stream Control Transmission Protocol Parameter for the Stream Control Transmission Protocol
(SCTP)", RFC 4820, March 2007. (SCTP)", RFC 4820, March 2007.
[RFC4821] Mathis, M. and J. Heffner, "Packetization Layer Path MTU [RFC4821] Mathis, M. and J. Heffner, "Packetization Layer Path MTU
Discovery", RFC 4821, March 2007. Discovery", RFC 4821, March 2007.
[RFC4895] Tuexen, M., Stewart, R., Lei, P., and E. Rescorla, [RFC4960] Stewart, R., "Stream Control Transmission Protocol", RFC
"Authenticated Chunks for the Stream Control Transmission 4960, September 2007.
Protocol (SCTP)", RFC 4895, August 2007.
[RFC4960] Stewart, R., "Stream Control Transmission Protocol",
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
September 2007. 2007.
[RFC6347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer [RFC6347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer
Security Version 1.2", RFC 6347, January 2012. Security Version 1.2", RFC 6347, January 2012.
[RFC6520] Seggelmann, R., Tuexen, M., and M. Williams, "Transport [RFC6520] Seggelmann, R., Tuexen, M., and M. Williams, "Transport
Layer Security (TLS) and Datagram Transport Layer Security Layer Security (TLS) and Datagram Transport Layer Security
(DTLS) Heartbeat Extension", RFC 6520, February 2012. (DTLS) Heartbeat Extension", RFC 6520, February 2012.
[RFC6525] Stewart, R., Tuexen, M., and P. Lei, "Stream Control [RFC6525] Stewart, R., Tuexen, M., and P. Lei, "Stream Control
Transmission Protocol (SCTP) Stream Reconfiguration", Transmission Protocol (SCTP) Stream Reconfiguration", RFC
RFC 6525, February 2012. 6525, February 2012.
[I-D.stewart-tsvwg-sctp-ndata]
Stewart, R., Tuexen, M., and S. Loreto, "A New Data Chunk
for Stream Control Transmission Protocol", draft-stewart-
tsvwg-sctp-ndata-01 (work in progress), February 2013.
9.2. Informative References 9.2. Informative References
[RFC6817] Shalunov, S., Hazel, G., Iyengar, J., and M. Kuehlewind, [RFC4895] Tuexen, M., Stewart, R., Lei, P., and E. Rescorla,
"Low Extra Delay Background Transport (LEDBAT)", RFC 6817, "Authenticated Chunks for the Stream Control Transmission
December 2012. Protocol (SCTP)", RFC 4895, August 2007.
[I-D.ietf-rtcweb-overview] [I-D.ietf-rtcweb-overview]
Alvestrand, H., "Overview: Real Time Protocols for Brower- Alvestrand, H., "Overview: Real Time Protocols for Brower-
based Applications", draft-ietf-rtcweb-overview-05 (work based Applications", draft-ietf-rtcweb-overview-06 (work
in progress), December 2012. in progress), February 2013.
[I-D.jesup-rtcweb-data] [I-D.ietf-rtcweb-data-channel]
Jesup, R., Loreto, S., and M. Tuexen, "RTCWeb Datagram Jesup, R., Loreto, S., and M. Tuexen, "RTCWeb Data
Connection", draft-jesup-rtcweb-data-01 (work in Channels", draft-ietf-rtcweb-data-channel-04 (work in
progress), October 2011. progress), February 2013.
Authors' Addresses Authors' Addresses
Randell Jesup Randell Jesup
WorldGate Communications WorldGate Communications
3800 Horizon Blvd, Suite #103 3800 Horizon Blvd, Suite #103
Trevose, PA 19053-4947 Trevose, PA 19053-4947
US US
Phone: +1-215-354-5166 Phone: +1-215-354-5166
 End of changes. 24 change blocks. 
82 lines changed or deleted 63 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/