Diff: rfc8850v2.txt - rfc8850.txt

	rfc8850v2.txt	rfc8850.txt

	Internet Engineering Task Force (IETF) C. Holmberg	Internet Engineering Task Force (IETF) C. Holmberg
	Request for Comments: 8850 Ericsson	Request for Comments: 8850 Ericsson

	Category: Experimental June 2020	Category: Experimental January 2021
	ISSN: 2070-1721	ISSN: 2070-1721


	Controlling Multiple Streams for Telepresence (CLUE)	Controlling Multiple Streams for Telepresence (CLUE) Protocol
	Protocol Data Channel	Data Channel

	Abstract	Abstract

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

	Status of This Memo	Status of This Memo


	skipping to change at line 37 ¶	skipping to change at line 37 ¶
	publication by the Internet Engineering Steering Group (IESG). Not	publication by the Internet Engineering Steering Group (IESG). Not
	all documents approved by the IESG are candidates for any level of	all documents approved by the IESG are candidates for any level of
	Internet Standard; see Section 2 of RFC 7841.	Internet Standard; see Section 2 of RFC 7841.

	Information about the current status of this document, any errata,	Information about the current status of this document, any errata,
	and how to provide feedback on it may be obtained at	and how to provide feedback on it may be obtained at
	https://www.rfc-editor.org/info/rfc8850.	https://www.rfc-editor.org/info/rfc8850.

	Copyright Notice	Copyright Notice


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

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

	skipping to change at line 288 ¶	skipping to change at line 288 ¶

	3.3.2. SDP dcmap Attribute	3.3.2. SDP dcmap Attribute

	The values of the SDP dcmap attribute [RFC8864], associated with the	The values of the SDP dcmap attribute [RFC8864], associated with the
	"m=" line describing the SCTPoDTLS association used to realize the	"m=" line describing the SCTPoDTLS association used to realize the
	WebRTC data channel, are set as follows:	WebRTC data channel, are set as follows:

	+===========+=============+=============+=======+========+==========+	+===========+=============+=============+=======+========+==========+
	\| stream-id \| subprotocol \| label \|ordered\|max-retr\| max-time \|	\| stream-id \| subprotocol \| label \|ordered\|max-retr\| max-time \|
	+===========+=============+=============+=======+========+==========+	+===========+=============+=============+=======+========+==========+

	\| Value of \| "CLUE" \| Application \|"true" \| N/A \| N/A \|	\| Value of \| "CLUE" \| Application \| "true"\| N/A \| N/A \|
	\| the SCTP \| \| specific \| \| \| \|	\| the SCTP \| \| specific \| \| \| \|
	\|stream used\| \| \| \| \| \|	\|stream used\| \| \| \| \| \|

	\|to realize \| \| \| \| \| \|	\| to realize\| \| \| \| \| \|
	\| the CLUE \| \| \| \| \| \|	\| the CLUE \| \| \| \| \| \|
	\| data \| \| \| \| \| \|	\| data \| \| \| \| \| \|
	\| channel \| \| \| \| \| \|	\| channel \| \| \| \| \| \|
	+-----------+-------------+-------------+-------+--------+----------+	+-----------+-------------+-------------+-------+--------+----------+

	Table 2: SDP dcmap Attribute Values	Table 2: SDP dcmap Attribute Values

	\| NOTE: As CLUE entities are required to use ordered SCTP message	\| NOTE: As CLUE entities are required to use ordered SCTP message
	\| delivery, with full reliability, according to the procedures in	\| delivery, with full reliability, according to the procedures in
	\| [RFC8864] the max-retr and max-time attribute parameters are	\| [RFC8864] the max-retr and max-time attribute parameters are

	skipping to change at line 347 ¶	skipping to change at line 347 ¶
	+-------------------------+----------+	+-------------------------+----------+
	\| Subprotocol Identifier \| clue \|	\| Subprotocol Identifier \| clue \|
	+-------------------------+----------+	+-------------------------+----------+
	\| Subprotocol Common Name \| CLUE \|	\| Subprotocol Common Name \| CLUE \|
	+-------------------------+----------+	+-------------------------+----------+
	\| Subprotocol Definition \| RFC 8850 \|	\| Subprotocol Definition \| RFC 8850 \|
	+-------------------------+----------+	+-------------------------+----------+
	\| Reference \| RFC 8850 \|	\| Reference \| RFC 8850 \|
	+-------------------------+----------+	+-------------------------+----------+


	Table 3: Registration of 'CLUE' Value	Table 3: Registration of 'clue' Value

	6. References	6. References

	6.1. Normative References	6.1. Normative References

	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119,	Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,	DOI 10.17487/RFC2119, March 1997,
	<https://www.rfc-editor.org/info/rfc2119>.	<https://www.rfc-editor.org/info/rfc2119>.


	skipping to change at line 403 ¶	skipping to change at line 403 ¶

	[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC	[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
	2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,	2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
	May 2017, <https://www.rfc-editor.org/info/rfc8174>.	May 2017, <https://www.rfc-editor.org/info/rfc8174>.

	[RFC8261] Tuexen, M., Stewart, R., Jesup, R., and S. Loreto,	[RFC8261] Tuexen, M., Stewart, R., Jesup, R., and S. Loreto,
	"Datagram Transport Layer Security (DTLS) Encapsulation of	"Datagram Transport Layer Security (DTLS) Encapsulation of
	SCTP Packets", RFC 8261, DOI 10.17487/RFC8261, November	SCTP Packets", RFC 8261, DOI 10.17487/RFC8261, November
	2017, <https://www.rfc-editor.org/info/rfc8261>.	2017, <https://www.rfc-editor.org/info/rfc8261>.


	[RFC8841] Holmberg, C., Shpount, R.S., Loreto, S., and G. Camarillo,	[RFC8831] Jesup, R., Loreto, S., and M. Tüxen, "WebRTC Data
		Channels", RFC 8831, DOI 10.17487/RFC8831, January 2021,
		<https://www.rfc-editor.org/info/rfc8831>.

		[RFC8841] Holmberg, C., Shpount, R., Loreto, S., and G. Camarillo,
	"Session Description Protocol (SDP) Offer/Answer	"Session Description Protocol (SDP) Offer/Answer
	Procedures for Stream Control Transmission Protocol (SCTP)	Procedures for Stream Control Transmission Protocol (SCTP)
	over Datagram Transport Layer Security (DTLS) Transport",	over Datagram Transport Layer Security (DTLS) Transport",

	RFC 8841, DOI 10.17487/RFC8841, June 2020,	RFC 8841, DOI 10.17487/RFC8841, January 2021,
	<https://www.rfc-editor.org/info/rfc8841>.	<https://www.rfc-editor.org/info/rfc8841>.


	[RFC8831] Jesup, R., Loreto, S., and M. Tüxen, "WebRTC Data	[RFC8864] Drage, K., Makaraju, M., Ejzak, R., Marcon, J., and R.
	Channels", RFC 8831, DOI 10.17487/RFC8831, June 2020,	Even, Ed., "Negotiation Data Channels Using the Session
	<https://www.rfc-editor.org/info/rfc8831>.	Description Protocol (SDP)", RFC 8864,
		DOI 10.17487/RFC8864, January 2021,
	[RFC8864] Drage, K. E., Makaraju, M. R., Ejzak, R.P., Marcon, J.M.,
	and R. E. Even, Ed., "Data Channel Negotiation Based on
	the Session Description Protocol (SDP)", RFC 8864,
	DOI 10.17487/RFC8864, June 2020,
	<https://www.rfc-editor.org/info/rfc8864>.	<https://www.rfc-editor.org/info/rfc8864>.

	6.2. Informative References	6.2. Informative References

	[RFC3758] Stewart, R., Ramalho, M., Xie, Q., Tuexen, M., and P.	[RFC3758] Stewart, R., Ramalho, M., Xie, Q., Tuexen, M., and P.
	Conrad, "Stream Control Transmission Protocol (SCTP)	Conrad, "Stream Control Transmission Protocol (SCTP)
	Partial Reliability Extension", RFC 3758,	Partial Reliability Extension", RFC 3758,
	DOI 10.17487/RFC3758, May 2004,	DOI 10.17487/RFC3758, May 2004,
	<https://www.rfc-editor.org/info/rfc3758>.	<https://www.rfc-editor.org/info/rfc3758>.

	[RFC8445] Keranen, A., Holmberg, C., and J. Rosenberg, "Interactive	[RFC8445] Keranen, A., Holmberg, C., and J. Rosenberg, "Interactive
	Connectivity Establishment (ICE): A Protocol for Network	Connectivity Establishment (ICE): A Protocol for Network
	Address Translator (NAT) Traversal", RFC 8445,	Address Translator (NAT) Traversal", RFC 8445,
	DOI 10.17487/RFC8445, July 2018,	DOI 10.17487/RFC8445, July 2018,
	<https://www.rfc-editor.org/info/rfc8445>.	<https://www.rfc-editor.org/info/rfc8445>.

	[RFC8832] Jesup, R., Loreto, S., and M. Tüxen, "WebRTC Data Channel	[RFC8832] Jesup, R., Loreto, S., and M. Tüxen, "WebRTC Data Channel
	Establishment Protocol", RFC 8832, DOI 10.17487/RFC8832,	Establishment Protocol", RFC 8832, DOI 10.17487/RFC8832,

	June 2020, <https://www.rfc-editor.org/info/rfc8832>.	January 2021, <https://www.rfc-editor.org/info/rfc8832>.

	[RFC8847] Presta, R. and S P. Romano, "Protocol for Controlling	[RFC8847] Presta, R. and S P. Romano, "Protocol for Controlling
	Multiple Streams for Telepresence (CLUE)", RFC 8847,	Multiple Streams for Telepresence (CLUE)", RFC 8847,

	DOI 10.17487/RFC8847, June 2020,	DOI 10.17487/RFC8847, January 2021,
	<https://www.rfc-editor.org/info/rfc8847>.	<https://www.rfc-editor.org/info/rfc8847>.

	[RFC8848] Hanton, R., Kyzivat, P., Xiao, L., and C. Groves, "Session	[RFC8848] Hanton, R., Kyzivat, P., Xiao, L., and C. Groves, "Session
	Signaling for Controlling Multiple Streams for	Signaling for Controlling Multiple Streams for

	Telepresence (CLUE)", RFC 8848, DOI 10.17487/RFC8848, June	Telepresence (CLUE)", RFC 8848, DOI 10.17487/RFC8848,
	2020, <https://www.rfc-editor.org/info/rfc8848>.	January 2021, <https://www.rfc-editor.org/info/rfc8848>.

	Acknowledgements	Acknowledgements

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

	Author's Address	Author's Address

	Christer Holmberg	Christer Holmberg
	Ericsson	Ericsson

End of changes. 12 change blocks.
	21 lines changed or deleted	21 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/