Re: [spring] Relationship betweendraft-cheng-spring-srv6-policy-resource-gurantee anddraft-ietf-spring-resource-aware-segments

[姜文颖 <[e-mail]>]

Hi Alvaro，


Thanks for your comments.


 


We received the similar comments before IETF 107 [1] and the authors of both drafts had worked together to resolve it in the latest version. We has clarified the scope in draft-cheng and has changed the name of the draft to "draft-cheng-spring-srv6-policy-resource-guarantee" to better differentiate the two drafts. The authors of both drafts have reached a consensus and recommend that WG proceed with them separately.


 


The main differences are as follows：


Draft #1 draft-ietf-spring-resource-aware-segments


This draft extends the SR paradigm by associating SIDs with network resource attributes，and specific behaviors and actual application application scenarios are not defined.


 


Draft #2 draft-cheng-spring-srv6-policy-resource-gurantee


Based on draft-ietf-spring-resource-aware-segments，This draft further defines specific behaviors, and actual application application scenarios for End.NRP behavior.  This draft can provide guidance when deploying. The SRv6 END.NRP functional mechanism has a running code, and China Mobile has completed the verification of this function.


 


[1] https://mailarchive.ietf.org/arch/msg/spring/bzEbusdlwGRC5qlnYZVacDL8r3s/





B.R.


WenYing









----邮件原文----发件人：Alvaro Retana  <[e-mail]>收件人：draft-cheng-spring-srv6-policy-resource-gurantee <[e-mail]>抄　送: spring  <[e-mail]>,spring-chairs <[e-mail]>,draft-ietf-spring-resource-aware-segments <[e-mail]>发送时间：2023-10-11 03:40:05主题：[spring] Relationship betweendraft-cheng-spring-srv6-policy-resource-gurantee anddraft-ietf-spring-resource-aware-segmentsDear authors (of draft-cheng-spring-srv6-policy-resource-gurantee):Hi!Building on Jie39s comments at IETF 115 [1] and this text from theIntroduction: "On the basis of[I-D.ietf-spring-resource-aware-segments], this document defines a newSRv6 Endpoint behavior...", please clarify the relationship betweenthese 2 documents.Is this document an instantiation of a use case already covered byI-D.ietf-spring-resource-aware-segments, or is it a new application?Do we need this new extension, or isI-D.ietf-spring-resource-aware-segments enough?  Why do we need aseparate document?  Should the use case defined here be part of thealready adopted document?We (chairs) would like to hear comments from the authors of bothdocuments and the WG in general.Thanks!Alvaro.[1] https://datatracker.ietf.org/doc/minutes-115-spring/#network-resource-programming-with-srv6-10-mins_______________________________________________spring mailing [e-mail]://www.ietf.org/mailman/listinfo/springSubject：[spring] Relationship betweendraft-cheng-spring-srv6-policy-resource-gurantee anddraft-ietf-spring-resource-aware-segmentsDear authors (of draft-cheng-spring-srv6-policy-resource-gurantee):Hi!Building on Jie39s comments at IETF 115 [1] and this text from theIntroduction: "On the basis of[I-D.ietf-spring-resource-aware-segments], this document defines a newSRv6 Endpoint behavior...", please clarify the relationship betweenthese 2 documents.Is this document an instantiation of a use case already covered byI-D.ietf-spring-resource-aware-segments, or is it a new application?Do we need this new extension, or isI-D.ietf-spring-resource-aware-segments enough?  Why do we need aseparate document?  Should the use case defined here be part of thealready adopted document?We (chairs) would like to hear comments from the authors of bothdocuments and the WG in general.Thanks!Alvaro.[1] https://datatracker.ietf.org/doc/minutes-115-spring/#network-resource-programming-with-srv6-10-mins_______________________________________________spring mailing [e-mail]://www.ietf.org/mailman/listinfo/spring