CLUE Protocol Data Channel
draft-holmberg-clue-datachannel-00

Abstract

This document specifies how the usage of the Stream Control Transmission Protocol (SCTP) on top of the Datagram Transport Layer Security (DTLS) protocol (SCTPoDTLS) for transporting CLUE protocol messages between CLUE entities.

The document describes the SCTP considerations for CLUE, and the SDP Offer/Answer procedures for negotiating a SCTPoDTLS connection for CLUE.

Details and procedures associated with the CLUE protocol are outside the scope of this document.

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 05, 2014.

Copyright Notice

Copyright (c) 2014 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.

Table of Contents

• 1. Introduction
• 2. Conventions
• 3. SCTPoDTLS
• 3.1. General
• 3.2. SCTP Considerations
• 3.2.1. SCTP Streams
• 3.2.2. SCTP Payload Protocol Identifier (PPID)
• 3.2.3. Reliability
• 3.2.4. Order
• 3.2.5. SCTP Multihoming
• 4. SDP Offer/Answer Procedures
• 5. Security Considerations
• 6. IANA Considerations
• 7. Acknowledgments
• 8. Change Log
• 9. Normative References
• Author's Address

1. Introduction

This document specifies how the usage of the Stream Control Transmission Protocol (SCTP) on top of the Datagram Transport Layer Security (DTLS) protocol (SCTPoDTLS) for transporting CLUE protocol messages between CLUE entities.

The document describes the SCTP considerations for CLUE, and the SDP Offer/Answer procedures for negotiating a SCTPoDTLS connection for CLUE.

Details and procedures associated with the CLUE protocol are outside the scope of this document.

2. Conventions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119 [RFC2119].

CLUE data channel refers to the SCTPoDTLS connection that is established between two CLUE entities in order to transport CLUE messages.

CLUE message refers to a CLUE protocol message that is sent over the CLUE data channel.

CLUE entity refers to a SIP User Agent (UA) device that supports the CLUE mechanism (including the CLUE protocol).

3. SCTPoDTLS

3.1. General

The CLUE data channel is implemented by using the Stream Control Transmission Protocol (SCTP) on top of the Datagram Transport Layer Security (DTLS) protocol [I-D.tuexen-tsvwg-sctp-dtls-encaps].

3.2. SCTP Considerations

3.2.1. SCTP Streams

CLUE entities MUST establish two uni-directional STCP streams between themselves, one for CLUE messages sent in each direction.

3.2.2. SCTP Payload Protocol Identifier (PPID)

CLUE entities MUST use a PPID value of 50 or 51, according to the procedures in [ref-to-rtcweb-data-channel].

3.2.3. Reliability

CLUE entities MUST use the reliable transport SCTP feature.

3.2.4. Order

CLUE entities MUST use the ordered delivery SCTP feature.

3.2.5. SCTP Multihoming

CLUE entities MUST NOT use SCTP multihoming.

NOTE: The SCTPoDTLS mechanism does not support SCTP multihoming.

4. SDP Offer/Answer Procedures

TBD

5. Security Considerations

TBD

6. IANA Considerations

[RFC EDITOR NOTE: Please replace RFC-XXXX with the RFC number of this document.]

7. Acknowledgments

TBD

8. Change Log

[RFC EDITOR NOTE: Please remove this section when publishing]

Changes from draft-holmberg-clue-datachannel-xx

• TBD

9. Normative References

Author's Address