[clue] Roman Danyliw's No Objection on draft-ietf-clue-datachannel-15: (with COMMENT)

[Roman Danyliw via Datatracker <[e-mail]>]

Roman Danyliw has entered the following ballot position for
draft-ietf-clue-datachannel-15: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-clue-datachannel/



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