[mpls] John Scudder's No Objection on draft-ietf-mpls-rfc6374-sr-16: (with COMMENT)
John Scudder via Datatracker <noreply@ietf.org> Thu, 17 October 2024 13:42 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@ietfa.amsl.com
Received: from [10.244.8.251] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id 8544EC14F619; Thu, 17 Oct 2024 06:42:32 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: John Scudder via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <172917255220.1398107.14965779731195440215@dt-datatracker-78dc5ccf94-w8wgc>
Date: Thu, 17 Oct 2024 06:42:32 -0700
Message-ID-Hash: DJXE2LHB6GL2TGZNEI4MWC4ZLINL22DS
X-Message-ID-Hash: DJXE2LHB6GL2TGZNEI4MWC4ZLINL22DS
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-mpls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-mpls-rfc6374-sr@ietf.org, mpls-chairs@ietf.org, mpls@ietf.org, tsaad@cisco.com
X-Mailman-Version: 3.3.9rc6
Reply-To: John Scudder <jgs@juniper.net>
Subject: [mpls] John Scudder's No Objection on draft-ietf-mpls-rfc6374-sr-16: (with COMMENT)
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/4w2Dyw6wJCgFyRLMI9xoYI1VmVU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Owner: <mailto:mpls-owner@ietf.org>
List-Post: <mailto:mpls@ietf.org>
List-Subscribe: <mailto:mpls-join@ietf.org>
List-Unsubscribe: <mailto:mpls-leave@ietf.org>
John Scudder has entered the following ballot position for draft-ietf-mpls-rfc6374-sr-16: 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-mpls-rfc6374-sr/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thanks for this well-written document. I have a few small comments. ### Section 2.3 The channel may be a directly connected link enabled with MPLS (Section 2.9.1 of [RFC6374]) or a Point-to-Point (P2P) SR-MPLS path [RFC8402]. The link may be a physical interface, a virtual link, or I don't see either "point-to-point" or "p2p" in RFC 8402. Would the quoted section be just as valid if you removed these adjectives? ### Section 4.1.2 by the intended responder, the Destination Address TLV (Type 129) [RFC6374] containing the address of the responder can be sent in the Shouldn't that be "an address of the responder" since in general it will have more than one? ### Section 9 responder. If the responder does not support the new Mandatory TLV Types defined in this document; it MUST return Error 0x17: Unsupported Mandatory TLV Object as per [RFC6374]. That seems like a misuse of the RFC 2119 keyword; by definition, this spec can't dictate any requirements to a responder that doesn't implement this spec. Probably you mean something like, NEW: responder. If the responder does not support the new Mandatory TLV Types defined in this document it will return Error 0x17: Unsupported Mandatory TLV Object as per [RFC6374]. (I also removed a spurious semicolon.)
- [mpls] Re: John Scudder's No Objection on draft-i… Rakesh Gandhi
- [mpls] John Scudder's No Objection on draft-ietf-… John Scudder via Datatracker