Re: [Detnet] FW: New Version Notification for draft-jags-mpls-ps-mna-hdr-00.txt

Hi, Jags, Authors, et al.,
thank you for sharing your proposal for the PSD MNA. I've read the draft
and would greatly appreciate your kind consideration of my notes and
questions.

   - The description of the IHS field suggests that its value indicates the
   scope of both ISD and PSD. As I understand it, described in Section 4, the
   post-stack network action indicator is part of NAS. If that is the case,
   then it seems like, in the given packet, PSD can have only one scope.
   - Assuming that the First Nibble for MNA PSD uses 0001b, as proposed in
   the draft, what is the value of the Version field?
   - I got confused reading the description of Opcode 1:

   Purpose: This opcode carries the start offset of the Post-Stack

   Network Action Top Header.

My understanding of the draft prior to Section 6.1 is that a Post-Stack
Network Action Header immediately follows a Post-Stack Network Action Top
Header (which, in turn, immediately follows a BoS LSE). If my understanding
is correct, what is the benefit of using Opcode 1?


   - I have a particular scenario. Consider a sequence of LSRs 1, 2, 3, and
   4 (there could be other LSRs, but these are not important for my case).
   Assume that LSR 1 places PSD and LSR 4 is expected to remove it. Now, my
   question is, Can LSR 2 add another PSD so that LSR 3 will dispose of it?
   - I appreciate your help in understanding the impact on the performance
   of the following requirement:

   A node that removes the last copy of a NAS that has the P bit set
   MUST remove all Post-Stack Network Actions.
It appears to me that every node that disposes of a NAS with the P bit set
has to scan the remaining label stack in order to determine that NAS is, in
fact, "the last with P set". Or am I missing something?


   - Another question, if I may. It seems to me that the following
   requirement is not complete:

the penultimate node MUST NOT remove the last copy of a HBH or I2E NAS

What if the scope of the last copy is Select? Also, it is not clear to me
how this requirement is related to PSD MNA. I hope you can clarify that for
me.

In conclusion, I believe that the discussion of a PSD MNA solution is
practical after we determine that there is a use case that cannot be
sufficiently well addressed using the ISD MNA approach. I still see a
significant level of complexity that PSD MNA adds to overall MNA.

Regards,
Greg

On Fri, Mar 10, 2023 at 4:58 AM Jaganbabu Rajamanickam (jrajaman) <jrajaman=
[email protected]> wrote:

> Hello Everyone,
>
>
>
>    We like to introduce our new draft on Post-Stack MNA solution.
>
>    Welcome your review comments and suggestions.
>
>
>
> Thanx,
>
> Jags
>
>
>
> *From: *[email protected] <[email protected]>
> *Date: *Friday, March 10, 2023 at 7:52 AM
> *To: *Jaganbabu Rajamanickam (jrajaman) <[email protected]>, Jie Dong <
> [email protected]>, Rakesh Gandhi (rgandhi) <[email protected]>, Royi
> Zigler <[email protected]>, Tony Li <[email protected]>
> *Subject: *New Version Notification for draft-jags-mpls-ps-mna-hdr-00.txt
>
>
> A new version of I-D, draft-jags-mpls-ps-mna-hdr-00.txt
> has been successfully submitted by Jaganbabu Rajamanickam and posted to the
> IETF repository.
>
> Name:           draft-jags-mpls-ps-mna-hdr
> Revision:       00
> Title:          Post-Stack MPLS Network Action (MNA) Solution
> Document date:  2023-03-10
> Group:          Individual Submission
> Pages:          17
> URL:
> https://www.ietf.org/archive/id/draft-jags-mpls-ps-mna-hdr-00.txt
> Status:
> https://datatracker.ietf.org/doc/draft-jags-mpls-ps-mna-hdr/
> Html:
> https://www.ietf.org/archive/id/draft-jags-mpls-ps-mna-hdr-00.html
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-jags-mpls-ps-mna-hdr
>
>
> Abstract:
>    This document defines the Post-Stack MPLS Network Action (MNA)
>    solution for carrying Network Actions and Ancillary Data after the
>    MPLS label stack based on In-Stack MNA solution defined in draft-
>    ietf-mpls-mna-hdr.  MPLS Network Actions can be used to influence
>    packet forwarding decisions, carry additional OAM information in the
>    MPLS packet or perform user-defined operations.  This document
>    addresses the MNA requirements specified in draft-ietf-mpls-mna-
>    requirements.  This document follows the MNA framework specified in
>    draft-ietf-mpls-mna-fwk.
>
>
>
>
>
> The IETF Secretariat
>
> _______________________________________________
> detnet mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/detnet
>

_______________________________________________
Pals mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/pals