I support publication of this draft.
I see a lot of value for operators with this draft encoding of the path
into a path segment for end to end 1+1 path protection and PM and path
correlation and bidirectional path instantiation for mobile backhaul.
In section 4 it talks about nesting of path seg
Support its publication.
Best Regards
Aijun Wang
China Telecom
From: spring-boun...@ietf.org On Behalf Of James
Guichard
Sent: Thursday, July 22, 2021 9:03 PM
To: James Guichard ; spring@ietf.org
Cc: spring-cha...@ietf.org
Subject: Re: [spring] WGLC for
https://datatracker.ietf.org
Dear all,
The meeting minutes for the SPRING session has been uploaded for your review.
https://datatracker.ietf.org/meeting/111/materials/minutes-111-spring-01.txt
Please let me know if there is any change that needs to make.
Thank you!
Best regards,
Shuping
__
Hi Stewart,
Many thanks for your comments.
Yes, we can add some text about the RX packet counters using the path
segment. As RX packet counts for incoming labels are typically supported by
most existing implementations, it is a natural choice. Other schemes e.g.
using metadata after BOS of MPLS lab
Hi Rakesh
I can see why you would want to use a label in that application, but using a
label has a cost that should be more thoroughly discussed in the text and
compared to alternatives.
What I see in the text is a reference to alt-marking, how are you proposing to
provide the alt pair?
Thank
Speaking as a WG chair from another WG:
If you followed the SPRING debate preceding the formation of the DT, it was
obvious that allowing open membership to the DT would not have been feasible
given the number of people participating and the combative tone of the
discussion. I think the chairs
Hi Robert,
In short the answer to your question is no. The chairs tried to create an
inclusive DT that had representation from all sides of the compression debate.
In addition the chairs deliberately stepped back and did not interfere in the
DT work.
Jim, Joel & Bruno
From: spring On Behalf
Hi Stewart,
The SR-MPLS path segment (MPLS label) is used to count received packets on
a particular path on the egress node. This allows us to measure PM packet
loss on a given path. The (incoming) MPLS label as path segment has an
advantage of using existing implementations for RX packet count.
Hi Greg
In -TP there were cases where we needed to send an OOB reply and we did this by
putting the IP address of the return node in the outgoing message.
My concern here is that just because this is an MPLS design, and you can use a
label as a proxy for an identifier does not mean that it is t
