RFC 8888: CLUE Protocol data channel

RFC 8888	CLUE data channel	June 2019
Mori	Experimental	[Page]

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.¶

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. See RFCs 5725 and 7509.)¶

<CODE BEGINS> file "sample.abnf"

test
test
test

<CODE ENDS>

<CODE BEGINS> file ""

test
test
test

<CODE ENDS>

<CODE BEGINS> file "None"

test
test
test

<CODE ENDS>

<CODE BEGINS> file "None"

test
test
test

<CODE ENDS>

<CODE BEGINS> file "None"

test
test
test

<CODE ENDS>

<CODE BEGINS> file "None"

test
test
test

<CODE ENDS>

<CODE BEGINS> file "None"

test
test
test

<CODE ENDS>

<CODE BEGINS> file "None"

test
test
test

<CODE ENDS>

<CODE BEGINS> file "None"

test
test
test

<CODE ENDS>

<CODE BEGINS> file "None"

test
test
test

<CODE ENDS>

<CODE BEGINS> file "None"

test
test
test

<CODE ENDS>

<CODE BEGINS> file "None"

test
test
test

<CODE ENDS>

<CODE BEGINS> file "None"

test
test
test

<CODE ENDS>

<CODE BEGINS> file "None"

test
test
test

<CODE ENDS>

<CODE BEGINS> file "None"

test
test
test

<CODE ENDS>

<CODE BEGINS> file "None"

test
test
test

<CODE ENDS>

<CODE BEGINS> file "None"

test
test
test

<CODE ENDS>

The document defines how to describe the SCTPoDTLS association in RFC 8261 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. Testing U+68EE ("森") and U+6E29 ("温")¶

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], 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.¶

3.3.1.1. SDP Media Description Fields

Table 1: Test table
fruit	color	amount	price
apple	red	5	1

Table 2: Test table
fruit	color	amount	price
apple	red	5	1
apricot	orange	6	2
peach	peach	7	3
lime	green	8	4

[I-D.ietf-mmusic-sctp-sdp] defines how to set the values of an "m=" line describing an SCTPoDTLS association. As defined in [I-D.ietf-mmusic-sctp-sdp], for a CLUE data channel the values are set as following:¶

Table 3: SDP "proto" field values
media	port	proto	fmt
"application"	UDP port value	"UDP/DTLS/SCTP"	"webrtc-datachannel"
"application"	TCP port value	"TCP/DTLS/SCTP"	"webrtc-datachannel"

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).¶

3.3.1.2. 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:¶

Table 4: SDP dcmap attribute values
stream-id	sub-protocol	label	ordered	max-retr	max-time
Value of the SCTP stream used to realize the CLUE data channel	"CLUE"	Appli-cation 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

7. Change Log

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

Changes from draft-ietf-clue-datachannel-17¶

Editorial changes to Tables based on TSV-ART review.¶

Changes from draft-ietf-clue-datachannel-16¶

Category changed to Experimental.¶

Changes from draft-ietf-clue-datachannel-15¶

Updates based on IESG review by Roman Danyliw.¶
Make CLUE references Informative, as they are going to be published as Experimental RFCs.¶

Changes from draft-ietf-clue-datachannel-14¶

ICE reference update.¶
Reference draft versions updates.¶

Changes from draft-ietf-clue-datachannel-13¶

Editorial changes based on Gen-ART review from Brian Carpenter.¶

Changes from draft-ietf-clue-datachannel-12¶

