[Idr] Éric Vyncke's No Objection on draft-ietf-idr-rfc7752bis-14: (with COMMENT)
Éric Vyncke via Datatracker <noreply@ietf.org> Thu, 15 December 2022 12:05 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C5BD8C152709; Thu, 15 Dec 2022 04:05:06 -0800 (PST)
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-idr-rfc7752bis@ietf.org, idr-chairs@ietf.org, idr@ietf.org, shares@ndzh.com, jhaas@pfrc.org, aretana.ietf@gmail.com, jhaas@pfrc.org, brian@innovationslab.net
X-Test-IDTracker: no
X-IETF-IDTracker: 9.3.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Éric Vyncke <evyncke@cisco.com>
Message-ID: <167110590679.47174.12764218588388046998@ietfa.amsl.com>
Date: Thu, 15 Dec 2022 04:05:06 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/aWdgIsrl_VSlxpO3pfxdqJM6HD4>
Subject: [Idr] Éric Vyncke's No Objection on draft-ietf-idr-rfc7752bis-14: (with COMMENT)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Dec 2022 12:05:06 -0000
Éric Vyncke has entered the following ballot position for draft-ietf-idr-rfc7752bis-14: 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/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-idr-rfc7752bis/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- # Éric Vyncke, INT AD, comments for draft-ietf-idr-rfc7752bis-14 CC @evyncke Thank you for the work put into this document, it appears to add welcomed clarification to RFC 7752. Due to lack of time, I have only reviewed the diff with RFC 7752 and I trust Brian Haberman's intdir review at: https://datatracker.ietf.org/doc/review-ietf-idr-rfc7752bis-14-intdir-telechat-haberman-2022-12-14/ (thank you Brian). Please find below some non-blocking COMMENT points (but replies would be appreciated even if only for my own education), and one nit. Special thanks to Jeffrey Haas for the *very detailed* shepherd's detailed write-up including the WG consensus and the justification of the intended status. I have also appreciated that you list the RFC 7752 authors as contributors to this document. I hope that this review helps to improve the document, Regards, -éric ## COMMENTS ### Section 5.2.2 The IPv4 address family has also link-local addresses (RFC 3927), to the text about link-local should be address family agnostic, i.e., either use "IPv6/IPv4 link-local address" or simply "link-local address". As this is mostly academic (IPv4 LLA are usually never used by routers), I am not raising a DISCUSS though. ### Section 5.3.2.3 What is the expected behaviour of the receiver/consumer when the trailing be are not 0 ? ### Section 5.3.2.7 Unsure what a `subset of the FQDN` is ... Do you mean a substring ? ### Section 5.4 Rather than `The Enterprise Codes are listed at <http://www.iana.org/assignments/enterprise-numbers>.`, suggest to use a normative reference. ## NITS ### ISIS vs. IS-IS Isn't the right writing "IS-IS" ? (I saw at least one such occurence) ## Notes This review is in the ["IETF Comments" Markdown format][ICMF], You can use the [`ietf-comments` tool][ICT] to automatically convert this review into individual GitHub issues. [ICMF]: https://github.com/mnot/ietf-comments/blob/main/format.md [ICT]: https://github.com/mnot/ietf-comments
- [Idr] Éric Vyncke's No Objection on draft-ietf-id… Éric Vyncke via Datatracker
- Re: [Idr] Éric Vyncke's No Objection on draft-iet… Ketan Talaulikar
- Re: [Idr] Éric Vyncke's No Objection on draft-iet… Eric Vyncke (evyncke)
- Re: [Idr] Éric Vyncke's No Objection on draft-iet… Ketan Talaulikar