CLUE Working Group C. Holmberg
Internet-Draft Ericsson
Intended status: Standards Track April 17, 2019
Expires: October 19, 2019

CLUE Protocol data channel


This document defines how to use the WebRTC data channel mechanism in order 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

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 19, 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 ( 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

This document defines how to use the WebRTC data channel mechanism [I-D.ietf-rtcweb-data-channel] in order 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.

NOTE: The usage of the Data Channel Establishment Protocol (DCEP) [I-D.ietf-rtcweb-data-protocol] for establishing a CLUE data channel is outside the scope of this document.

2. Conventions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

SCTPoDTLS association refers to an SCTP association carried over an DTLS connection [RFC8261].

WebRTC data channel refers to a pair of SCTP streams over a SCTPoDTLS association that is used to transport non-media data between two entities, as defined in [I-D.ietf-rtcweb-data-channel].

CLUE data channel refers to a WebRTC data channel [I-D.ietf-rtcweb-data-channel] realization, with a specific set of SCTP characteristics, with the purpose of transporting CLUE protocol [I-D.ietf-clue-protocol] messages between two CLUE entities.

CLUE entity refers to a SIP User Agent (UA) [RFC3261] that supports the CLUE data channel and the CLUE protocol.

CLUE session refers to a SIP session [RFC3261] between two SIP UAs, where a CLUE data channel, associated with the SIP session, has been established between the SIP UAs.

SCTP stream is defined in [RFC4960] as a unidirectional logical channel established from one to another associated SCTP endpoint, within which all user messages are delivered in sequence except for those submitted to the unordered delivery service.

SCTP identifier is defined in [RFC4960] as an unsigned integer, which identifies an SCTP stream.

3. CLUE data channel

3.1. General

This section describes the realization of a CLUE data channel, using the WebRTC data channel mechanism. This includes a set of SCTP characteristics specific to a CLUE data channel, the values of the "m=" line describing the SCTPoDTLS association associated with the WebRTC data channel, and the usage of the SDP-based "SCTP over DTLS" data channel negotiation mechanism for creating the CLUE data channel.

As described in [I-D.ietf-rtcweb-data-channel], the SCTP streams realizing a WebRTC data channel must be associated with the same SCTP association. In addition, both SCTP streams realizing the WebRTC data channel must use the same SCTP stream identifier value. These rules also apply to a CLUE data channel.

Within a given CLUE session, a CLUE entity MUST use a single CLUE data channel for transport of all CLUE messages towards its peer.

3.2. SCTP Considerations

3.2.1. General

As described in [I-D.ietf-rtcweb-data-channel], different SCTP options (e.g., regarding ordered delivery ), can be used for a data channel. This section describes the SCTP options used for a CLUE data channel. Section 3.3 describes how SCTP options are signaled using SDP.

NOTE: While SCTP allows SCTP options to be applied per SCTP message, [I-D.ietf-rtcweb-data-channel] mandates that, for a given data channel, the same SCTP options are applied to each SCTP message associated with that data channel.

3.2.2. SCTP Payload Protocol Identifier (PPID)

A CLUE entity MUST use the PPID value 51 when sending a CLUE message on a CLUE data channel.

NOTE: As described in [I-D.ietf-rtcweb-data-channel], the PPID value 51 indicates that the SCTP message contains data encoded in a UTF-8 format. The PPID value 51 does not indicate which application protocol the SCTP message is associated with, only the format in which the data is encoded.

3.2.3. Reliability

The usage of SCTP for the CLUE data channel ensures reliable transport of CLUE protocol [I-D.ietf-clue-protocol] messages.

[I-D.ietf-rtcweb-data-channel] requires the support of the partial reliability extension defined in [RFC3758] and the limited retransmission policy defined in [RFC7496]. A CLUE entity MUST NOT use these extensions, as messages are required to always be sent reliably. A CLUE entity MUST terminate the session if it detects that the peer entity uses any of the extensions.

3.2.4. Order

A CLUE entity MUST use the ordered delivery SCTP service, as described in [RFC4960], for the CLUE data channel.

3.2.5. Stream Reset

A CLUE entity MUST support the stream reset extension defined in [RFC6525].

As defined in [I-D.ietf-rtcweb-data-channel], the dynamic address reconfiguration extension ('Supported Extensions Parameter' parameter) defined in [RFC5061] must be used to signal the support of the stream reset extension defined in [RFC6525]. Other features of [RFC5061] MUST NOT be used for CLUE data channels.

3.2.6. SCTP Multihoming

SCTP multi-homing is not supported for SCTPoDTLS associations, and can therefore not be used for a CLUE data channel.

3.2.7. Closing the CLUE data channel

As described in [I-D.ietf-rtcweb-data-channel], in order to close a data channel, an entity sends an SCTP reset message [RFC6525] on its outgoing SCTP stream associated with the data channel. When the remote peer receives the reset message, it also sends (unless already sent) a reset message on its outgoing SCTP stream associated with the data channel. The SCTPoDTLS association, and other data channels established on the same association, are not affected by the SCTP reset messages.

3.3. SDP Considerations

3.3.1. General

This section defines how to construct the SDP Media Description ("m=" line) for describing the SCTPoDTLS association used to realize a CLUE data channel. The section also defines how to use the SDP-based "SCTP over DTLS" data channel negotiation mechanism [I-D.ietf-mmusic-data-channel-sdpneg] for establishing a CLUE data channel on the SCTPoDTLS association.

NOTE: Other protocols than SDP for negotiating usage of an SCTPoDTLS association for realizing a CLUE data channel are outside the scope of this specification.

[I-D.ietf-clue-signaling] describes the SDP Offer/Answer procedures for negotiating a CLUE session, including the CLUE controlled media streams and the CLUE data channel. SDP Media Description Fields

As defined in [I-D.ietf-mmusic-sctp-sdp], the field values of an "m=" line describing an SCTPoDTLS association are set as following:

SDP "proto" field values
media port proto fmt
"application" UDP port value "UDP/DTLS/SCTP" application usage
"application" TCP port value "TCP/DTLS/SCTP" application usage

CLUE entities SHOULD NOT transport the SCTPoDTLS association used to realize the CLUE data channel over TCP (using the "TCP/DTLS/SCTP" proto value), unless it is known that UDP/DTLS/SCTP will not work (for instance, when the Interactive Connectivity Establishment (ICE) mechanism [RFC8445] is used and the ICE procedures determine that TCP transport is required).

As defined in [I-D.ietf-mmusic-sctp-sdp], when the SCTPoDTLS association is used to realize a WebRTC data channel, the value of the application usage part is 'webrtc-datachannel'. SDP sctp-port Attribute

As defined in [I-D.ietf-mmusic-sctp-sdp], the SDP sctp-port attribute value is set to the SCTP port of the SCTPoDTLS association. A CLUE entity can choose any valid SCTP port value [I-D.ietf-mmusic-sctp-sdp].

3.3.2. SDP dcmap Attribute

The values of the SDP dcmap attribute [I-D.ietf-mmusic-data-channel-sdpneg], associated with the "m=" line describing the SCTPoDTLS association used to realize the WebRTC data channel, are set as following:

SDP dcmap attribute values
stream-id subprotocol label ordered max-retr max-time
Value of the SCTP stream used to realize the CLUE data channel "CLUE" Application specific "true" N/A N/A

NOTE: As CLUE entities are required to use ordered SCTP message delivery, with full reliability, according to the procedures in [I-D.ietf-mmusic-data-channel-sdpneg] the max-retr and max-time attribute parameters are not used when negotiating CLUE data channels.

3.3.3. SDP dcsa Attribute

The SDP dcsa attribute [I-D.ietf-mmusic-data-channel-sdpneg] is not used when establishing a CLUE data channel.

3.3.4. Example

The example in Figure 1 shows an SDP media description for a CLUE data channel. Examples of complete SDP examples can be found in [I-D.ietf-clue-signaling].

        m=application 54111 UDP/DTLS/SCTP webrtc-datachannel
        a=sctp-port: 5000
        a=dcmap:2 subprotocol="CLUE";ordered=true


Figure 1: SDP Media Description for a CLUE data channel

4. Security Considerations

This specification relies on the security properties of the WebRTC data channel described in [I-D.ietf-rtcweb-data-channel], including reliance on DTLS. Since CLUE sessions are established using SIP/SDP, protecting the data channel against message modification and recovery requires the use of SIP authentication and authorization mechanisms described in [RFC3261] for session establishment prior to establishing the data channel.

5. IANA Considerations

5.1. New WebRTC data channel Protocol Value

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

This document adds the 'CLUE' value to the "WebSocket Subprotocol Name Registry" as follows:

	Subprotocl Identifier:		CLUE
	Subprotocol Common Name:	CLUE
	Subprotocol Definition:		RFC-XXXX
    Reference:                  RFC-XXXX


6. Acknowledgments

Thanks to Paul Kyzivat, Christian Groves and Mark Duckworth for comments on the document.

7. Change Log

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

Changes from draft-ietf-clue-datachannel-15

Changes from draft-ietf-clue-datachannel-14

Changes from draft-ietf-clue-datachannel-13

Changes from draft-ietf-clue-datachannel-12

Changes from draft-ietf-clue-datachannel-11

Changes from draft-ietf-clue-datachannel-10

Changes from draft-ietf-clue-datachannel-09

Changes from draft-ietf-clue-datachannel-08

Changes from draft-ietf-clue-datachannel-07

Changes from draft-ietf-clue-datachannel-06

Changes from draft-ietf-clue-datachannel-05

Changes from draft-ietf-clue-datachannel-04

Changes from draft-ietf-clue-datachannel-03

Changes from draft-ietf-clue-datachannel-02

Changes from draft-ietf-clue-datachannel-01

Changes from draft-ietf-clue-datachannel-00

Changes from draft-holmberg-clue-datachannel-04

Changes from draft-holmberg-clue-datachannel-03

Changes from draft-holmberg-clue-datachannel-02

Changes from draft-holmberg-clue-datachannel-01

Changes from draft-holmberg-clue-datachannel-00

8. References

8.1. Normative References

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP: Session Initiation Protocol", RFC 3261, DOI 10.17487/RFC3261, June 2002.
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with Session Description Protocol (SDP)", RFC 3264, DOI 10.17487/RFC3264, June 2002.
[RFC4566] Handley, M., Jacobson, V. and C. Perkins, "SDP: Session Description Protocol", RFC 4566, DOI 10.17487/RFC4566, July 2006.
[RFC4960] Stewart, R., "Stream Control Transmission Protocol", RFC 4960, DOI 10.17487/RFC4960, September 2007.
[RFC5061] Stewart, R., Xie, Q., Tuexen, M., Maruyama, S. and M. Kozuka, "Stream Control Transmission Protocol (SCTP) Dynamic Address Reconfiguration", RFC 5061, DOI 10.17487/RFC5061, September 2007.
[RFC6525] Stewart, R., Tuexen, M. and P. Lei, "Stream Control Transmission Protocol (SCTP) Stream Reconfiguration", RFC 6525, DOI 10.17487/RFC6525, February 2012.
[RFC7496] Tuexen, M., Seggelmann, R., Stewart, R. and S. Loreto, "Additional Policies for the Partially Reliable Stream Control Transmission Protocol Extension", RFC 7496, DOI 10.17487/RFC7496, April 2015.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017.
[RFC8261] Tuexen, M., Stewart, R., Jesup, R. and S. Loreto, "Datagram Transport Layer Security (DTLS) Encapsulation of SCTP Packets", RFC 8261, DOI 10.17487/RFC8261, November 2017.
[I-D.ietf-mmusic-sctp-sdp] Holmberg, C., Loreto, S. and G. Camarillo, "Stream Control Transmission Protocol (SCTP)-Based Media Transport in the Session Description Protocol (SDP)", Internet-Draft draft-ietf-mmusic-sctp-sdp-26.txt, April 2017.
[I-D.ietf-rtcweb-data-channel] Jesup, R., Loreto, S. and M. Tuexen, "WebRTC data channels", Internet-Draft draft-ietf-rtcweb-data-channel-13.txt, January 2015.
[I-D.ietf-mmusic-data-channel-sdpneg] Drage, K., Makaraju, R., Stoetzer-Bradler, J., Ejzak, R. and J. Marcon, "SDP-based "SCTP over DTLS" data channel negotiation", Internet-Draft draft-ietf-mmusic-data-channel-sdpneg-25.txt, March 2019.

8.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, DOI 10.17487/RFC3758, May 2004.
[RFC8445] Keranen, A., Holmberg, C. and J. Rosenberg, "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal", RFC 8445, DOI 10.17487/RFC8445, July 2018.
[I-D.ietf-rtcweb-data-protocol] Jesup, R., Loreto, S. and M. Tuexen, "WebRTC data channel Establishment Protocol", Internet-Draft draft-ietf-rtcweb-data-protocol-09.txt, January 2015.
[I-D.ietf-clue-protocol] Presta, R. and S. Romano, "CLUE protocol", Internet-Draft draft-ietf-clue-protocol-17.txt, September 2018.
[I-D.ietf-clue-signaling] Kyzivat, P., Xiao, L., Groves, C. and S. Romano, "CLUE Signaling", Internet-Draft draft-ietf-clue-signaling-14.txt, October 2018.

Author's Address

Christer Holmberg Ericsson Hirsalantie 11 Jorvas, 02420 Finland EMail: