Hi All, We have submitted a new version of this draft. Thanks for giving comments for this draft at the last IETF meeting. We have summarized the issues and tried to give some response as follows. If there is any other comment that is missing, please also let us know.
What is the requirement and applicable scenario? #1 [Response] The draft has been updated. This draft focuses on the scenario of hop-by-hop strict path. At the same time, it also analyzes the situation of non-strict paths, and describes the behavior and processing of the transition node Is the NRP-ID a hop by hop ID? #2 [Reponse] Relevant descriptions have been added to the updated version.In general, the network uniformly deploys NRP, and the NRP-IDs of each node are consistent. At the same time, the document adds the scenario description of different network nodes using different NRP-IDs What is the use case of having NRP-ID per SID? #3 [Reponse] The relevant description has been updated in the draft, NRP-ID carried by each SID can meet different scenario requirements, please refer to Section 4 for detailed description. What is the benefit of the approach? #4 [Reponse] In the scenario of SRv6 TE, the NRP-ID is carried by the segment encoded in the SRH, without the need for additional extension headers (such as HBH). With the feature that segment updates the destination address constantly; different NRP-IDs can be carried in the segment list and carried in the destination address to implement more flexible control. How to be sure that ARG has NRP-ID? #5 [Reponse]For the endpoint, it is a local behavior. For the transient node, as long as the destination address matches the local LSPT, will try to extract the NRP-ID from the destination address. Best Regards Yisong Liu -----邮件原件----- 发件人: internet-dra...@ietf.org <internet-dra...@ietf.org> 发送时间: 2022年10月16日 12:59 收件人: Changwang Lin <linchangwang.04...@h3c.com>; Hao Li <li...@h3c.com>; Liyan Gong <gongli...@chinamobile.com>; Yisong Liu <liuyis...@chinamobile.com> 主题: New Version Notification for draft-liu-spring-nrp-id-in-srv6-segment-01.txt A new version of I-D, draft-liu-spring-nrp-id-in-srv6-segment-01.txt has been successfully submitted by Yisong Liu and posted to the IETF repository. Name: draft-liu-spring-nrp-id-in-srv6-segment Revision: 01 Title: NRP ID in SRv6 segment Document date: 2022-10-16 Group: Individual Submission Pages: 21 URL: https://www.ietf.org/archive/id/draft-liu-spring-nrp-id-in-srv6-segment-01.txt Status: https://datatracker.ietf.org/doc/draft-liu-spring-nrp-id-in-srv6-segment/ Htmlized: https://datatracker.ietf.org/doc/html/draft-liu-spring-nrp-id-in-srv6-segment Diff: https://www.ietf.org/rfcdiff?url2=draft-liu-spring-nrp-id-in-srv6-segment-01 Abstract: This document proposes a method to carry the NRP-ID with the packet in the SRv6 segment. The IETF Secretariat _______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
