[mpls] Re: New Version Notification for draft-ietf-mpls-mna-hdr-08.txt

["Jaganbabu Rajamanickam (jrajaman)" <[e-mail]>]

Hello Everyone,
   We have addressed the review comments discussed on the mailing list and during the IETF 120 meeting. Most of them are editorial comments. We have updated the draft with the following changes:


 Change-1:

In Section 3.
OLD
This document describes how network actions and their optional ancillary data are encoded as part of
an NAS as a stack of LSEs.

NEW

This document describes how network actions and their optional ancillary data are encoded as part of
an NAS as a stack of LSEs. Mechanisms that allow sharing of ancillary data AD between multiple network
actions encoded in the same NAS can be described in other documents and do not rely on any explicit
provision in the encodings described in this document.

END

Change-2:

In section-12 Implementation Status

Added New statement:     [Note to the RFC Editor - remove this section before publication, as well as remove the reference to [RFC7942].

OLD:
   The solution defined in this document has been implemented using P4 pipeline. The implementation code could be found at https://github.com/uni-tue-kn/P4-MNA.

NEW:
      The solution defined in the document draft-ietf-mpls-mna-hdr-05 has been implemented using P4 pipeline. The implementation code can be found at https://github.com/uni-tue-kn/P4-MNA.


xref target="I-D.ietf-mpls-mna-requirements

<xref target="RFC9613" format="default"/>

Change-3:

Updated the requirement docs to RFC 9613

Change-4:
Section 9.1: (Encapsulating Node Responsibilities)

OLD:
    If there is an existing label stack, the encapsulating node When ECMP technique in the network is using the hashing of the labels on the label stack then the first 20 bits of any LSE in the label stack MUST NOT be modified.

NEW:
If there is an existing label stack, the encapsulating node MUST NOT modify the first 20 bits of any LSE in the label stack when the ECMP technique in the network is using the hashing of the labels on the label stack.

Change-5:
Section 9.2: (Transit Node Responsibilities)

OLD:
    Transit nodes When ECMP technique in the network is using the hashing of the labels on the label stack then the first 20 bits of any LSE in the label stack MUST NOT be modified.

NEW:
The transit node MUST NOT modify the first 20 bits of any LSE in the label stack when the ECMP technique in the network is using the hashing of the labels on the label stack.


Change-7:

Addressed the following comments from IANA
About Section 14.2: In the first sentence, the second instance of the term “registry group” could be replaced with “category.”

About Section 14.4: Please remove the word “Registry” from the title “Network Action Opcodes Registry.”

Change-8:

section 15.1.1

Typo changed opcode=1 instead of opcode=2


Thanx,
Jags

From: [e-mail] <[e-mail]>
Date: Friday, August 30, 2024 at 5:27 PM
To: Haoyu Song <[e-mail]>, Jaganbabu Rajamanickam (jrajaman) <[e-mail]>, Kireeti Kompella <[e-mail]>, Rakesh Gandhi (rgandhi) <[e-mail]>, Royi Zigler <[e-mail]>
Subject: New Version Notification for draft-ietf-mpls-mna-hdr-08.txt
A new version of Internet-Draft draft-ietf-mpls-mna-hdr-08.txt has been
successfully submitted by Jaganbabu Rajamanickam and posted to the
IETF repository.

Name:     draft-ietf-mpls-mna-hdr
Revision: 08
Title:    MPLS Network Action (MNA) Sub-Stack Solution
Date:     2024-08-30
Group:    mpls
Pages:    28
URL:      https://www.ietf.org/archive/id/draft-ietf-mpls-mna-hdr-08.txt
Status:   https://datatracker.ietf.org/doc/draft-ietf-mpls-mna-hdr/
HTML:     https://www.ietf.org/archive/id/draft-ietf-mpls-mna-hdr-08.html
HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-mpls-mna-hdr
Diff:     https://author-tools.ietf.org/iddiff?url2=draft-ietf-mpls-mna-hdr-08

Abstract:

   This document defines the MPLS Network Action (MNA) sub-stack
   solution for carrying Network Actions and Ancillary Data in the label
   stack.  MPLS Network Actions can be used to influence packet
   forwarding decisions, carry additional Operations, Administration,
   and Maintenance (OAM) information in the MPLS packet or perform user-
   defined operations.  This solution document specifies In-stack
   network action and In-stack data (ISD) specific requirements found in
   "Requirements for MPLS Network Actions".  This document follows the
   architectural framework for the MPLS Network Actions (MNA)
   technologies specified in "MPLS Network Actions (MNA) Framework".



The IETF Secretariat