Controlling Multiple Streams for Telepresence (CLUE) Protocol Data Channel
draft-ietf-clue-datachannel-18

[Ballot comment]
A few nits:

(1) Section 1.  Typo (missing space).

s/[I-D.ietf-clue-protocol]messages/
[I-D.ietf-clue-protocol] messages/

(2) Section 1. Editorial Nit.

s/data channel Establishment Protocol/
Data Channel Establishment Protocol/

(3) Section 3.2.1, Typo

s/(e.g. regarding ordered delivery )/
(e.g., regarding ordered delivery)/

(4) Section 3.2.1.  Typo.  s/signalled/signaled/

(5) Section 3.2.3, Per “[I-D.ietf-rtcweb-data-channel] also mandates support of the limited retransmission policy defined in [RFC7496].”, I was expecting to read something about how this extension is also not needed by CLUE like the previous part of the paragraph.  Right now the text only states something about rtcweb but not CLUE.

[Ballot comment]
Section 1

                                          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.

nit: "m= line"

Section 2

Please use the RFC 8174 boilerplate.

Section 3.1

  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

nit: "m= line"?

Section 3.2.7

  As described in [I-D.ietf-rtcweb-data-protocol], in order to close a
  data channel, an entity sends an SCTP reset message [RFC6525] on its

This reference would normally make draft-ietf-rtcweb-data-protocol a
normative reference, but I think that perhaps the intended reference is
actually draft-ietf-rtcweb-data-channel (which is already a normative
reference).  In particular, Section 6.7 of the latter document is about
"Closing a Data Channel" and mentions resetting the streams.

Section 3.3.2

  The values of the SDP dcmap attribute
  [I-D.ietf-mmusic-data-channel-sdpneg], associated with the m- line

nit: "m= line"?

Section 5.1

I note that the WebSocket Subprotocol Name Registry has the "first come,
first served" registration policy, which makes a declarative statement like
this ("this document adds") a bit risky -- what if someone else swoops in
to register this name?

[Ballot comment]
While the I-D was waiting for missing references, RFC 2119 has been obsoleted by RFC 8174 => please update section 2.

It is unclear for me in section 3.2.7 whether the 'stream reset' actually refers to RFC 6525 "SSN reset". Looking forward to being enlighten on this point.

*Nits*

Section 3.2.2, I wonder whether the note is really required as it restates parts of another documents (even if it gives some more context as in other subsections of section 3.2).

Section 3.2.7 s/Close CLUE data channel/Closing the CLUE data channel/

[Ballot comment]
This document completed IETF last call in 2016, and was held by my predecessor AD "to await progress on the RTCWEB security document, which is referenced." Now that the RTCWEB security documents have completed their IESG evaulation, this document is ready for evaluation.

Please note that the document internally says it is standards-track, while the datatracker has it marked as experimental. The datatracker is correct. See https://mailarchive.ietf.org/arch/msg/clue/1o3-x4T_J9lZGp50Z4rOIpmsE60 and https://mailarchive.ietf.org/arch/msg/clue/lqCLQNlb0XWWJ9GAseVGJU4yP6E for context.

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

IANA has completed its review of draft-ietf-clue-datachannel-13. If any part of this review is inaccurate, please let us know.

IANA understands that, upon approval of this document, there is a single action which IANA must complete.

In the WebSocket Subprotocol Name subregistry of the WebSocket Protocol Registries located at:

https://www.iana.org/assignments/websocket/

a single new subprotocol name is to be registered as follows:

Subprotocol Identifier: CLUE
Subprotocol Common Name: CLUE
Subprotocol Definition: [ TBD-at-registration ]
Reference: [ RFC-to-be ]

IANA understands that this is the only action required upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed. 

Thank you,

Amanda Baber
IANA Lead Specialist
ICANN

(Via drafts-lastcall-comment@iana.org): IESG/Authors/WG Chairs:

IANA has completed its review of draft-ietf-clue-datachannel-13.txt. If any part of this review is inaccurate, please let us know.

IANA understands that some of the actions requested in the IANA Considerations section of this document are dependent upon the approval of and completion of IANA Actions in another document:

https://tools.ietf.org/html/draft-ietf-rtcweb-data-protocol

IANA understands that, upon approval of this document, there is a single action which IANA must complete.

In the new registry called the "Protocol Registry" for the Data Channel Establishment Protocol created upon approval of the document:

https://tools.ietf.org/html/draft-ietf-rtcweb-data-protocol

a single new protocol is to be registered as follows:

Protocol Value: [ TBD-at-registration ]
Protocol: CLUE
Reference: [ RFC-to-be ]

IANA understands that this is the only action required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed. 

Thank you,

Sabrina Tanamal
IANA Specialist
ICANN

The following Last Call announcement was sent out:

From: The IESG
To: "IETF-Announce"
CC: pkyzivat@cisco.com, clue@ietf.org, draft-ietf-clue-datachannel@ietf.org, alissa@cooperw.in, clue-chairs@ietf.org
Reply-To: ietf@ietf.org
Sender:
Subject: Extended Last Call:  (CLUE Protocol data channel) to Proposed Standard


The IESG has received a request from the ControLling mUltiple streams for
tElepresence WG (clue) to consider the following document:
- 'CLUE Protocol data channel'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2016-08-01. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


  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.

  The document defines how to describe the SCTPoDTLS association used
  to realize the CLUE data channel using the Session Description
  Protocol (SDP), and defines usage of SDP-based "SCTP over DTLS" data
  channel negotiation mechanism for establishing a CLUE data channel.

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




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-clue-datachannel/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-clue-datachannel/ballot/


No IPR declarations have been submitted directly on this I-D.

The following Last Call announcement was sent out:

From: The IESG
To: "IETF-Announce"
CC: pkyzivat@cisco.com, clue@ietf.org, draft-ietf-clue-datachannel@ietf.org, alissa@cooperw.in, clue-chairs@ietf.org
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (CLUE Protocol data channel) to Proposed Standard


The IESG has received a request from the ControLling mUltiple streams for
tElepresence WG (clue) to consider the following document:
- 'CLUE Protocol data channel'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2016-07-21. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


  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.

  The document defines how to describe the SCTPoDTLS association used
  to realize the CLUE data channel using the Session Description
  Protocol (SDP), and defines usage of SDP-based "SCTP over DTLS" data
  channel negotiation mechanism for establishing a CLUE data channel.

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




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-clue-datachannel/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-clue-datachannel/ballot/


No IPR declarations have been submitted directly on this I-D.