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

Roman Danyliw via Datatracker <noreply@ietf.org> Thu, 11 April 2019 00:41 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: clue@ietf.org
Delivered-To: clue@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ABA612025B; Wed, 10 Apr 2019 17:41:32 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-clue-datachannel@ietf.org, Paul Kyzivat <pkyzivat@alum.mit.edu>, clue-chairs@ietf.org, pkyzivat@alum.mit.edu, clue@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <155494329235.22694.2977698573542744808.idtracker@ietfa.amsl.com>
Date: Wed, 10 Apr 2019 17:41:32 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/jvRLwQTCSqOqXBRJV5YSdJe_ogE>
Subject: [clue] Roman Danyliw's No Objection on draft-ietf-clue-datachannel-15: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Apr 2019 00:41:33 -0000

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.