Thank you Cheng. -10 addresses my point. Regards, --Bruno
-----Original Message----- From: Cheng Li <[email protected]> Sent: Monday, September 9, 2024 7:15 PM To: [email protected]; DECRAENE Bruno INNOV/NET <[email protected]>; [email protected]; [email protected]; Joel Halpern <[email protected]> Subject: RE: [spring] I-D Action: draft-ietf-spring-srv6-path-segment-10.txt -------------------------------------------------------------------------------------------------------------- CAUTION : This email originated outside the company. Do not click on any links or open attachments unless you are expecting them from the sender. ATTENTION : Cet e-mail provient de l'extérieur de l'entreprise. Ne cliquez pas sur les liens ou n'ouvrez pas les pièces jointes à moins de connaitre l'expéditeur. -------------------------------------------------------------------------------------------------------------- Hi Bruno, Zehua, Yao, Joel, Adrian, We have updated the draft according to your valuable comments recently. Please check if your comments are addressed. 1. added IANA section of P-flag and removed P-flag in the figure 3. [Bruno: https://mailarchive.ietf.org/arch/msg/spring/GF-l7Njzt9GzuYgjDN7Xmkqw_uw/] 2. added text to explain how to handle the P-flag and intermediate node processing. Confirmed by Zehua already. [Zehua: https://mailarchive.ietf.org/arch/msg/spring/f6teRgYMt1pv-ZtKqjh49WZw1aI/] 3. added text in introduction to explain the usage of Path Segment in different SR policy. [Yao: https://mailarchive.ietf.org/arch/msg/spring/jzoWkPc7VlhfJeKfzI8zW_jI194/] 4. added terms of SR path and SRv6 path, added text in Section 3 to explain the usage of SRv6 Path Segment to address Joel's comments.[Joel: https://mailarchive.ietf.org/arch/msg/spring/9DaRZ16Lhdvr-w8Z_BMTDF8Y8gw/] 5. added text in Security section. 6. made arguments are 0 instead of optional. In SRv6, the SID should define its argument clearly, with argument or without. We choose to remain the argument part but make it as 0 for now, which makes the implementation clear and easy. 7. updated to IANA code point 100 for END.PSID. 8. Other editorial modification. Please see diffs. Thank you so much for your comments! BTW, thanks for Lijie, Shengnan, Haojie's support, and Greg's comments. Respect, Cheng -----Original Message----- From: [email protected] <[email protected]> Sent: Monday, September 9, 2024 6:56 PM To: [email protected] Cc: [email protected] Subject: [spring] I-D Action: draft-ietf-spring-srv6-path-segment-10.txt Internet-Draft draft-ietf-spring-srv6-path-segment-10.txt is now available. It is a work item of the Source Packet Routing in Networking (SPRING) WG of the IETF. Title: Path Segment for SRv6 (Segment Routing in IPv6) Authors: Cheng Li Weiqiang Cheng Mach(Guoyi) Chen Dhruv Dhody Yongqing Zhu Name: draft-ietf-spring-srv6-path-segment-10.txt Pages: 15 Dates: 2024-09-09 Abstract: Segment Routing (SR) allows for a flexible definition of end-to-end paths by encoding an ordered list of instructions, called "segments". The SR architecture can be implemented over an MPLS data plane as well as an IPv6 data plane. Currently, Path Segment has been defined to identify an SR path in SR-MPLS networks, and is used for various use-cases such as end-to- end SR Path Protection and Performance Measurement (PM) of an SR path. This document defines the Path Segment to identify an SRv6 path in an IPv6 network. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-spring-srv6-path-segment/ There is also an HTMLized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-spring-srv6-path-segment-10 A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-spring-srv6-path-segment-10 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts _______________________________________________ spring mailing list -- [email protected] To unsubscribe send an email to [email protected] ____________________________________________________________________________________________________________ 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] To unsubscribe send an email to [email protected]
