[clue] Benjamin Kaduk's No Objection on draft-ietf-clue-datachannel-15: (with COMMENT)
Benjamin Kaduk via Datatracker <noreply@ietf.org> Wed, 10 April 2019 14:16 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 DC9E7120021; Wed, 10 Apr 2019 07:16:58 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk 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: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <155490581889.22863.747311121377162579.idtracker@ietfa.amsl.com>
Date: Wed, 10 Apr 2019 07:16:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/xjj4HhAb0BBYTxj020zPd7zgVrc>
Subject: [clue] Benjamin Kaduk'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: Wed, 10 Apr 2019 14:16:59 -0000
Benjamin Kaduk 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: ---------------------------------------------------------------------- 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?
- [clue] Benjamin Kaduk's No Objection on draft-iet… Benjamin Kaduk via Datatracker
- Re: [clue] Benjamin Kaduk's No Objection on draft… Christer Holmberg