[core] Barry Leiba's Yes on draft-ietf-core-hop-limit-06: (with COMMENT)

Barry Leiba via Datatracker <noreply@ietf.org> Tue, 15 October 2019 22:04 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: core@ietf.org
Delivered-To: core@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B0681120045; Tue, 15 Oct 2019 15:04:48 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Barry Leiba via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-core-hop-limit@ietf.org, Jaime Jimenez <jaime@iki.fi>, core-chairs@ietf.org, jaime@iki.fi, core@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.105.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Barry Leiba <barryleiba@computer.org>
Message-ID: <157117708870.28091.17993723408155206601.idtracker@ietfa.amsl.com>
Date: Tue, 15 Oct 2019 15:04:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/2Qb4ZQ52uhjDUEOyWKM9pZSUmTw>
Subject: [core] Barry Leiba's Yes on draft-ietf-core-hop-limit-06: (with COMMENT)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Oct 2019 22:04:49 -0000

Barry Leiba has entered the following ballot position for
draft-ietf-core-hop-limit-06: 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-core-hop-limit/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for a simple, yet useful document.  Just some really small nits here:

I wish you had used “that” in most places in the document where “which” is. 
Perhaps the RFC Editor will change those.  If you care to make me happier (an
optional thing, surely), you might change every instance of “which” to “that”
*except* the one in the Abstract (which is correct).

— Section 3 —

   Nevertheless, the presence of such proxies will not prevent infinite
   loop detection if at least one CoAP proxy which support the Hop-Limit
   option is involved in the loop.

“support” -> “supports”

   A CoAP proxy which understands the Hop-Limit option MAY be
   instructed, using a configuration parameter, to insert a Hop-Limit
   option when relaying a request which do not include the Hop-Limit
   option.

“do not” -> “does not”