Re: [mpls] Update to the bullets on the first page of my review of draft-song-mpls-extension-header-09

[Tianran Zhou <[e-mail]>]

Hi Loa,
Thanks very much for your review.
Some quick answer to your major concerns.
Please see in line with my reply.

Best,
Tianran

-----Original Message-----
From: Loa Andersson [mailto:[e-mail]] 
Sent: Tuesday, August 30, 2022 12:14 AM
To: [e-mail]
Cc: [e-mail]; [e-mail]; [e-mail]; DetNet Chairs <[e-mail]>
Subject: Update to the bullets on the first page of my review of draft-song-mpls-extension-header-09

Folks,

I just sent out a mail with my review of draft-song-mpls-extension-header-09.

It was very quickly pointed that I have a bunch of typos in the three bullets on the first page. The three bullets should have been:

•  I’m concerned about the inclusion of text on  “accessing the
    original protocol type and payload” in this document. Accessing
    protocol types (except for the first nibble) and payload is out of
    scope for MPLS, and thus for MNA.


ZTR> As you mentioned the "first nibble" is in the scope of MPLS. Since we have HEH, we can use some bits to quickly identify the original protocol. 

•  I’m still concerned that we are not considering the processing order
    between NAIs. I believe that for NAIs using post stack data only the
    EHs could be inserted in the right order after the HEH. However, what
    if the NAI relies on ISD ancillary data; and that NAI must be
    processed after one of the post stack data NAI, but before another?
    How is that handled?

ZTR> Do you mean the case when the ISD is not enough, hence requires a PSD? I am not sure if there is such use case. IMHO, if we anyway need PSD, we can put everything in the PSD. Why we need to split a feature into different parts?

•  The authors have started the process of transforming this into an MNA
    document, but the transformation is incomplete.


Sorry about this!

/Loa


-- 
Loa Andersson                        email: [e-mail]
Senior MPLS Expert                          [e-mail]
Bronze Dragon Consulting             phone: [phone]