[mpls] Gunter Van de Velde's No Record on draft-ietf-mpls-msd-yang-12: (with COMMENT)

Gunter Van de Velde via Datatracker <noreply@ietf.org> Mon, 08 July 2024 17:27 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@ietfa.amsl.com
Received: from [10.244.2.22] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id 256EFC22A2E8; Mon, 8 Jul 2024 10:27:20 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Gunter Van de Velde via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.17.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <172045963981.461285.15140299591053855501@dt-datatracker-5f88556585-j5r2h>
Date: Mon, 08 Jul 2024 10:27:19 -0700
Message-ID-Hash: ZHMJIUKZXVTNFAULCZRK3TZJZQGADAUR
X-Message-ID-Hash: ZHMJIUKZXVTNFAULCZRK3TZJZQGADAUR
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-msd-yang@ietf.org, mpls-chairs@ietf.org, mpls@ietf.org, tsaad@cisco.com
X-Mailman-Version: 3.3.9rc4
Reply-To: Gunter Van de Velde <gunter.van_de_velde@nokia.com>
Subject: [mpls] Gunter Van de Velde's No Record on draft-ietf-mpls-msd-yang-12: (with COMMENT)
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/z9eajBBle9hdE6-Crqo4Q5g3mn0>
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>

Gunter Van de Velde has entered the following ballot position for
draft-ietf-mpls-msd-yang-12: No Record

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-msd-yang/



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

I reviewed version draft-ietf-mpls-msd-yang-12

The draft is clear and in general i see no big issues with the yang model
proposed.

Currently, my ballot is explicitly set to a 'No Record' position as I am
unclear on the history behind why the MSD (Maximum SID Depth) leaves only
provide read-only operational information. I'll update once i understand the
philosophy of MSD model intent better.

Allow me to explain my concern. One might assume that a hardware device
supports, for instance, the most optimal setup where Ethernet encapsulation can
impose 10 MPLS segment SIDs. However, if such an interface is configured with a
more complex L2 encapsulation (such as 802.1q combined with EVPN service SIDs
and Entropy SIDs), the value that controllers can use might be reduced to 8, or
even less, depending on the encoding and encapsulation complexity. In such
scenarios, an operator may wish to adjust the most optimal MSD values to
something less optimal but supported by the hardware when attempting to program
a segment routing policy on a data packet