draft-ietf-tsvwg-sctp-dtls-encaps-01.txt   draft-ietf-tsvwg-sctp-dtls-encaps-02.txt 
Network Working Group R. Jesup Network Working Group M. Tuexen
Internet-Draft WorldGate Communications Internet-Draft Muenster Univ. of Appl. Sciences
Intended status: Standards Track S. Loreto Intended status: Standards Track R. Stewart
Expires: January 16, 2014 Ericsson Expires: April 23, 2014 Adara Networks
R. Stewart R. Jesup
Adara Networks WorldGate Communications
M. Tuexen S. Loreto
Muenster Univ. of Appl. Sciences Ericsson
July 15, 2013 October 20, 2013
DTLS Encapsulation of SCTP Packets DTLS Encapsulation of SCTP Packets
draft-ietf-tsvwg-sctp-dtls-encaps-01.txt draft-ietf-tsvwg-sctp-dtls-encaps-02.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 document specifies how SCTP can be used on top of IPv4 or IPv6. This document specifies how SCTP can be used on top of
the Datagram Transport Layer Security (DTLS) protocol. the Datagram Transport Layer Security (DTLS) protocol.
Status of This Memo Status of This Memo
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 January 16, 2014. This Internet-Draft will expire on April 23, 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
skipping to change at page 3, line 43 skipping to change at page 3, line 43
extension defined in [RFC6520] MUST be used. extension defined in [RFC6520] MUST be used.
If path MTU discovery is performed by the SCTP layer and IPv4 is used If path MTU discovery is performed by the SCTP layer and IPv4 is used
as the network layer protocol, the DTLS implementation MUST allow the as the network layer protocol, the DTLS implementation MUST allow the
DTLS user to enforce that the corresponding IPv4 packet is sent with DTLS user to enforce that the corresponding IPv4 packet is sent with
the DF bit set. the DF bit set.
SCTP performs segmentation and reassembly based on the path MTU. SCTP performs segmentation and reassembly based on the path MTU.
Therefore the DTLS layer MUST NOT use any compression algorithm. Therefore the DTLS layer MUST NOT use any compression algorithm.
5. SCTP Considerations The DTLS MUST support sending messages larger than the current path
MTU. This might result in sending IP level fragmented messages.
5. SCTP Considerations
5.1. Base Protocol 5.1. Base Protocol
SCTP as specified in [RFC4960] is used. However, the following SCTP as specified in [RFC4960] is used. However, the following
restrictions are necessary to reflect that the lower layer is the restrictions are necessary to reflect that the lower layer is the
connection oriented protocol DTLS instead of the connection less connection oriented protocol DTLS instead of the connection less
protocol IPv4 and IPv6: protocol IPv4 and IPv6:
o A DTLS connection MUST be established before an SCTP association o A DTLS connection MUST be established before an SCTP association
can be set up. can be set up.
skipping to change at page 5, line 27 skipping to change at page 5, line 35
The authors wish to thank Gorry Fairhurst for his invaluable The authors wish to thank Gorry Fairhurst for his invaluable
comments. 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.
Conrad, "Stream Control Transmission Protocol (SCTP)
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.
[RFC4960] Stewart, R., "Stream Control Transmission Protocol", RFC [RFC4960] Stewart, R., "Stream Control Transmission Protocol", RFC
4960, September 2007. 4960, September 2007.
[RFC5061] Stewart, R., Xie, Q., Tuexen, M., Maruyama, S., and M.
Kozuka, "Stream Control Transmission Protocol (SCTP)
Dynamic Address Reconfiguration", RFC 5061, September
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
Transmission Protocol (SCTP) Stream Reconfiguration", RFC
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
[RFC3758] Stewart, R., Ramalho, M., Xie, Q., Tuexen, M., and P.
Conrad, "Stream Control Transmission Protocol (SCTP)
Partial Reliability Extension", RFC 3758, May 2004.
[RFC4895] Tuexen, M., Stewart, R., Lei, P., and E. Rescorla, [RFC4895] Tuexen, M., Stewart, R., Lei, P., and E. Rescorla,
"Authenticated Chunks for the Stream Control Transmission "Authenticated Chunks for the Stream Control Transmission
Protocol (SCTP)", RFC 4895, August 2007. Protocol (SCTP)", RFC 4895, August 2007.
[RFC5061] Stewart, R., Xie, Q., Tuexen, M., Maruyama, S., and M.
Kozuka, "Stream Control Transmission Protocol (SCTP)
Dynamic Address Reconfiguration", RFC 5061, September
2007.
[RFC6525] Stewart, R., Tuexen, M., and P. Lei, "Stream Control
Transmission Protocol (SCTP) Stream Reconfiguration", RFC
6525, February 2012.
[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-06 (work based Applications", draft-ietf-rtcweb-overview-08 (work
in progress), February 2013. in progress), September 2013.
[I-D.ietf-rtcweb-data-channel] [I-D.ietf-rtcweb-data-channel]
Jesup, R., Loreto, S., and M. Tuexen, "RTCWeb Data Jesup, R., Loreto, S., and M. Tuexen, "RTCWeb Data
Channels", draft-ietf-rtcweb-data-channel-04 (work in Channels", draft-ietf-rtcweb-data-channel-05 (work in
progress), February 2013. progress), July 2013.
[I-D.stewart-tsvwg-sctp-ndata]
Stewart, R., Tuexen, M., Loreto, S., and R. Seggelmann, "A
New Data Chunk for Stream Control Transmission Protocol",
draft-stewart-tsvwg-sctp-ndata-02 (work in progress), July
2013.
Authors' Addresses Authors' Addresses
Michael Tuexen
Muenster University of Applied Sciences
Stegerwaldstrasse 39
48565 Steinfurt
DE
Email: tuexen@fh-muenster.de
Randall R. Stewart
Adara Networks
Chapin, SC 29036
US
Email: randall@lakerest.net
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
Email: randell_ietf@jesup.org Email: randell_ietf@jesup.org
Salvatore Loreto Salvatore Loreto
Ericsson Ericsson
Hirsalantie 11 Hirsalantie 11
Jorvas 02420 Jorvas 02420
FI FI
Email: Salvatore.Loreto@ericsson.com Email: Salvatore.Loreto@ericsson.com
Randall R. Stewart
Adara Networks
Chapin, SC 29036
US
Email: randall@lakerest.net
Michael Tuexen
Muenster University of Applied Sciences
Stegerwaldstrasse 39
48565 Steinfurt
DE
Email: tuexen@fh-muenster.de
 End of changes. 14 change blocks. 
34 lines changed or deleted 51 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/