[mpls] Gunter Van de Velde's No Objection on draft-ietf-mpls-mna-usecases-13: (with COMMENT)

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

Return-Path: <noreply@ietf.org>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@ietfa.amsl.com
Received: from [10.244.2.67] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id B5181C151094; Tue, 17 Sep 2024 01:27:09 -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.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <172656162941.92849.17749042581073649397@dt-datatracker-65695bf5bc-rgg8z>
Date: Tue, 17 Sep 2024 01:27:09 -0700
Message-ID-Hash: YEQKDIY5RYQQZOLD5K663FY5A2YCCKUA
X-Message-ID-Hash: YEQKDIY5RYQQZOLD5K663FY5A2YCCKUA
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-mna-usecases@ietf.org, mpls-chairs@ietf.org, mpls@ietf.org
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 Objection on draft-ietf-mpls-mna-usecases-13: (with COMMENT)
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/156bhh7QQdKnmgLGG-zmLoAK_zI>
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-mna-usecases-13: 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-mna-usecases/



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

# Gunter Van de Velde, RTG AD, comments for draft-ietf-mpls-mna-usecases-13

# Please find the following non-blocking comments observed when reading the
draft. Please use at your discretion

#DETAILED COMMENTS
#=================
## classified as [minor] and [major]

173        MPLS Fast Reroute [RFC4090], [RFC5286] and [RFC7490] is a useful and
174        widely deployed tool for minimizing packet loss in the case of a link
175        or node failure.

[minor]
We should add the most advanced flavor of LFA
draft-ietf-rtgwg-segment-routing-ti-lfa-17 in this FRR list.

319        misordering, and allow for fragmentation.  In this case, the first
320        nibble the data that immediately follows after the MPLS BoS is set to
321        0000b to identify the presence of PW CW.

[minor]
the "0000b" threw me off-guard. Maybe better to say "0000 (binary)" to align
with formal writing conventions.

What about considering a to reference section 2.:
"   If the first nibble of a PW packet carried over an MPLS PSN has a
   value of 0, this indicates that the packet starts with a PWMCW."

330        Bit Index Explicit Replication (BIER) [RFC8296] traffic can also be
331        encapsulated over MPLS.  In this case, BIER has defined 0101b as the
332        value for the first nibble in the data that immediately appears after

[minor]
s/0000b/0000 (binary)/