Changes based on AD comments from Alissa Cooper (https://www.ietf.org/mail-archive/web/clue/current/msg04911.html):¶
- DCEP reference removed from security considerations.¶
- Editorial fixes.¶
- NOTE: Comment regarding the Security Considerations is still pending.¶

Changes from draft-ietf-clue-datachannel-11¶

Changes based on WGLC comments from Juergen Stoetzer-Bradler and Christian groves:¶
- Reference updates.¶
- 'Reference' added to IANA registration data.¶

Changes from draft-ietf-clue-datachannel-10¶

Security Considerations modified and enhanced, based on comments provided by Alissa Cooper.¶

Changes from draft-ietf-clue-datachannel-09¶

Reference updates:¶
- draft-ietf-tsvwg-sctp-prpolicies published as RFC 7496¶
- Reference update of draft versions¶

Changes from draft-ietf-clue-datachannel-08¶

Changes based on WGLC comments from Daniel Burnett:¶
- Editorial corrections.¶
Changes based on WGLC comments from Paul Kyzivat:¶
- Editorial corrections.¶

Changes from draft-ietf-clue-datachannel-07¶

Changes based on WGLC comments from Christian Groves:¶
- IANA considerations for dcmap attribute removed.¶
- Explicit clarification that the dcmap attribute max-time and max-retr parameters are not used with ordered/reliable transmission of SCTP messages.¶
- Indication that TCP transport should only be used if ICE is used, and if usage of TCP is required by ICE.¶
- Informative reference to ICE added.¶
- Editorial corrections.¶
Changes based on WGLC comments from Mark Duckworth:¶
- Make it more clear that the rules regarding usage of partial reliability and ordered reliability apply to CLUE data channels.¶
Changes based on WGLC comments from Paul Kyzivat:¶
- Clarify that same SCTP options are applied to each SCTP message associated with a given data channel.¶
- Switched location of sections 3.2 and 3.3.¶
- PPID table removed. Not needed, since only one value is used.¶
- Editorial corrections.¶

Changes from draft-ietf-clue-datachannel-06¶

Usage of DCEP removed.¶

Changes from draft-ietf-clue-datachannel-05¶

"DTLS/SCTP" split into "UDP/DTLS/SCTP" and "TCP/DTLS/SCTP".¶
Removed note regarding optionality of including the SDP sctp-port attribute.¶
Added defintion of 'SCTPoDTLS association' to the Conventions.¶
Reference to RFC 4566 (SDP) added.¶

Changes from draft-ietf-clue-datachannel-04¶

Defines DCEP and external SDP negotiation as two separate mechanisms for negotiating a CLUE data channel.¶
Updates based on technical changes in referenced specifications.¶
Reference to draft-ietf-mmusic-sctp-sdp added.¶

Changes from draft-ietf-clue-datachannel-03¶

IANA considerations added.¶
Editorial changes based on comments from Christian Groves.¶

Changes from draft-ietf-clue-datachannel-02¶

SDP "m=" line example fixed.¶
OPEN ISSUE #1 closed.¶
- It was agreed (IETF#91) to use draft-ejzak-mmusic-data-channel-sdpneg, as it was adopted as a WG item in MMUSIC.¶
- Details for draft-ejzak-mmusic-data-channel-sdpneg usage added.¶
SDP Offer/Answer procedures removed, as they will be defined in the CLUE protocol draft.¶
References updated.¶

Changes from draft-ietf-clue-datachannel-01¶

Support of interleaving "MUST"->"SHOULD".¶
Example updated.¶
Reference update.¶

Changes from draft-ietf-clue-datachannel-00¶

SDP Offer/Answer procedures structures according to RFC 3264.¶
Reference update.¶

Changes from draft-holmberg-clue-datachannel-04¶

Draft submitted as draft-ietf-clue-data-channel-00.¶
Editorial nits fixed.¶
Changes based on comments from Paul Kyzivat (http://www.ietf.org/mail-archive/web/clue/current/msg03559.html).¶
- Proto value fixed.¶
- Explicit text that the partial reliability and limited retransmission policies MUST NOT be used.¶
- Added open issue on whether the DCEP 'protocol' field value for CLUE should contain a version number.¶
- Removed paragraph saying that an offerer must not insert more than one "m=" line describing an SCTPoDTLS association to be used to realize a CLUE data channel, as the draft already states that only one CLUE data channel per CLUE session shall be opened.¶
- Added reference to draft-ietf-rtcweb-data-protocol regarding details on reseting SCTP streams.¶
- Added text saying that the value of the DCEP 'channel type' MUST be DATA_CHANNEL_RELIABLE.¶
- Clarified that DCEP must be supported, and used in the absence of another mechanism for opening a CLUE data channel.¶

Changes from draft-holmberg-clue-datachannel-03¶

Procedures updated, based on WG agreement (IETF#89) to use DCEP for the CLUE data channel.¶
Procedures updated, based on WG agreement (IETF#89) that offerer is responsible for sending DCEP DATA_CHANNEL_OPEN.¶
Editorial changes, and alignments caused by changes in referenced specifications.¶

Changes from draft-holmberg-clue-datachannel-02¶

PPID value for CLUE messages added¶
References updated¶

Changes from draft-holmberg-clue-datachannel-01¶

More text added¶

Changes from draft-holmberg-clue-datachannel-00¶

Editorial corrections based on comments from Paul K¶

8. References

8.1. Normative References

[I-D.ietf-mmusic-data-channel-sdpneg]: Drage, K.D., Makaraju, R.M., Stoetzer-Bradler, J.S., Ejzak, R.E., and J.M. Marcon, " SDP-based "SCTP over DTLS" data channel negotiation ", Internet-Draft draft-ietf-mmusic-data-channel-sdpneg-26.txt, 23 April 2019, <https://www.ietf.org/archive/id/draft-ietf-mmusic-data-channel-sdpneg-26.txt>.
[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, 20 April 2017, <https://www.ietf.org/archive/id/draft-ietf-mmusic-sctp-sdp-26.txt>.
[I-D.ietf-rtcweb-data-channel]: Jesup, R.J., Loreto, S.L., and M.T. Tuexen, " WebRTC data channels ", Internet-Draft draft-ietf-rtcweb-data-channel-13.txt, 4 January 2015, <https://www.ietf.org/archive/id/draft-ietf-rtcweb-data-channel-13.txt>.
[RFC2119]: Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>.
[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, <https://www.rfc-editor.org/info/rfc3261>.
[RFC3264]: Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with Session Description Protocol (SDP)", RFC 3264, DOI 10.17487/RFC3264, June 2002, <https://www.rfc-editor.org/info/rfc3264>.
[RFC3550]: Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson, "RTP: A Transport Protocol for Real-Time Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550, July 2003, <https://www.rfc-editor.org/info/rfc3550>.
[RFC4566]: Handley, M., Jacobson, V., and C. Perkins, "SDP: Session Description Protocol", RFC 4566, DOI 10.17487/RFC4566, July 2006, <https://www.rfc-editor.org/info/rfc4566>.
[RFC4960]: Stewart, R., Ed., "Stream Control Transmission Protocol", RFC 4960, DOI 10.17487/RFC4960, September 2007, <https://www.rfc-editor.org/info/rfc4960>.
[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, <https://www.rfc-editor.org/info/rfc5061>.
[RFC6525]: Stewart, R., Tuexen, M., and P. Lei, "Stream Control Transmission Protocol (SCTP) Stream Reconfiguration", RFC 6525, DOI 10.17487/RFC6525, February 2012, <https://www.rfc-editor.org/info/rfc6525>.
[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, <https://www.rfc-editor.org/info/rfc7496>.
[RFC8174]: Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[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, <https://www.rfc-editor.org/info/rfc8261>.

8.2. Informative References

[I-D.ietf-clue-protocol]: Presta, R.P. and S P.R. Romano, " CLUE protocol ", Internet-Draft draft-ietf-clue-protocol-17.txt, 21 September 2018, <https://www.ietf.org/archive/id/draft-ietf-clue-protocol-17.txt>.
[I-D.ietf-clue-signaling]: Kyzivat, P.K., Xiao, L.X., Groves, C.G., and S P.R. Romano, " CLUE Signaling ", Internet-Draft draft-ietf-clue-signaling-14.txt, 22 October 2018, <https://www.ietf.org/archive/id/draft-ietf-clue-signaling-14.txt>.
[I-D.ietf-rtcweb-data-protocol]: Jesup, R.J., Loreto, S.L., and M.T. Tuexen, " WebRTC data channel Establishment Protocol ", Internet-Draft draft-ietf-rtcweb-data-protocol-09.txt, 4 January 2015, <https://www.ietf.org/archive/id/draft-ietf-rtcweb-data-protocol-09.txt>.
[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, <https://www.rfc-editor.org/info/rfc3758>.
[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, <https://www.rfc-editor.org/info/rfc8445>.

CLUE Protocol data channel