Hi Roberta, IMHO, from path identification point of view, they are similar. Binding Segment is used to identify a path at the ingress LSR of the path, the Path segment is expected to be used to identify a path at the egress LSR or intermediate LSRs.
In addition, the Binding Segment will be replaced by the specific expanded label stack, and they will not be in the label stack at same time. The Path segment proposed in https://tools.ietf.org/html/draft-hegde-spring-traffic-accounting-for-sr-paths-01 and https://tools.ietf.org/html/draft-cheng-spring-mpls-path-segment-00 will be put together with the segment labels that identify the SR path in the label stack, and normally the Path segment label will be inserted following the last label of the SR path. Best regards, Mach From: spring [mailto:[email protected]] On Behalf Of Roberta Maglione (robmgl) Sent: Saturday, November 04, 2017 1:56 AM To: Shraddha Hegde <[email protected]>; [email protected] Cc: Adrian Farrel <[email protected]> Subject: Re: [spring] Slot request for IETF 100 Hello Shraddha, what's the difference between the SR-Path-Identifier specified in your draft and the Binding Segment defined in the Segment Routing Architecture draft? Thanks Roberta From: spring [mailto:[email protected]] On Behalf Of Shraddha Hegde Sent: Thursday, November 2, 2017 5:14 PM To: [email protected]<mailto:[email protected]> Cc: Adrian Farrel <[email protected]<mailto:[email protected]>> Subject: [spring] Slot request for IETF 100 Chairs, I would like to request a 10 min slot to present the below draft. https://tools.ietf.org/html/draft-hegde-spring-traffic-accounting-for-sr-paths-01 Thanks Shraddha
_______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
