CLUE Protocol data channel
draft-ietf-clue-datachannel-18

Document Type Active Internet-Draft (clue WG)
Last updated 2019-08-20 (latest revision 2019-04-24)
Replaces draft-holmberg-clue-datachannel
Stream IETF
Intended RFC status Experimental
Formats plain text xml pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Paul Kyzivat
Shepherd write-up Show (last changed 2016-05-30)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Adam Roach
Send notices to "Paul Kyzivat" <pkyzivat@alum.mit.edu>
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state EDIT
CLUE Working Group                                           C. Holmberg
Internet-Draft                                                  Ericsson
Intended status: Experimental                             April 24, 2019
Expires: October 26, 2019

                       CLUE Protocol data channel
                     draft-ietf-clue-datachannel-18

Abstract

   This document defines how to use the WebRTC data channel mechanism to
   realize a data channel, referred to as a CLUE data channel, for
   transporting CLUE protocol messages between two CLUE entities.

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 October 26, 2019.

Copyright Notice

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

Holmberg                Expires October 26, 2019                [Page 1]
Internet-Draft              CLUE data channel                 April 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  CLUE data channel . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  SCTP Considerations . . . . . . . . . . . . . . . . . . .   4
       3.2.1.  General . . . . . . . . . . . . . . . . . . . . . . .   4
       3.2.2.  SCTP Payload Protocol Identifier (PPID) . . . . . . .   4
       3.2.3.  Reliability . . . . . . . . . . . . . . . . . . . . .   4
       3.2.4.  Order . . . . . . . . . . . . . . . . . . . . . . . .   5
       3.2.5.  Stream Reset  . . . . . . . . . . . . . . . . . . . .   5
       3.2.6.  SCTP Multihoming  . . . . . . . . . . . . . . . . . .   5
       3.2.7.  Closing the CLUE data channel . . . . . . . . . . . .   5
     3.3.  SDP Considerations  . . . . . . . . . . . . . . . . . . .   5
       3.3.1.  General . . . . . . . . . . . . . . . . . . . . . . .   5
       3.3.2.  SDP dcmap Attribute . . . . . . . . . . . . . . . . .   6
       3.3.3.  SDP dcsa Attribute  . . . . . . . . . . . . . . . . .   7
       3.3.4.  Example . . . . . . . . . . . . . . . . . . . . . . .   7
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  New WebRTC data channel Protocol Value  . . . . . . . . .   8
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   8
   7.  Change Log  . . . . . . . . . . . . . . . . . . . . . . . . .   8
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  12
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  13
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   This document defines how to use the WebRTC data channel mechanism
   [I-D.ietf-rtcweb-data-channel] to realize a data channel, referred to
   as a CLUE data channel, for transporting CLUE protocol
   [I-D.ietf-clue-protocol] messages between two CLUE entities.

   The document defines how to describe the SCTPoDTLS association
   [RFC8261] used to realize the CLUE data channel using the Session
   Description Protocol (SDP) [RFC4566], and defines usage of the SDP-
   based "SCTP over DTLS" data channel negotiation mechanism
   [I-D.ietf-mmusic-data-channel-sdpneg].  This includes SCTP
   considerations specific to a CLUE data channel, the SDP Media
   Description ("m=" line) values, and usage of SDP attributes specific
   to a CLUE data channel.

   Details and procedures associated with the CLUE protocol, and the SDP
   Offer/Answer [RFC3264] procedures for negotiating usage of a CLUE
   data channel, are outside the scope of this document.
Show full document text