draft-ietf-idr-tunnel-encaps
<[email protected]> Tue, 26 Nov 2019 15:38:00 +0000
| Newsgroups | gmane.ietf.idr |
|---|---|
| Message-ID | <16327_1574782681_5DDD46D9_16327_358_1_53C29892C857584299CBF5D05346208A48D0BCB7@OPEXCAUBM43.corporate.adroot.infra.ftgroup> |
Hi authors, Cc'ing John and Alvaro as the document has left IDR WG. TL;DR: I think that you should remove "an "IPv6 SID (Segment Identifier)" TLV," https://tools.ietf.org/html/draft-ietf-idr-tunnel-encaps-14#section-3.7 says: [I-D.ietf-idr-bgp-prefix-sid] defines a BGP Path attribute known as the "Prefix-SID Attribute". This attribute is defined to contain a sequence of one or more TLVs, where each TLV is either a "Label- Index" TLV, an "IPv6 SID (Segment Identifier)" TLV, or an "Originator SRGB (Source Routing Global Block)" TLV. Actually latest version of [I-D.ietf-idr-bgp-prefix-sid] has removed the support for "IPv6 SID (Segment Identifier)" TLV The value 2 previously corresponded to the IPv6 SID TLV which was specified in previous versions of this document. It was removed and usage of the BGP Prefix-SID for Segment Routing over the IPv6 dataplane [I-D.ietf-spring-segment-routing<https://tools.ietf.org/html/draft-ietf-idr-bgp-prefix-sid-27#ref-I-D.ietf-spring-segment-routing>] has been deferred to future specifications. https://tools.ietf.org/html/draft-ietf-idr-bgp-prefix-sid-27#section-7 Best regards, --Bruno _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Idr mailing list [email protected] https://www.ietf.org/mailman/listinfo/idr