I reviewed the doc and had a bunch of editorial suggestions. Anoop
== Section 2 control layer protocol -> control plane protocol Segment routing header instantiated -> Segment routing header is instantiated We call "MPLS Control Plane Client (MCC)" any control plane -> We use the term "MPLS Control Plane Client (MCC)" to refer to any control plane which restrict its ability -> which restricts its ability In order ... -> This paragraph should be a subsection titled Node-SID TI-LFA -- expand acronym and provide reference (the reference is provided later, but should be provided here) node-SID -> Node-SID Section 2.1 ....,etc -> , etc. Instantiating Segment -> Instantiating segment Section 2.2 Probably be better if moved to being the first subsection in Section 2. Section 2.3 MPLS Label ranges -> MPLS label ranges The list of ranges comprising -> Any pair of ranges from the list of ranges comprising A Local segment -> A local segment except rule -> except the rule ....future study -> ...future study. Section 2.4 In the title -- label -> Label Section 2.5 Segment-Routing MPLS -> Segment Routing MPLS >>> For the purpose of incoming label collision resolution, a routing instance is identified by a single incoming label downloader to FIB. >>> ....identified by a single entity that installs incoming labels in the LFIB? (downloader is a new term.) make numerical value -> make the numerical value map to the same -> maps to the same a first-come-first-serve -> first-come-first-serve still collision -> still a collision reload -> reboot (only instance of reload, many instances of reboot) Section 2.5.1 >>> Each FEC is assigned an administrative distance. The FEC administrative distance is encoded as an 8-bit value. The lower the value, the better the administrative distance. >>> Move to be first paragraph in 2.5.1 smallest numerical FEC value -> smallest numerical FEC value. collision freeness on the same router -> collision freeness on the same router. administrative distance of any other FEC type -> administrative distance of any other FEC type. type code point for each SR FEC defined at the beginning of this Section -> code points for each SR FEC types defined at the beginning of this section an SR policy [RFC8402]. -> an SR policy [RFC8402] Missing periods at the end of many bullets/sub-bullets, and at last sentence of section. encoded in a 16 bits field -> encoded using 16 bits routing_instance_id, Topology, SR Algorithm,) -> Routing Instance ID, Topology, SR Algorithm) Color_id -> Color ID allow to map the original index -> allow mapping of the original index Section 2.5.2.2 with the prefix 192.0.2.1/32 -> with the prefix 192.0.2.1/32. index 1 corresponds to the local label 16001 -> index 1 corresponds to the local label 16001. (Also remove following bullet.) adj-SID, Adj-SID -- make consistent _______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
