[spring] Re: New Version Notification fordraft-cheng-spring- srv6-encoding-network-sliceid-13.txt
Liyan Gong <[email protected]> Wed, 8 Jul 2026 17:13:53 +0800 (CST)
| Newsgroups | gmane.ietf.spring,gmane.ietf.ipv6 |
|---|---|
| Message-ID | <2afe6a4de7f3f26-00106.Richmail.00000042459980901057@chinamobile.com> |
--===============3137679879358640411== Content-Type: multipart/alternative; boundary="----=_Part_301106_1680089663.1783502033052" ------=_Part_301106_1680089663.1783502033052 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: quoted-printable Dear Adrian and All, Thank you again for your valuable comments on the draft[1].=20 As suggested, we have carefully reviewed the mature NRP-related documents t= o ensure our terminology and concepts are fully aligned with the current fr= amework.=20 Based on this review, we have updated the draft to version -13. Key updates in version -13 include: 1. Terminology Alignment: Terminology has been updated throughout the docum= ent to align with the definitions in RFC 9543 and draft-ietf-teas-ns-ip-mpl= s. 1) The data plane identifier previously referred to as "SLID" is now consis= tently called the "NRP Selector Identifier",=20 2) The presence indicator has been renamed from "SPI" to "NPI".=20 3) The terminology section now includes formal definitions for "NRP Selecto= r" and "NRP Selector Identifier" with proper references. 2. Scope Clarification: We have made it clear that the document focuses sol= ely on encoding the NRP Selector ID in the outer IPv6 header, and that the = mapping from a specific slice to an NRP is outside the scope of this draft. =20 We hope these changes address the concerns raised and make the document mor= e aligned with the broader TEAS framework. We would appreciate further revi= ew and comments. [1]The draft link information is as follows=EF=BC=9A URL: https://www.ietf.org/archive/id/draft-cheng-spring-srv6-encoding-netwo= rk-sliceid-13.txtStatus: https://datatracker.ietf.org/doc/draft-cheng-sprin= g-srv6-encoding-network-sliceid/HTML: https://www.ietf.org/archive/id/draft= -cheng-spring-srv6-encoding-network-sliceid-13.htmlHTMLized: https://datatr= acker.ietf.org/doc/html/draft-cheng-spring-srv6-encoding-network-sliceidDif= f: https://author-tools.ietf.org/iddiff?url2=3Ddraft-cheng-spring-srv6-enco= ding-network-sliceid-13 =20 Best Regards, Liyan(on behalf of co-authors) ----=E9=82=AE=E4=BB=B6=E5=8E=9F=E6=96=87----=E5=8F=91=E4=BB=B6=E4=BA=BA=EF= =BC=9ALiyan Gong <[email protected]>=E6=94=B6=E4=BB=B6=E4=BA=BA=EF= =BC=9Aadrian <[email protected]>,spring <[email protected]>,6man <6man@i= etf.org>,TEAS WG <[email protected]>,IPv6 List <[email protected]>=E6=8A=84=E3=80= =80=E9=80=81: Changwang Lin <[email protected]>,Fenghua Ren <ren= [email protected]>,Mingyu Wu <[email protected]>,Peiyong Ma <mapeiy@chinat= elecom.cn>,Shay Zadok <[email protected]>,Weiqiang Cheng <chengweiq= [email protected]>,Xuewei Wang <[email protected]>=E5=8F=91=E9= =80=81=E6=97=B6=E9=97=B4=EF=BC=9A2026-01-14 18:39:33=E4=B8=BB=E9=A2=98=EF= =BC=9A[Teas] Re: New Version Notification fordraft-cheng-spring-srv6-encodi= ng-network-sliceid-12.txtDear Adrian, Thank you for your valuable feedback. We will carefully review RFC 9543 and the related drafts to better align th= e terminology and refine the positioning of our work. Once We have a clearer revision plan, We will follow up for further discuss= ion. Best regards, =20 Liyan ----=E9=82=AE=E4=BB=B6=E5=8E=9F=E6=96=87----=E5=8F=91=E4=BB=B6=E4=BA=BA=EF= =BC=9AAdrian Farrel <[email protected]>=E6=94=B6=E4=BB=B6=E4=BA=BA=EF=BC= =9A39Liyan Gong39 <[email protected]>,spring <[email protected]>,396m= an39 <[email protected]>,39TEAS WG39 <[email protected]>,39IPv6 List39 <[email protected]= rg>=E6=8A=84=E3=80=80=E9=80=81: 39Changwang Lin39 <[email protected]= om>,39Fenghua Ren39 <[email protected]>,39Mingyu Wu39 <[email protected]>= ,39Peiyong Ma39 <[email protected]>,39Shay Zadok39 <shay.zadok@broadco= m.com>,39Weiqiang Cheng39 <[email protected]>,39Xuewei Wang39 <= [email protected]>=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4=EF=BC=9A2026= -01-13 20:08:54=E4=B8=BB=E9=A2=98=EF=BC=9ARE: [Teas] Re: New Version Notifi= cation for draft-cheng-spring-srv6-encoding-network-sliceid-12.txt Hello, =20 Thanks for continuing to work on your draft. =20 I think it would be really helpful to try to align your terminology with ot= her work on network slicing. =20 For example: A network slice and a network resource partition are not the same thing (RF= C 9543). So a slice ID and an NRP ID are different. While it might be possi= ble to have a 1:1 mapping between slice and NRP, this is unlikely to be nor= mal. There may be a difference between a network resource partition identifier (= NRP-ID) and a network resource partition selector identifier (NRPS ID) (dra= ft-ietf-teas-nrp-scalability section 5.2 and draft-ietf-teas-ns-ip-mpls) =20 It might also be useful to look at drafts that already exist and have been = adopted by working groups to discover where you are =E2=80=9Ccompeting=E2= =80=9D with existing IETF work and where you supplement it. =20 Cheers, Adrian =20 From: Liyan Gong <[email protected]> Sent: 13 January 2026 10:28To:= [email protected] 6man <[email protected]> TEAS WG <[email protected]> IPv6 List <ip= [email protected]>Cc: Changwang Lin <[email protected]> Fenghua Ren <ren= [email protected]> Mingyu Wu <[email protected]> Peiyong Ma <mapeiy@chinatel= ecom.cn> Shay Zadok <[email protected]> Weiqiang Cheng <chengweiqiang= @chinamobile.com> Xuewei Wang <[email protected]>Subject: [Teas] Re= : New Version Notification for draft-cheng-spring-srv6-encoding-network-sli= ceid-12.txt =20 Dear All, =20 We have updated the individual draft **draft-cheng-spring-srv6-encoding-net= work-sliceid** to version **-12**. We would greatly appreciate your review and comments on this new revision. =20 This document describes a method to encode a Network Slice Identifier(NRP-I= D) within the outer IPv6 header of SRv6 packets. It enables routers along a path to identify the slice and apply specific fo= rwarding treatment, facilitating slice-aware traffic steering across an SRv= 6 domain.=20 The primary goal of this update is to refine the document39s clarity, addre= ss security considerations, and enhance its readiness for wider review.=20 =20 **Key updates in version -12 include:** =20 1. **Security Considerations Section:** Significantly expanded to define a= concrete trust model for the proposed encoding methods. It now includes a = threat analysis and discusses mitigation strategies relevant to operational= deployment. 2. **Clarification on SPI Encoding Options:** Enhanced descriptions for bo= th SPI encoding options (Traffic Class bit and Source Address prefix), with= a clearer comparison of their backward compatibility implications. 3. **Backward Compatibility Section:** Updated to more explicitly detail t= he deployment and interoperability characteristics of each SPI option, help= ing operators understand the migration path. 4. **Editorial Improvements:** Various text refinements, structure adjustm= ents, and typo fixes throughout the document to improve readability. =20 Furthermore, the proposed encoding mechanism has undergone practical valida= tion.It was successfully applied to realize "Link Slicing over SRv6" (use c= ase 3.21)in the 2024 MPLS&SDN Interoperability Test=EF=BC=88EANTC=EF=BC=89,= enabling cross-vendor source address slicing integration. The insights fro= m this implementation have informed the refinements in this document versio= n. =20 Following advice to socialize this work, we are sending this update to the = SPRING, 6MAN, and TEAS mailing lists.=20 Thank you for your time and consideration, looking forward to your feedback= . =20 Best Regards, Liyan =20 ----=E9=82=AE=E4=BB=B6=E5=8E=9F=E6=96=87----=E5=8F=91=E4=BB=B6=E4=BA=BA=EF= =BC=9Ainternet-drafts <[email protected]>=E6=94=B6=E4=BB=B6=E4=BA=BA= =EF=BC=9AChangwang Lin <[email protected]>,Fenghua Ren <renfh3@chi= naunicom.cn>,Liyan Gong <[email protected]>,Mingyu Wu <wumy@centec.= com>,Peiyong Ma <[email protected]>,Shay Zadok <[email protected]= m>,Weiqiang Cheng <[email protected]>,Xuewei Wang <wangxuewei1@= ruijie.com.cn>,xuewei wang <[email protected]>=E6=8A=84=E3=80=80=E9= =80=81: (=E6=97=A0)=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4=EF=BC=9A2026-01-13 = 18:00:24=E4=B8=BB=E9=A2=98=EF=BC=9ANew Version Notification for draft-cheng= -spring-srv6-encoding-network-sliceid-12.txtA new version of Internet-Draft= draft-cheng-spring-srv6-encoding-network-sliceid-12.txt has been successful= lysubmitted by Liyan Gong and posted to theIETF repository.Name: draft-= cheng-spring-srv6-encoding-network-sliceidRevision: 12Title: Encoding Ne= twork Slice Identification for SRv6Date: 2026-01-13Group: Individual= SubmissionPages: 10URL: https://www.ietf.org/archive/id/draft-chen= g-spring-srv6-encoding-network-sliceid-12.txtStatus: https://datatracker.= ietf.org/doc/draft-cheng-spring-srv6-encoding-network-sliceid/HTML: htt= ps://www.ietf.org/archive/id/draft-cheng-spring-srv6-encoding-network-slice= id-12.htmlHTMLized: https://datatracker.ietf.org/doc/html/draft-cheng-sprin= g-srv6-encoding-network-sliceidDiff: https://author-tools.ietf.org/iddi= ff?url2=3Ddraft-cheng-spring-srv6-encoding-network-sliceid-12Abstract: A = Network Resource Partition (NRP) is a subset of the network resources and= associated policies on each of a connected set of links in the underlay = network. An NRP could be used as the underlay to support one or a group = of enhanced VPN services. For packet forwarding in a specific NRP, some = fields in the data packet are used to identify the NRP the packet belongs= to, so that NRP-specific processing can be performed on each node along = a path in the NRP. This document describes a novel method to encode NRP-I= D in the outer IPv6 header of an SRv6 domain, which could be used to iden= tify the NRP-specific processing to be performed on the packets by each = network node along a network path in the NRP.The IETF SecretariatSubject= =EF=BC=9ANew Version Notification for draft-cheng-spring-srv6-encoding-netw= ork-sliceid-12.txtA new version of Internet-Draftdraft-cheng-spring-srv6-en= coding-network-sliceid-12.txt has been successfullysubmitted by Liyan Gong = and posted to theIETF repository.Name: draft-cheng-spring-srv6-encoding= -network-sliceidRevision: 12Title: Encoding Network Slice Identification= for SRv6Date: 2026-01-13Group: Individual SubmissionPages: 10URL= : https://www.ietf.org/archive/id/draft-cheng-spring-srv6-encoding-net= work-sliceid-12.txtStatus: https://datatracker.ietf.org/doc/draft-cheng-s= pring-srv6-encoding-network-sliceid/HTML: https://www.ietf.org/archive/= id/draft-cheng-spring-srv6-encoding-network-sliceid-12.htmlHTMLized: https:= //datatracker.ietf.org/doc/html/draft-cheng-spring-srv6-encoding-network-sl= iceidDiff: https://author-tools.ietf.org/iddiff?url2=3Ddraft-cheng-spri= ng-srv6-encoding-network-sliceid-12Abstract: A Network Resource Partition= (NRP) is a subset of the network resources and associated policies on ea= ch of a connected set of links in the underlay network. An NRP could be = used as the underlay to support one or a group of enhanced VPN services. = For packet forwarding in a specific NRP, some fields in the data packet = are used to identify the NRP the packet belongs to, so that NRP-specific = processing can be performed on each node along a path in the NRP. This = document describes a novel method to encode NRP-ID in the outer IPv6 head= er of an SRv6 domain, which could be used to identify the NRP-specific pr= ocessing to be performed on the packets by each network node along a netw= ork path in the NRP.The IETF Secretariat ------=_Part_301106_1680089663.1783502033052 Content-Type: text/html;charset=UTF-8 Content-Transfer-Encoding: quoted-printable <p style=3D"margin-top:5px;margin-right:0;margin-bottom:5px;margin-left:0;t= ext-indent:0"><span style=3D"font-family: =E5=AE=8B=E4=BD=93;letter-spacing= : 0;font-size: 14px">Dear Adrian and All,</span></p><p style=3D"margin-top:= 5px;margin-right:0;margin-bottom:5px;margin-left:0;text-indent:0"><span sty= le=3D"font-size: 14px; font-family: =E5=AE=8B=E4=BD=93; letter-spacing: 0px= ;">Thank you again for your valuable comments on the draft[1].</span><span = style=3D"font-size: 14px; font-family: =E5=AE=8B=E4=BD=93; letter-spacing: = 0px;"> </span></p><p style=3D"margin-top:5px;margin-right:0;margin-bot= tom:5px;margin-left:0;text-indent:0"><span style=3D"font-family: =E5=AE=8B= =E4=BD=93;letter-spacing: 0;font-size: 14px">As suggested, we have carefull= y reviewed the mature NRP-related documents to ensure our terminology and c= oncepts are fully aligned with the current framework. </span></p><p st= yle=3D"margin-top:5px;margin-right:0;margin-bottom:5px;margin-left:0;text-i= ndent:0"><span style=3D"font-size: 14px; font-family: =E5=AE=8B=E4=BD=93; l= etter-spacing: 0px;">Based on this review, we have updated the draft to ver= sion -13.</span></p><p style=3D"margin-top:5px;margin-right:0;margin-bottom= :5px;margin-left:0;text-indent:0"><span style=3D"font-family: =E5=AE=8B=E4= =BD=93;letter-spacing: 0;font-size: 14px"><br/></span></p><p style=3D"margi= n-top:5px;margin-right:0;margin-bottom:5px;margin-left:0;text-indent:0"><st= rong><span style=3D"font-family: =E5=AE=8B=E4=BD=93;letter-spacing: 0;font-= size: 14px"><span style=3D"font-family: SimSun; font-size: 14px;">Key updat= es in version -13 include:</span></span></strong></p><p style=3D"margin-top= : 5px;margin-right: 0;margin-bottom: 5px"><span style=3D"font-family: =E5= =AE=8B=E4=BD=93;letter-spacing: 0;font-size: 14px">1. Terminology Alignment= </span><span style=3D"font-family: =E5=AE=8B=E4=BD=93;letter-spacing: 0;fon= t-size: 14px">:</span><span style=3D"font-family: =E5=AE=8B=E4=BD=93;letter= -spacing: 0;font-size: 14px"> </span><span style=3D"font-family: =E5= =AE=8B=E4=BD=93;letter-spacing: 0;font-size: 14px">Terminology has been upd= ated throughout the document to align with the definitions in RFC 9543 and<= /span> <span style=3D"font-family: =E5=AE=8B=E4=BD=93;letter-spacing: 0;fon= t-size: 14px">draft-ietf-teas-ns-ip-mpls</span><span style=3D"font-family: = =E5=AE=8B=E4=BD=93;letter-spacing: 0;font-size: 14px">.</span></p><p style= =3D"margin-top:5px;margin-right:0;margin-bottom:5px"><span style=3D"font-fa= mily: =E5=AE=8B=E4=BD=93;letter-spacing: 0;font-size: 14px">1) </span><span= style=3D"font-family: =E5=AE=8B=E4=BD=93;letter-spacing: 0;font-size: 14px= ">The data plane identifier previously referred to as "SLID" is n= ow consistently called the "NRP Selector Identifier", </span></p>= <p style=3D"margin-top:5px;margin-right:0;margin-bottom:5px"><span style=3D= "font-family: =E5=AE=8B=E4=BD=93;letter-spacing: 0;font-size: 14px">2) </sp= an><span style=3D"font-family: =E5=AE=8B=E4=BD=93;letter-spacing: 0;font-si= ze: 14px">T</span><span style=3D"font-family: =E5=AE=8B=E4=BD=93;letter-spa= cing: 0;font-size: 14px">he presence indicator has been renamed from "= SPI" to "NPI". </span></p><p style=3D"margin-top:5px;margin-= right:0;margin-bottom:5px"><span style=3D"font-family: =E5=AE=8B=E4=BD=93;l= etter-spacing: 0;font-size: 14px">3) </span><span style=3D"font-family: =E5= =AE=8B=E4=BD=93;letter-spacing: 0;font-size: 14px">The terminology section = now includes formal definitions for "NRP Selector" and "NRP = Selector Identifier" with proper references.</span></p><p style=3D"mar= gin-top:5px;margin-right:0;margin-bottom:5px"><span style=3D"font-family: = =E5=AE=8B=E4=BD=93;letter-spacing: 0;font-size: 14px">2. Scope Clarificatio= n:</span><span style=3D"font-family: =E5=AE=8B=E4=BD=93;letter-spacing: 0;f= ont-size: 14px"> We have made it clear that the document focuses solely on = encoding the NRP Selector ID in the outer IPv6 header, and that the mapping= from a specific slice to an NRP is outside the scope of this draft</span><= span style=3D"font-family: =E5=AE=8B=E4=BD=93;letter-spacing: 0;font-size: = 14px">.</span></p><p style=3D"margin-top:5px;margin-right:0;margin-bottom:5= px;margin-left:0;text-indent:0"><span style=3D"font-family: =E5=AE=8B=E4=BD= =93;letter-spacing: 0;font-size: 14px"> </span></p><p style=3D"margin-= top:5px;margin-right:0;margin-bottom:5px;margin-left:0;text-indent:0"><span= style=3D"font-family: =E5=AE=8B=E4=BD=93;letter-spacing: 0;font-size: 14px= ">We </span><span style=3D"font-family: =E5=AE=8B=E4=BD=93;letter-spacing: = 0;font-size: 14px">hope </span><span style=3D"font-family: =E5=AE=8B=E4=BD= =93;letter-spacing: 0;font-size: 14px">these changes address the concerns r= aised and make the document more aligned with the broader TEAS framework. W= e wou</span><span style=3D"font-family: =E5=AE=8B=E4=BD=93;letter-spacing: = 0;font-size: 14px">ld appreciate fu</span><span style=3D"font-family: =E5= =AE=8B=E4=BD=93;letter-spacing: 0;font-size: 14px">rther review and comment= s.</span></p><p style=3D"margin-top:5px;margin-right:0;margin-bottom:5px;ma= rgin-left:0;text-indent:0"><span style=3D"font-family: =E5=AE=8B=E4=BD=93;l= etter-spacing: 0;font-size: 14px"><br/></span></p><p style=3D"margin-top:5p= x;margin-right:0;margin-bottom:5px;margin-left:0;text-indent:0"><strong><sp= an style=3D"font-family: =E5=AE=8B=E4=BD=93;letter-spacing: 0;font-size: 14= px">[1]Th</span></strong><span style=3D"font-family: =E5=AE=8B=E4=BD=93;let= ter-spacing: 0;font-size: 14px"><strong>e draft link information is as foll= ows=EF=BC=9A</strong></span></p><p style=3D"margin: 5px 0px; text-indent: 0= px; text-align: left;"><span style=3D"font-family: =E5=AE=8B=E4=BD=93;lette= r-spacing: 0;font-size: 14px">URL: https://www.ietf.org/archive/id/draft-ch= eng-spring-srv6-encoding-network-sliceid-13.txt<br style=3D"font-family: &q= uot;=E5=AE=8B=E4=BD=93,NSimSun,SimSun"; font-size: 14px; white-space: = normal;"/>Status: https://datatracker.ietf.org/doc/draft-cheng-spring-srv6-= encoding-network-sliceid/<br style=3D"font-family: "=E5=AE=8B=E4=BD=93= ,NSimSun,SimSun"; font-size: 14px; white-space: normal;"/>HTML: https:= //www.ietf.org/archive/id/draft-cheng-spring-srv6-encoding-network-sliceid-= 13.html<br style=3D"font-family: "=E5=AE=8B=E4=BD=93,NSimSun,SimSun&qu= ot;; font-size: 14px; white-space: normal;"/>HTMLized: https://datatracker.= ietf.org/doc/html/draft-cheng-spring-srv6-encoding-network-sliceid<br style= =3D"font-family: "=E5=AE=8B=E4=BD=93,NSimSun,SimSun"; font-size: = 14px; white-space: normal;"/>Diff: https://author-tools.ietf.org/iddiff?url= 2=3Ddraft-cheng-spring-srv6-encoding-network-sliceid-13</span></p><p style= =3D"margin-top:5px;margin-right:0;margin-bottom:5px;margin-left:0;text-inde= nt:0"><span style=3D"font-family: =E5=AE=8B=E4=BD=93;letter-spacing: 0;font= -size: 14px"> </span></p><p style=3D"margin-top:5px;margin-right:0;mar= gin-bottom:5px;margin-left:0;text-indent:0"><span style=3D"font-family: =E5= =AE=8B=E4=BD=93;letter-spacing: 0;font-size: 14px">Best Regards,</span></p>= <p style=3D"margin-top:5px;margin-right:0;margin-bottom:5px;margin-left:0;t= ext-indent:0"><span style=3D"font-family: =E5=AE=8B=E4=BD=93;letter-spacing= : 0;font-size: 14px">Liyan(on behalf of co-authors)</span></p><p style=3D"m= argin-top:5px;margin-right:0;margin-bottom:5px;margin-left:0;text-indent:0"= ><span style=3D"font-family: =E5=AE=8B=E4=BD=93;letter-spacing: 0;font-size= : 14px"><br/></span></p><!-- block name=3D"headerinfo" --><blockquote id=3D= "oriMsgHtmlSeperator" style=3D" MARGIN: 0px 0px 0px 0.8ex; ">----=E9=82=AE= =E4=BB=B6=E5=8E=9F=E6=96=87----<br/><strong>=E5=8F=91=E4=BB=B6=E4=BA=BA=EF= =BC=9A</strong>Liyan Gong <[email protected]>= <br/><strong>=E6=94=B6=E4=BB=B6=E4=BA=BA=EF=BC=9A</strong>adrian  = ;<[email protected]>,spring <[email protected]>,6man= <[email protected]>,TEAS WG <[email protected]= >,IPv6 List <[email protected]><br/><strong>=E6=8A=84= =E3=80=80=E9=80=81: </strong>Changwang Lin <linchangwang= [email protected]>,Fenghua Ren <[email protected]>= ;,Mingyu Wu <[email protected]>,Peiyong Ma &n= bsp;<[email protected]>,Shay Zadok <shay.zado= [email protected]>,Weiqiang Cheng <chengweiqiang@chinamo= bile.com>,Xuewei Wang <[email protected]><= br/><strong>=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4=EF=BC=9A</strong>2026-01-1= 4 18:39:33<br/><strong>=E4=B8=BB=E9=A2=98=EF=BC=9A</strong>[Teas] Re:&= nbsp;New Version Notification fordraft-cheng-spring-srv6-enc= oding-network-sliceid-12.txt<br/><br/><p>Dear Adrian,</p><p><span style=3D"= font-size: 16.0px;"><br/></span></p><p><span style=3D"font-size: 16.0px;">T= hank you for your valuable feedback.</span></p><p><br/></p><p><span style= =3D"font-size: 16.0px;">We will carefully review RFC 9543 and the related d= rafts to better align the terminology and refine the positioning of our wor= k.</span></p><p><span style=3D"font-size: 16.0px;"><br/></span></p><p><span= style=3D"font-size: 16.0px;">Once We have a clearer revision plan, We will= follow up for further discussion.<br/></span></p><p><br/></p><p><span styl= e=3D"font-size: 16.0px;">Best regards, </span></p><p><span style= =3D"">Liyan</span></p><p><span style=3D""><br/></span></p><p><span style=3D= ""><br/></span></p><blockquote id=3D"oriMsgHtmlSeperator" style=3D"MARGIN: = 0.0px 0.0px 0.0px 0.8ex;">----=E9=82=AE=E4=BB=B6=E5=8E=9F=E6=96=87----<br/>= <strong>=E5=8F=91=E4=BB=B6=E4=BA=BA=EF=BC=9A</strong>Adrian Farrel&nbs= p;<[email protected]><br/><strong>=E6=94=B6=E4=BB=B6=E4=BA=BA=EF=BC= =9A</strong>'Liyan Gong' <[email protected]>= ;,spring <[email protected]>,'6man' <[email protected]= >,'TEAS WG' <[email protected]>,'IPv6 List&= #39; <[email protected]><br/><strong>=E6=8A=84=E3=80=80=E9=80=81: </= strong>'Changwang Lin' <[email protected]>= ,'Fenghua Ren' <[email protected]>,'Mingyu&= nbsp;Wu' <[email protected]>,'Peiyong Ma' &l= t;[email protected]>,'Shay Zadok' <shay.zadok@= broadcom.com>,'Weiqiang Cheng' <chengweiqiang@china= mobile.com>,'Xuewei Wang' <[email protected]= n><br/><strong>=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4=EF=BC=9A</strong>202= 6-01-13 20:08:54<br/><strong>=E4=B8=BB=E9=A2=98=EF=BC=9A</strong>RE: [= Teas] Re: New Version Notification for draft-= cheng-spring-srv6-encoding-network-sliceid-12.txt<br/><br/><div class=3D"Wo= rdSection1"><p class=3D"MsoNormal"><span style=3D"font-size: 11.0pt;font-fa= mily: Calibri , sans-serif;">Hello,</span></p><p class=3D"MsoNormal"><span = style=3D"font-size: 11.0pt;font-family: Calibri , sans-serif;"> </span= ></p><p class=3D"MsoNormal"><span style=3D"font-size: 11.0pt;font-family: C= alibri , sans-serif;">Thanks for continuing to work on your draft.</span></= p><p class=3D"MsoNormal"><span style=3D"font-size: 11.0pt;font-family: Cali= bri , sans-serif;"> </span></p><p class=3D"MsoNormal"><span style=3D"f= ont-size: 11.0pt;font-family: Calibri , sans-serif;">I think it would be re= ally helpful to try to align your terminology with other work on network sl= icing.</span></p><p class=3D"MsoNormal"><span style=3D"font-size: 11.0pt;fo= nt-family: Calibri , sans-serif;"> </span></p><p class=3D"MsoNormal"><= span style=3D"font-size: 11.0pt;font-family: Calibri , sans-serif;">For exa= mple:</span></p><ul style=3D"margin: 0px; padding: 0px 0px 0px 30px; width:= 95%;" class=3D" list-paddingleft-2"><li style=3D"background-position: 0px = 3px; background-repeat: no-repeat; clear: both;"><p><span style=3D"font-siz= e: 11.0pt;font-family: Calibri , sans-serif;">A network slice and a network= resource partition are not the same thing (RFC 9543). So a slice ID and an= NRP ID are different. While it might be possible to have a 1:1 mapping bet= ween slice and NRP, this is unlikely to be normal.</span></p></li><li style= =3D"background-position: 0px 3px; background-repeat: no-repeat; clear: both= ;"><p><span style=3D"font-size: 11.0pt;font-family: Calibri , sans-serif;">= There may be a difference between a network resource partition identifier (= NRP-ID) and a network resource partition selector identifier (NRPS ID) (dra= ft-ietf-teas-nrp-scalability section 5.2 and draft-ietf-teas-ns-ip-mpls)</s= pan></p></li></ul><p class=3D"MsoNormal"><span style=3D"font-size: 11.0pt;f= ont-family: Calibri , sans-serif;"> </span></p><p class=3D"MsoNormal">= <span style=3D"font-size: 11.0pt;font-family: Calibri , sans-serif;">It mig= ht also be useful to look at drafts that already exist and have been adopte= d by working groups to discover where you are =E2=80=9Ccompeting=E2=80=9D w= ith existing IETF work and where you supplement it.</span></p><p class=3D"M= soNormal"><span style=3D"font-size: 11.0pt;font-family: Calibri , sans-seri= f;"> </span></p><p class=3D"MsoNormal"><span style=3D"font-size: 11.0p= t;font-family: Calibri , sans-serif;">Cheers,</span></p><p class=3D"MsoNorm= al"><span style=3D"font-size: 11.0pt;font-family: Calibri , sans-serif;">Ad= rian</span></p><p class=3D"MsoNormal"><span style=3D"font-size: 11.0pt;font= -family: Calibri , sans-serif;"> </span></p><div style=3D"border: none= ;border-top: solid rgb(225,225,225) 1.0pt;padding: 3.0pt 0.0cm 0.0cm 0.0cm;= "><p class=3D"MsoNormal"><strong><span style=3D"font-size: 11.0pt;font-fami= ly: Calibri , sans-serif;">From:</span></strong><span style=3D"font-size: 1= 1.0pt;font-family: Calibri , sans-serif;"> Liyan Gong <gongliyan@chinamo= bile.com> <br/><strong>Sent:</strong> 13 January 2026 10:28<br/><strong>= To:</strong> [email protected]; 6man <[email protected]>; TEAS WG <teas@= ietf.org>; IPv6 List <[email protected]><br/><strong>Cc:</strong> Chan= gwang Lin <[email protected]>; Fenghua Ren <renfh3@chinau= nicom.cn>; Mingyu Wu <[email protected]>; Peiyong Ma <mapeiy@chin= atelecom.cn>; Shay Zadok <[email protected]>; Weiqiang Cheng= <[email protected]>; Xuewei Wang <wangxuewei1@ruijie.= com.cn><br/><strong>Subject:</strong> [Teas] Re: New Version Notificatio= n for draft-cheng-spring-srv6-encoding-network-sliceid-12.txt</span></p></d= iv><p class=3D"MsoNormal"> </p><p><span style=3D"font-size: 10.5pt;fon= t-family: SimSun;">Dear All,</span></p><p style=3D""><span style=3D"font-si= ze: 10.5pt;font-family: SimSun;"> </span></p><p style=3D""><span style= =3D"font-size: 10.5pt;font-family: SimSun;">We have updated the individual = draft **draft-cheng-spring-srv6-encoding-network-sliceid** to version **-12= **.</span></p><p style=3D""><span style=3D"font-size: 10.5pt;font-family: S= imSun;">We would greatly appreciate your review and comments on this new re= vision.</span></p><p style=3D""> </p><p style=3D""><span style=3D"font= -size: 10.5pt;font-family: SimSun;">This document describes a method to enc= ode a Network Slice Identifier(NRP-ID) within the outer IPv6 header of SRv6= packets.</span></p><p style=3D""><span style=3D"font-size: 10.5pt;font-fam= ily: SimSun;">It enables routers along a path to identify the slice and app= ly specific forwarding treatment, facilitating slice-aware traffic steering= across an SRv6 domain. </span></p><p style=3D""><span style=3D"font-s= ize: 10.5pt;font-family: SimSun;">The primary goal of this update is to ref= ine the document's clarity, address security considerations, and enhanc= e its readiness for wider review. </span></p><p style=3D""><span style= =3D"font-size: 10.5pt;font-family: SimSun;"> </span></p><p style=3D"">= <span style=3D"font-size: 10.5pt;font-family: SimSun;">**Key updates in ver= sion -12 include:**</span></p><p style=3D""><span style=3D"font-size: 10.5p= t;font-family: SimSun;"> </span></p><p style=3D""><span style=3D"font-= size: 10.5pt;font-family: SimSun;">1. **Security Considerations Secti= on:** Significantly expanded to define a concrete trust model for the propo= sed encoding methods. It now includes a threat analysis and discusses mitig= ation strategies relevant to operational deployment.</span></p><p style=3D"= "><span style=3D"font-size: 10.5pt;font-family: SimSun;">2. **Clarifi= cation on SPI Encoding Options:** Enhanced descriptions for both SPI encodi= ng options (Traffic Class bit and Source Address prefix), with a clearer co= mparison of their backward compatibility implications.</span></p><p style= =3D""><span style=3D"font-size: 10.5pt;font-family: SimSun;">3. **Bac= kward Compatibility Section:** Updated to more explicitly detail the deploy= ment and interoperability characteristics of each SPI option, helping opera= tors understand the migration path.</span></p><p style=3D""><span style=3D"= font-size: 10.5pt;font-family: SimSun;">4. **Editorial Improvements:*= * Various text refinements, structure adjustments, and typo fixes throughou= t the document to improve readability.</span></p><p style=3D""><span style= =3D"font-size: 10.5pt;font-family: SimSun;"> </span></p><p style=3D"">= <span style=3D"font-size: 10.5pt;font-family: SimSun;">Furthermore, the pro= posed encoding mechanism has undergone practical validation.It was successf= ully applied to realize "Link Slicing over SRv6" (use case 3= .21)in the 2024 MPLS&SDN Interoperability Test=EF=BC=88EANTC=EF=BC=89, = enabling cross-vendor source address slicing integration. The insights from= this implementation have informed the refinements in this document version= .</span></p><p style=3D""> </p><p style=3D""><span style=3D"font-size:= 10.5pt;font-family: SimSun;color: #0F1115;background: white;">Following ad= vice to socialize this work, we are sending this update to the SPRING, 6MAN= , and TEAS mailing lists.</span><span style=3D"font-size: 10.5pt;font-famil= y: SimSun;"> </span></p><p style=3D""><span style=3D"font-size: 10.5pt= ;font-family: SimSun;">Thank you for your time and consideration, looking f= orward to your feedback.</span></p><p style=3D""><span style=3D"font-size: = 8.5pt;font-family: "Segoe UI" , sans-serif;color: #0F1115;backgro= und: white;"> </span></p><p style=3D""><span style=3D"font-size: 10.5p= t;font-family: SimSun;">Best Regards,</span></p><p style=3D""><span style= =3D"font-size: 10.5pt;font-family: SimSun;">Liyan</span></p><p> </p><p= style=3D"margin-bottom: 12.0pt;">----<span style=3D"font-family: "Mic= rosoft JhengHei" , sans-serif;">=E9=82=AE=E4=BB=B6=E5=8E=9F=E6=96=87</= span>----<br/><span style=3D"font-family: "Microsoft JhengHei" , = sans-serif;">=E5=8F=91=E4=BB=B6=E4=BA=BA=EF=BC=9A</span>internet-drafts&nbs= p;<<a href=3D"mailto:[email protected]">[email protected]<= /a>><br/><span style=3D"font-family: "MS Gothic";">=E6=94=B6= =E4=BB=B6=E4=BA=BA=EF=BC=9A</span>Changwang Lin <<a href=3D"ma= ilto:[email protected]">[email protected]</a>>,Fenghua= Ren <<a href=3D"mailto:[email protected]">renfh3@chinauni= com.cn</a>>,Liyan Gong <<a href=3D"mailto:gongliyan@chinamo= bile.com">[email protected]</a>>,Mingyu Wu <<a href= =3D"mailto:[email protected]">[email protected]</a>>,Peiyong Ma &l= t;<a href=3D"mailto:[email protected]">[email protected]</a>>,= Shay Zadok <<a href=3D"mailto:[email protected]">shay.za= [email protected]</a>>,Weiqiang Cheng <<a href=3D"mailto:che= [email protected]">[email protected]</a>>,Xuewei&nb= sp;Wang <<a href=3D"mailto:[email protected]">wangxuewei1@r= uijie.com.cn</a>>,xuewei wang <<a href=3D"mailto:wangxuewei= [email protected]">[email protected]</a>><br/><span style=3D"font-= family: "MS Gothic";">=E6=8A=84=E3=80=80=E9=80=81</span>: (<= span style=3D"font-family: "MS Gothic";">=E6=97=A0</span>)<br/><s= pan style=3D"font-family: "Microsoft JhengHei" , sans-serif;">=E5= =8F=91=E9=80=81=E6=97=B6=E9=97=B4=EF=BC=9A</span>2026-01-13 18:00:24<b= r/><span style=3D"font-family: "MS Gothic";">=E4=B8=BB</span><spa= n style=3D"font-family: "Microsoft JhengHei" , sans-serif;">=E9= =A2=98=EF=BC=9A</span>New Version Notification for draf= t-cheng-spring-srv6-encoding-network-sliceid-12.txt<br/><br/>A new&nbs= p;version of Internet-Draft<br/>draft-cheng-spring-srv6-encoding-= network-sliceid-12.txt has been successfully<br/>submitted&n= bsp;by Liyan Gong and posted to the<br/>IETF&= nbsp;repository.<br/><br/>Name: draft-cheng-sp= ring-srv6-encoding-network-sliceid<br/>Revision: 12<br/>Title: &n= bsp; Encoding Network Slice Identification f= or SRv6<br/>Date: 2026-01-13<br/>Group:&n= bsp; Individual Submission<br/>Pages: &nbs= p; 10<br/>URL: <a href=3D"https://w= ww.ietf.org/archive/id/draft-cheng-spring-srv6-encoding-network-sliceid-12.= txt">https://www.ietf.org/archive/id/draft-cheng-spring-srv6-encoding-netwo= rk-sliceid-12.txt</a><br/>Status: <a href=3D"https://datat= racker.ietf.org/doc/draft-cheng-spring-srv6-encoding-network-sliceid/">http= s://datatracker.ietf.org/doc/draft-cheng-spring-srv6-encoding-network-slice= id/</a><br/>HTML: <a href=3D"https://www.ietf.= org/archive/id/draft-cheng-spring-srv6-encoding-network-sliceid-12.html">ht= tps://www.ietf.org/archive/id/draft-cheng-spring-srv6-encoding-network-slic= eid-12.html</a><br/>HTMLized: <a href=3D"https://datatracker.ietf.org/= doc/html/draft-cheng-spring-srv6-encoding-network-sliceid">https://datatrac= ker.ietf.org/doc/html/draft-cheng-spring-srv6-encoding-network-sliceid</a><= br/>Diff: <a href=3D"https://author-tools.ietf= .org/iddiff?url2=3Ddraft-cheng-spring-srv6-encoding-network-sliceid-12">htt= ps://author-tools.ietf.org/iddiff?url2=3Ddraft-cheng-spring-srv6-encoding-n= etwork-sliceid-12</a><br/><br/>Abstract:<br/><br/> A = Network Resource Partition (NRP) is a subset&= nbsp;of the network<br/> resources and = ;associated policies on each of a connected&n= bsp;set of links<br/> in the underlay&= nbsp;network. An NRP could be used as&n= bsp;the underlay to<br/> support one o= r a group of enhanced VPN services. &nbs= p;For packet<br/> forwarding in a spec= ific NRP, some fields in the data packet= are used<br/> to identify the NR= P the packet belongs to, so that NRP-spe= cific<br/> processing can be performed = ;on each node along a path in the N= RP.<br/><br/> This document describes a&nbs= p;novel method to encode NRP-ID in the o= uter<br/> IPv6 header of an SRv6 = domain, which could be used to identify = the<br/> NRP-specific processing to be = ;performed on the packets by each<br/> = network node along a network path in&nb= sp;the NRP.<br/><br/><br/><br/>The IETF Secretariat<br/><br/= ><br/><br/>Subject<span style=3D"font-family: "MS Gothic";">=EF= =BC=9A</span>New Version Notification for draft-cheng-s= pring-srv6-encoding-network-sliceid-12.txt<br/><br/>A new version= of Internet-Draft<br/>draft-cheng-spring-srv6-encoding-network-s= liceid-12.txt has been successfully<br/>submitted by&nb= sp;Liyan Gong and posted to the<br/>IETF repo= sitory.<br/><br/>Name: draft-cheng-spring-srv6= -encoding-network-sliceid<br/>Revision: 12<br/>Title:  = ; Encoding Network Slice Identification for S= Rv6<br/>Date: 2026-01-13<br/>Group:  = ; Individual Submission<br/>Pages: 1= 0<br/>URL: <a href=3D"https://www.ietf.o= rg/archive/id/draft-cheng-spring-srv6-encoding-network-sliceid-12.txt">http= s://www.ietf.org/archive/id/draft-cheng-spring-srv6-encoding-network-slicei= d-12.txt</a><br/>Status: <a href=3D"https://datatracker.ie= tf.org/doc/draft-cheng-spring-srv6-encoding-network-sliceid/">https://datat= racker.ietf.org/doc/draft-cheng-spring-srv6-encoding-network-sliceid/</a><b= r/>HTML: <a href=3D"https://www.ietf.org/archi= ve/id/draft-cheng-spring-srv6-encoding-network-sliceid-12.html">https://www= .ietf.org/archive/id/draft-cheng-spring-srv6-encoding-network-sliceid-12.ht= ml</a><br/>HTMLized: <a href=3D"https://datatracker.ietf.org/doc/html/= draft-cheng-spring-srv6-encoding-network-sliceid">https://datatracker.ietf.= org/doc/html/draft-cheng-spring-srv6-encoding-network-sliceid</a><br/>Diff:= <a href=3D"https://author-tools.ietf.org/iddi= ff?url2=3Ddraft-cheng-spring-srv6-encoding-network-sliceid-12">https://auth= or-tools.ietf.org/iddiff?url2=3Ddraft-cheng-spring-srv6-encoding-network-sl= iceid-12</a><br/><br/>Abstract:<br/><br/> A Network&n= bsp;Resource Partition (NRP) is a subset of&n= bsp;the network<br/> resources and associat= ed policies on each of a connected set&n= bsp;of links<br/> in the underlay netw= ork. An NRP could be used as the&n= bsp;underlay to<br/> support one or a&= nbsp;group of enhanced VPN services. For&nbs= p;packet<br/> forwarding in a specific = ;NRP, some fields in the data packet are= used<br/> to identify the NRP th= e packet belongs to, so that NRP-specific<br/= > processing can be performed on = each node along a path in the NRP.<br/><= br/> This document describes a novel&n= bsp;method to encode NRP-ID in the outer<br/>= IPv6 header of an SRv6 domain,&n= bsp;which could be used to identify the<br/>&= nbsp; NRP-specific processing to be performe= d on the packets by each<br/> net= work node along a network path in the&nb= sp;NRP.<br/><br/><br/><br/>The IETF Secretariat<br/><br/><br/></p= ></div></blockquote><p><br/></p></blockquote><!-- endblock name=3D"headerin= fo" --><p><br/></p> ------=_Part_301106_1680089663.1783502033052-- --===============3137679879358640411== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18Kc3ByaW5nIG1h aWxpbmcgbGlzdCAtLSBzcHJpbmdAaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFp bCB0byBzcHJpbmctbGVhdmVAaWV0Zi5vcmcK --===============3137679879358640411==--