The following errata report has been verified for RFC8666, "OSPFv3 Extensions for Segment Routing".
-------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid8319 -------------------------------------- Status: Verified Type: Editorial Reported by: Mohamed BOUCADAIR <mohamed.boucad...@orange.com> Date Reported: 2025-03-02 Verified by: Jim Guichard (IESG) Section: 6 Original Text ------------- Example 1: If the following router addresses (loopback addresses) need to be mapped into the corresponding Prefix-SID indexes: Router-A: 2001:DB8::1/128, Prefix-SID: Index 1 Router-B: 2001:DB8::2/128, Prefix-SID: Index 2 Router-C: 2001:DB8::3/128, Prefix-SID: Index 3 Router-D: 2001:DB8::4/128, Prefix-SID: Index 4 then the Address Prefix field in the OSPFv3 Extended Prefix Range TLV would be set to 2001:DB8::1, the Prefix Length would be set to 128, the Range Size would be set to 4, and the Index value in the Prefix- SID sub-TLV would be set to 1. Example 2: If the following prefixes need to be mapped into the corresponding Prefix-SID indexes: 2001:DB8:1::0/120, Prefix-SID: Index 51 2001:DB8:1::100/120, Prefix-SID: Index 52 2001:DB8:1::200/120, Prefix-SID: Index 53 2001:DB8:1::300/120, Prefix-SID: Index 54 2001:DB8:1::400/120, Prefix-SID: Index 55 2001:DB8:1::500/120, Prefix-SID: Index 56 2001:DB8:1::600/120, Prefix-SID: Index 57 then the Prefix field in the OSPFv3 Extended Prefix Range TLV would be set to 2001:DB8:1::0, the Prefix Length would be set to 120, the Range Size would be set to 7, and the Index value in the Prefix-SID sub-TLV would be set to 51. Corrected Text -------------- Example 1: If the following router addresses (loopback addresses) need to be mapped into the corresponding Prefix-SID indexes: Router-A: 2001:db8::1/128, Prefix-SID: Index 1 Router-B: 2001:db8::2/128, Prefix-SID: Index 2 Router-C: 2001:db8::3/128, Prefix-SID: Index 3 Router-D: 2001:db8::4/128, Prefix-SID: Index 4 then the Address Prefix field in the OSPFv3 Extended Prefix Range TLV would be set to 2001:db8::1, the Prefix Length would be set to 128, the Range Size would be set to 4, and the Index value in the Prefix- SID sub-TLV would be set to 1. Example 2: If the following prefixes need to be mapped into the corresponding Prefix-SID indexes: 2001:db8:1::0/120, Prefix-SID: Index 51 2001:db8:1::100/120, Prefix-SID: Index 52 2001:db8:1::200/120, Prefix-SID: Index 53 2001:db8:1::300/120, Prefix-SID: Index 54 2001:db8:1::400/120, Prefix-SID: Index 55 2001:db8:1::500/120, Prefix-SID: Index 56 2001:db8:1::600/120, Prefix-SID: Index 57 then the Prefix field in the OSPFv3 Extended Prefix Range TLV would be set to 2001:DB8:1::0, the Prefix Length would be set to 120, the Range Size would be set to 7, and the Index value in the Prefix-SID sub-TLV would be set to 51. Notes ----- The OLD does not follow this recommendation from rfc5952#section-4.3 The characters "a", "b", "c", "d", "e", and "f" in an IPv6 address MUST be represented in lowercase. -------------------------------------- RFC8666 (draft-ietf-ospf-ospfv3-segment-routing-extensions-23) -------------------------------------- Title : OSPFv3 Extensions for Segment Routing Publication Date : December 2019 Author(s) : P. Psenak, Ed., S. Previdi, Ed. Category : PROPOSED STANDARD Source : Link State Routing Stream : IETF Verifying Party : IESG _______________________________________________ Lsr mailing list -- lsr@ietf.org To unsubscribe send an email to lsr-le...@ietf.org
