Re-,
Thanks, Thomas.
The description of 4 entry ("**Any label** associated with BGP") may suggest
that labels disseminated in BGP as per RFC8669 are also covered by that one.
You may include the clarification you provided below in your document to make
things less ambiguous.
Cheers,
Med
De : [email protected] [mailto:[email protected]]
Envoyé : mercredi 24 mars 2021 12:31
À : BOUCADAIR Mohamed TGI/OLN <[email protected]>;
[email protected]; [email protected]; [email protected]
Objet : RE: Call for adoption: draft-tgraf-ipfix-mpls-sr-label-type-07
Hi Med,
Many thanks for your review. I will include your input by adding
"mplsTopLabelIPv6Address" and correcting from "extension" to "extensions" in
-08.
In regards to IE46, distinguish between code point 4 and TBD4
4 | BGP: Any label associated with BGP or BGP routing
TBD4 | BGP Segment Routing Prefix-SID
This relates to the pending cleanup of the IE46 IPFIX MPLS label type registry
at IANA. Slide deck attached. Slides 3 and 4.
Code point 4 will be updated to RFC 8277 as reference.
With "BGP: Any label associated with BGP or BGP routing" the following is being
meant:
Using BGP to Bind MPLS Labels to Address Prefixes
https://tools.ietf.org/html/rfc8277#section-2
BGP Path Attributes - (14) MP_REACH_NLRI - Top Label
https://www.iana.org/assignments/bgp-parameters/bgp-parameters.xhtml#bgp-parameters-2
Code point TBD4 will have RFC 8669 as reference.
With "BGP Segment Routing Prefix-SID" the following is being meant:
Segment Routing Prefix Segment Identifier Extensions for BGP
https://tools.ietf.org/html/rfc8669#section-3.1
BGP Prefix-SID Label-Index TLV Flags
https://www.iana.org/assignments/bgp-parameters/bgp-parameters.xhtml#bgp-prefix-sid-label-index-tlv-flags
I hope this clarifies it. Looking forward to your feedback.
Best wishes
Thomas
From: OPSAWG <[email protected]<mailto:[email protected]>> On
Behalf Of [email protected]<mailto:[email protected]>
Sent: Wednesday, March 24, 2021 10:49 AM
To: Rob Wilton (rwilton)
<[email protected]<mailto:[email protected]>>;
Tianran Zhou <[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>
Subject: Re: [OPSAWG] Call for adoption: draft-tgraf-ipfix-mpls-sr-label-type-07
Hi all,
I support it as well.
As I expect that some usual suspects will raise a comment about IPv6, it is
better to fix this by mentioning mplsTopLabelIPv6Address in addition to 47
already cited in the document.
I also suggest to update the description in Section 3 to mention for each entry
this is about "extensions" for SR.
The authors may also clarify the relationship with (4 BGP: Any label
associated with BGP or BGP routing).
Cheers,
Med
De : OPSAWG [mailto:[email protected]] De la part de Rob Wilton (rwilton)
Envoyé : mercredi 24 mars 2021 10:21
À : Tianran Zhou <[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>
Objet : Re: [OPSAWG] Call for adoption: draft-tgraf-ipfix-mpls-sr-label-type-07
I've read this document and support its adoption.
Given that this document is only 6 pages long (really only 2 pages of
substantial content) I hope that this document can move through the WG quickly.
Thanks,
Rob
From: OPSAWG <[email protected]<mailto:[email protected]>> On
Behalf Of Tianran Zhou
Sent: 24 March 2021 06:23
To: [email protected]<mailto:[email protected]>
Subject: [OPSAWG] Call for adoption: draft-tgraf-ipfix-mpls-sr-label-type-07
Hi WG,
As discussed in the IETF110 meeting, we start a two weeks adoption call on
draft-tgraf-ipfix-mpls-sr-label-type-07:
https://datatracker.ietf.org/doc/draft-tgraf-ipfix-mpls-sr-label-type/<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-tgraf-ipfix-mpls-sr-label-type%2F&data=04%7C01%7CThomas.Graf%40swisscom.com%7C41a540a6788c4aec044708d8eeaa1c32%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637521761664220921%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=OZiFofgEwz5mtCz7gotduDLp3mddOYpqOb5nhGKUA%2Fs%3D&reserved=0>
Please respond with your comments and thoughts on this draft.
We will conclude on April 7, 2021.
Thanks,
Tianran as co-chair
_________________________________________________________________________________________________________________________
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.
_________________________________________________________________________________________________________________________
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.
_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg
