Hi authors,
Speaking as individual contributor.
This document seems to define multiple types of segments (1 to 11).
May be this document would be the right place to define them normatively and
creates the IANA registry for them. And this seems like a work for spring.
Otherwise, there is a risk that other documents redefine them, possibly in a
non-consistent manner. (1) E.g. the BGP draft is not using the same type
numbers/name, which may bring confusion. I would expect YANG models to also
need these types.
BTW is there any chance to align the types in the BGP document or is this too
late? (alternatively may be changing the types in the sr-policy document)
Thanks,
Regards,
Bruno
(1)
SR-policy:
Type 1: SR-MPLS Label:
Type 2: SRv6 SID:
Type 3: IPv4 Prefix with optional SR Algorithm:
Type 4: IPv6 Global Prefix with optional SR Algorithm for SR-MPLS:
Type 5: IPv4 Prefix with Local Interface ID:
Type 6: IPv4 Addresses for link endpoints as Local, Remote pair:
Type 7: IPv6 Prefix and Interface ID for link endpoints as Local, Remote
pair for SR-MPLS:
Type 8: IPv6 Addresses for link endpoints as Local, Remote pair for SR-MPLS:
Type 9: IPv6 Global Prefix with optional SR Algorithm for SRv6:
Type 10: IPv6 Prefix and Interface ID for link endpoints as Local, Remote
pair for SRv6:
Type 11: IPv6 Addresses for link endpoints as Local, Remote pair for SRv6:
BGP:
1 MPLS SID sub-TLV This document
2 SRv6 SID sub-TLV This document
3 IPv4 Node and SID sub-TLV This document
4 IPv6 Node and SID for SR-MPLS sub-TLV This document
5 IPv4 Node, index and SID sub-TLV This document
6 IPv4 Local/Remote addresses and SID sub-TLV This document
7 IPv6 Node, index for remote and local pair This document
and SID for SR-MPLS sub-TLV
8 IPv6 Local/Remote addresses and SID sub-TLV This document
9 Weight sub-TLV This document
10 IPv6 Node and SID for SRv6 sub-TLV This document
11 IPv6 Node, index for remote and local pair This document
and SID for SRv6 sub-TLV
12 IPv6 Local/Remote addresses and SID for This document
SRv6 sub-TLV
_________________________________________________________________________________________________________________________
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.
_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring
