|
Dear authors, I noticed a couple of typos in Section 2.5. These two points reference RFC8042 instead of 8402: o (Endpoint, Color) representing an SR policy [RFC8042] o (Mirrored SID) The Mirrored SID [RFC8042, Section 5.1] is the IP address advertised by the advertising node to identify the mirror- SID. The IP address is encoded as specified in Section 2.5.1.
Otherwise, I support. -- Sergey -----Original Message----- The IESG has received a request from the Source Packet Routing in Networking WG (spring) to consider the following document: - 'Segment Routing with MPLS data plane' <draft-ietf-spring-segment-routing-mpls-18.txt> as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the
ietf@xxxxxxxx mailing lists by 2019-03-07. Exceptionally, comments may be sent to
iesg@xxxxxxxx instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract Segment Routing (SR) leverages the source routing paradigm. A node steers a packet through a controlled set of instructions, called segments, by prepending the packet with an SR header. In the MPLS dataplane, the SR header is instantiated through a label stack. This document specifies the forwarding behavior to allow instantiating SR over the MPLS dataplane. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing-mpls/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing-mpls/ballot/ The following IPR Declarations may be related to this I-D: https://datatracker.ietf.org/ipr/2880/ https://datatracker.ietf.org/ipr/2453/ https://datatracker.ietf.org/ipr/2454/ _______________________________________________ spring mailing list |
