Network Working Group M. Petit-Huguenin
Internet-Draft Impedance Mismatch
Intended status: Standards Track February 17, 2013
Expires: August 21, 2013

SCTP Overlay link for REsource LOcation And Discovery (RELOAD)
draft-petithuguenin-p2psip-reload-sctp-00

Abstract

This document defines two new Overlay Link protocols to be used with REsource LOcation And Discovery (RELOAD), both using SCTP. The Overlay Link protocol DTLS-SCTP-NO-ICE uses DTLS on top of native SCTP for overlays that do not require the use of ICE. The Overlay Link protocol DTLS-SCTP-UDP uses DTLS on top of an UDP encapsulation of SCTP for overlays that require the use of ICE.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on August 21, 2013.

Copyright Notice

Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

This document may not be modified, and derivative works of it may not be created, except to format it for publication as an RFC or to translate it into languages other than English.


Table of Contents

1. Introduction

RELOAD [I-D.ietf-p2psip-base] defines 3 Overlay Link protocols, DTLS-UDP-SR, TLS-TCP-FH-NO-ICE and DTLS-UDP-SR-NO-ICE but none of them prevents Head of Line (HoL) blocking. DTLS for SCTP [RFC6083], is a good candidate as Overlay Link protocol, but because most NATs cannot handle SCTP [RFC4960], it can only been used with overlays that are known to not have nodes behind a NAT. For overlays that may have nodes behind a NAT, a UDP encapsulation of SCTP [I-D.ietf-tsvwg-sctp-udp-encaps] is used in place of the native SCTP, so it can traverses NAT Additionnaly using a UDP encapsulation does not require to define how using SCTP in ICE.

2. Terminology

The key words "MUST" and "MUST NOT" in this document are to be interpreted as described in [RFC2119].

3. DTLS-SCTP-NO-ICE Overlay Link Protocol

This overlay link protocol consists of DTLS over SCTP, as specified in [RFC6083]. The RELOAD messages MUST be sent on a stream other than 0 (which is reserved for the DTLS ChangeCipherSpec, Alert and Handshake protocols), with unlimited reliability but without the ordered delivery feature.

The Framing Header or the Simple Reliability protocols described in RELOAD MUST NOT be used.

4. DTLS-SCTP-UDP Overlay Link Protocol

This overlay link protocol consists of DTLS over an UDP encapsulation of SCTP, as specified in [RFC6083] and [I-D.ietf-tsvwg-sctp-udp-encaps]. The RELOAD messages MUST be sent on a stream other than 0 (which is reserved for the DTLS ChangeCipherSpec, Alert and Handshake protocols), with unlimited reliability but without the ordered delivery feature.

The Framing Header or the Simple Reliability protocols described in RELOAD MUST NOT be used.

5. Security Considerations

TBD.

6. IANA Considerations

If this document is accepted as a standard track document this section will request that IANA assign codes for the DTLS-SCTP-NO-ICE and DTLS-SCTP-UDP overlay protocols. Until this is done, implementions should use code 5 (reserved for experimentations as EXP-LINK). Using the same code is not an issue in this case as ICE and NO-ICE Overlays Protocols cannot be be simultaneously used in the same overlay.

[[Do we need to also assign a PPID?]]

7. Normative References

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4960] Stewart, R., "Stream Control Transmission Protocol", RFC 4960, September 2007.
[RFC4960] Stewart, R., "Stream Control Transmission Protocol", RFC 4960, September 2007.
[RFC6083] Tuexen, M., Seggelmann, R. and E. Rescorla, "Datagram Transport Layer Security (DTLS) for Stream Control Transmission Protocol (SCTP)", RFC 6083, January 2011.
[RFC6083] Tuexen, M., Seggelmann, R. and E. Rescorla, "Datagram Transport Layer Security (DTLS) for Stream Control Transmission Protocol (SCTP)", RFC 6083, January 2011.
[I-D.ietf-p2psip-base] Jennings, C., Lowekamp, B., Rescorla, E., Baset, S. and H. Schulzrinne, "REsource LOcation And Discovery (RELOAD) Base Protocol", Internet-Draft draft-ietf-p2psip-base-25, February 2013.
[I-D.ietf-p2psip-base] Jennings, C., Lowekamp, B., Rescorla, E., Baset, S. and H. Schulzrinne, "REsource LOcation And Discovery (RELOAD) Base Protocol", Internet-Draft draft-ietf-p2psip-base-24, January 2013.
[I-D.ietf-tsvwg-sctp-udp-encaps] Tuexen, M. and R. Stewart, "UDP Encapsulation of SCTP Packets for End-Host to End-Host Communication", Internet-Draft draft-ietf-tsvwg-sctp-udp-encaps-10, February 2013.
[I-D.ietf-tsvwg-sctp-udp-encaps] Tuexen, M. and R. Stewart, "UDP Encapsulation of SCTP Packets", Internet-Draft draft-ietf-tsvwg-sctp-udp-encaps-09, January 2013.

Author's Address

Marc Petit-Huguenin Impedance Mismatch EMail: petithug@acm.org