[Idr] Martin Duke's No Objection on draft-ietf-idr-bgp-ls-segment-routing-msd-16: (with COMMENT)

Martin Duke via Datatracker <noreply@ietf.org> Fri, 24 April 2020 16:54 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 DD5DB3A0F8C; Fri, 24 Apr 2020 09:54:52 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Martin Duke via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-idr-bgp-ls-segment-routing-msd@ietf.org, idr-chairs@ietf.org, idr@ietf.org, Susan Hares <shares@ndzh.com>, aretana.ietf@gmail.com, shares@ndzh.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.127.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Martin Duke <martin.h.duke@gmail.com>
Message-ID: <158774729288.14012.4297480673585471299@ietfa.amsl.com>
Date: Fri, 24 Apr 2020 09:54:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/C4N51oGnA2Fwvk0HtT26V0OsrII>
Subject: [Idr] Martin Duke's No Objection on draft-ietf-idr-bgp-ls-segment-routing-msd-16: (with COMMENT)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 24 Apr 2020 16:54:53 -0000

Martin Duke has entered the following ballot position for
draft-ietf-idr-bgp-ls-segment-routing-msd-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/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-idr-bgp-ls-segment-routing-msd/



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

This is not a DISCUSS-level concern, but I found it odd that the Node MSD TLV
must be the minimum of all configured interfaces without regard for the
presence of any Link MSD TLVs.

For example, if all node interfaces have an MSD of 20 except one with an MSD of
10, it would be much more compact to advertise a Node MSD of 20 and a single
Link MSD of 10. Section 5 says the Link MSD would take precedence, so there
would be no information loss. As I understand the spec, this would not be
allowed, and each link would have to be advertised separately to gain that
level of granularity.

If this is not the intent, then in Section 3, extending a sentence to say "Node
MSD is the smallest MSD supported by the node on the set of interfaces
configured for use, [excepting links advertised with their own Link MSD TLV]"
would avoid the problem.