Hi dongyu,




Thank you very much for taking time to review our draft and for your feedback. 
Please see the following:


1) If the context is carried in an SRv6 SID ARG, is the length of ARG enough to 
encode the context?


-What is carried in the fields of packets described in the draft, such as ARG, 
SRH TAG, SRH TLV, DOH, etc., is an identifier which could be mapping to a local 
context, as the context itself cannot be directly embedded within the packet. 
Once receiving an SRv6 packet containing identifier, the device could processes 
the packet using context corresponding to that identifier. Therefore, I think 
approximately 16 bits allocated from the 128-bit structure for the Argument 
field should suffice to encode these identifiers.





2) Suppose multiple SIDs including underlay SIDs and Service SIDs are carried 
in the Segment List, and if the context is carried in SRH TLV or DOH, how would 
the SIDs in SL correctly match the context?


-The identifier carried in the packet only serves to differentiate different 
tenants, applications and so on, and its semantics are locally defined by the 
device processing the packet. Specifically, the identifier is mapped to local 
instance, so that the suitable service could be delivered. The only requirement 
is that the value of an identifier should be unique either within a local 
domain or globally. 


For service function nodes, this identifier can be mapped to local 
context(e.g., local instances, policies, rules, etc.). Similarly, in the 
underlay network, the identifiers also can be locally mapped to specific 
process. If no service differentiation is required, just ignore the field 
directly.





Any questions and comments are welcome!





--------------------------------------------------------------------------------

Best regards,



叶佳铭/Jiaming Ye中国移动通信有限公司研究院/China Mobile Research Institute
Email: yejiam...@chinamobile.com
Mobile: 18810735331



----邮件原文----发件人:"yuan.dongyu" <yuan.don...@zte.com.cn>收件人:yejiaming 
<yejiam...@chinamobile.com>抄 送: spring <spring@ietf.org>,srv6ops 
<srv6...@ietf.org>,"huang.guangping" 
<huang.guangp...@zte.com.cn>,"miao.chuanyang" 
<miao.chuany...@zte.com.cn>发送时间:2025-05-08 22:03:59主题:Comments for 
draft-lin-spring-srv6-aware-context-indicator
Hi, Jiaming,

I39ve read the draft 
https://www.ietf.org/archive/id/draft-lin-spring-srv6-aware-context-indicator-05.txt.
 Here are several comments and questions.

1) If the context is carried in an SRv6 SID ARG, is the length of ARG enough to 
encode the context?

2) Suppose multiple SIDs including underlay SIDs and Service SIDs are carried 
in the Segment List, and if the context is carried in SRH TLV or DOH, how would 
the SIDs in SL correctly match the context?

Thanks for the work and looking forward to the reply.



Best regards,

Dongyu Yuan













袁冬宇


IT开发工程师


软件平台开发一部/有线研究院/系统产品_有线产品经营部





中兴通讯股份有限公司


南京市雨花台区紫荆花路68号南研一期2楼B2


M: +86 13776623784


E: yuan.don...@zte.com.cn






_______________________________________________
spring mailing list -- spring@ietf.org
To unsubscribe send an email to spring-le...@ietf.org

Reply via email to