[Ice] Benjamin Kaduk's Yes on draft-ietf-ice-trickle-18: (with COMMENT)
Benjamin Kaduk <kaduk@mit.edu> Thu, 29 March 2018 20:59 UTC
Return-Path: <kaduk@mit.edu>
X-Original-To: ice@ietf.org
Delivered-To: ice@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 615AB1250B8; Thu, 29 Mar 2018 13:59:42 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk <kaduk@mit.edu>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-ice-trickle@ietf.org, Nils Ohlmeier <nohlmeier@mozilla.com>, ice-chairs@ietf.org, nohlmeier@mozilla.com, ice@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.76.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152235718235.4397.6159667533096871849.idtracker@ietfa.amsl.com>
Date: Thu, 29 Mar 2018 13:59:42 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ice/7YwlqAuEH8o9tbqewC6EPXv-J6E>
Subject: [Ice] Benjamin Kaduk's Yes on draft-ietf-ice-trickle-18: (with COMMENT)
X-BeenThere: ice@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "Interactive Connectivity Establishment \(ICE\)" <ice.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ice>, <mailto:ice-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ice/>
List-Post: <mailto:ice@ietf.org>
List-Help: <mailto:ice-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ice>, <mailto:ice-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Mar 2018 20:59:42 -0000
Benjamin Kaduk has entered the following ballot position for draft-ietf-ice-trickle-18: Yes 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-ice-trickle/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Please consider using the RFC 8174 boilerplate to supplement RFC 2119. Section 5 implies that plain ICE includes a provision for an ICE description with no candidates, but I'm failing to find that reference. The rfc5245bis draft seems to always assume that there will be at least a host candidate. Is perhaps a different reference intended? In section 8.2: o As a standalone notification (e.g., after STUN Binding requests or TURN Allocate requests to a server time out and the agent has is not actively gathering candidates) s/has is/is/ Section 13 says that trickled candidate information may cause an ICE restart using the 5245bis semantics, but I don't see anywhere in 5245bis that would have additional candidate information induce a restart. Is this the right reference? Thanks for updating per the secdir review about the in-order requirement! However, we currently have language about transmitting candidates/end-of-candidates "not more than once", but we kind of do want exactly-once semantics for end-of-candidates, unless ICE terminates normally prior to that. Is there a good way to phrase that more clearly? Maybe the last bullet of section 15 (must be able to send end-of-candidates) should come earlier in the list, in particular before the requirement for nonduplication and in-order.
- [Ice] Benjamin Kaduk's Yes on draft-ietf-ice-tric… Benjamin Kaduk
- Re: [Ice] Benjamin Kaduk's Yes on draft-ietf-ice-… Peter Saint-Andre
- Re: [Ice] Benjamin Kaduk's Yes on draft-ietf-ice-… Peter Saint-Andre
- Re: [Ice] Benjamin Kaduk's Yes on draft-ietf-ice-… Benjamin Kaduk
- Re: [Ice] Benjamin Kaduk's Yes on draft-ietf-ice-… Peter Saint-Andre
- Re: [Ice] Benjamin Kaduk's Yes on draft-ietf-ice-… Benjamin Kaduk
- Re: [Ice] Benjamin Kaduk's Yes on draft-ietf-ice-… Peter Saint-Andre