[core] Éric Vyncke's No Objection on draft-ietf-core-hop-limit-06: (with COMMENT)
Éric Vyncke via Datatracker <noreply@ietf.org> Fri, 11 October 2019 06:41 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 3ED3F1200D5; Thu, 10 Oct 2019 23:41:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Éric Vyncke 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: Éric Vyncke <evyncke@cisco.com>
Message-ID: <157077606125.20455.11752074619038685184.idtracker@ietfa.amsl.com>
Date: Thu, 10 Oct 2019 23:41:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/dHj4vQHp7fAVXqoU-iFLfoP1cjA>
Subject: [core] Éric Vyncke's No Objection 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: Fri, 11 Oct 2019 06:41:01 -0000
Éric Vyncke has entered the following ballot position for draft-ietf-core-hop-limit-06: 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-core-hop-limit/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you for the work put into this document. I have a couple of COMMENTs (that I would appreciate to see a reply of yours) and one NIT. Regards, -éric == DISCUSS == == COMMENTS == -- Section 3 -- C.1) "Because forwarding errors may occur if inadequate Hop-Limit values are used, proxies at the boundaries of an administrative domain MAY be instructed to remove or rewrite the value of Hop-Limit carried in received messages" Isn't this remove all usefulness of the Hop-Limit option ? C.2) table 1, suggest to state the value of the C, U, N, R properties -- Section 4 -- C.3) while I understand why a proxy should not add its own diagnostic information when packet should become larger than the MTU of the next link, I wonder what will happen downstream when the MTU will be exceeded... C.4) suggest to use normative language (uppercase MAY, MUST, ...) == NITS == -- Section 3 -- N.1) s/if a less value/if a smaller value/ ?
- [core] Éric Vyncke's No Objection on draft-ietf-c… Éric Vyncke via Datatracker
- Re: [core] Éric Vyncke's No Objection on draft-ie… mohamed.boucadair
- Re: [core] Éric Vyncke's No Objection on draft-ie… Eric Vyncke (evyncke)
- Re: [core] Éric Vyncke's No Objection on draft-ie… mohamed.boucadair