[spring] Re: [Teas] Re: New Version Notification fordr aft-cheng-spring-srv6-encoding-network-sliceid-12.txt
Liyan Gong <[email protected]> Wed, 14 Jan 2026 18:39:33 +0800 (CST)
| Newsgroups | gmane.ietf.spring,gmane.ietf.ipv6 |
|---|---|
| Message-ID | <2b06696736dd16f-000f0.Richmail.00002062252930706037@chinamobile.com> |
--===============4462304096674139265== Content-Type: multipart/alternative; boundary="----=_Part_832544_331956354.1768387173737" ------=_Part_832544_331956354.1768387173737 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: quoted-printable Dear 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_832544_331956354.1768387173737 Content-Type: text/html;charset=UTF-8 Content-Transfer-Encoding: quoted-printable <p>Dear Adrian,</p><p><span style=3D"font-size: 16.0px;"><br/></span></p><p= ><span style=3D"font-size: 16.0px;">Thank you for your valuable feedback.</= span></p><p><br/></p><p><span style=3D"font-size: 16.0px;">We will carefull= y review RFC 9543 and the related drafts to better align the terminology an= d refine the positioning of our work.</span></p><p><span style=3D"font-size= : 16.0px;"><br/></span></p><p><span style=3D"font-size: 16.0px;">Once We ha= ve a clearer revision plan, We will follow up for further discussion.<br/><= /span></p><p><br/></p><p><span style=3D"font-size: 16.0px;">Best regards,&n= bsp; </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"ori= MsgHtmlSeperator" 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 <[email protected]><br/><str= ong>=E6=94=B6=E4=BB=B6=E4=BA=BA=EF=BC=9A</strong>'Liyan Gong'&= nbsp;<[email protected]>,spring <[email protected]>,= '6man' <[email protected]>,'TEAS WG' <t= [email protected]>,'IPv6 List' <[email protected]><br/><s= trong>=E6=8A=84=E3=80=80=E9=80=81: </strong>'Changwang Lin'&nb= sp;<[email protected]>,'Fenghua Ren' <r= [email protected]>,'Mingyu Wu' <[email protected]&= gt;,'Peiyong Ma' <[email protected]>,'Shay= Zadok' <[email protected]>,'Weiqiang Ch= eng' <[email protected]>,'Xuewei Wang&#= 39; <[email protected]><br/><strong>=E5=8F=91=E9=80=81= =E6=97=B6=E9=97=B4=EF=BC=9A</strong>2026-01-13 20:08:54<br/><strong>=E4=B8= =BB=E9=A2=98=EF=BC=9A</strong>RE: [Teas] Re: New Versio= n Notification for draft-cheng-spring-srv6-encoding-network-= sliceid-12.txt<br/><br/><div class=3D"WordSection1"><p class=3D"MsoNormal">= <span style=3D"font-size: 11.0pt;font-family: Calibri , sans-serif;">Hello,= </span></p><p class=3D"MsoNormal"><span style=3D"font-size: 11.0pt;font-fam= ily: Calibri , sans-serif;"> </span></p><p class=3D"MsoNormal"><span s= tyle=3D"font-size: 11.0pt;font-family: Calibri , sans-serif;">Thanks for co= ntinuing to work on your draft.</span></p><p class=3D"MsoNormal"><span styl= e=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: Calib= ri , sans-serif;">I think it would be really helpful to try to align your t= erminology with other work on network slicing.</span></p><p class=3D"MsoNor= mal"><span style=3D"font-size: 11.0pt;font-family: Calibri , sans-serif;">&= nbsp;</span></p><p class=3D"MsoNormal"><span style=3D"font-size: 11.0pt;fon= t-family: Calibri , sans-serif;">For example:</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-size: 11.0pt;font-family: Calibri , sa= ns-serif;">A network slice and a network resource partition are not the sam= e thing (RFC 9543). So a slice ID and an NRP ID are different. While it mig= ht be possible to have a 1:1 mapping between slice and NRP, this is unlikel= y to be normal.</span></p></li><li style=3D"background-position: 0px 3px; b= ackground-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 part= ition selector identifier (NRPS ID) (draft-ietf-teas-nrp-scalability sectio= n 5.2 and draft-ietf-teas-ns-ip-mpls)</span></p></li></ul><p class=3D"MsoNo= rmal"><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;fo= nt-family: Calibri , sans-serif;">It might also be useful to look at drafts= that already exist and have been adopted by working groups to discover whe= re you are =E2=80=9Ccompeting=E2=80=9D with existing IETF work and where yo= u supplement it.</span></p><p class=3D"MsoNormal"><span style=3D"font-size:= 11.0pt;font-family: Calibri , sans-serif;"> </span></p><p class=3D"Ms= oNormal"><span style=3D"font-size: 11.0pt;font-family: Calibri , sans-serif= ;">Cheers,</span></p><p class=3D"MsoNormal"><span style=3D"font-size: 11.0p= t;font-family: Calibri , sans-serif;">Adrian</span></p><p class=3D"MsoNorma= l"><span style=3D"font-size: 11.0pt;font-family: Calibri , sans-serif;">&nb= sp;</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><s= pan style=3D"font-size: 11.0pt;font-family: Calibri , sans-serif;">From:</s= pan></strong><span style=3D"font-size: 11.0pt;font-family: Calibri , sans-s= erif;"> Liyan Gong <[email protected]> <br/><strong>Sent:</st= rong> 13 January 2026 10:28<br/><strong>To:</strong> [email protected]; 6man = <[email protected]>; TEAS WG <[email protected]>; IPv6 List <ipv6@ie= tf.org><br/><strong>Cc:</strong> Changwang Lin <linchangwang.04414@h3= c.com>; Fenghua Ren <[email protected]>; Mingyu Wu <wumy@ce= ntec.com>; Peiyong Ma <[email protected]>; Shay Zadok <sha= [email protected]>; Weiqiang Cheng <[email protected]&= gt;; Xuewei Wang <[email protected]><br/><strong>Subject:</st= rong> [Teas] Re: New Version Notification for draft-cheng-spring-srv6-encod= ing-network-sliceid-12.txt</span></p></div><p class=3D"MsoNormal"> </p= ><p><span style=3D"font-size: 10.5pt;font-family: SimSun;">Dear All,</span>= </p><p style=3D""><span style=3D"font-size: 10.5pt;font-family: SimSun;">&n= bsp;</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-enc= oding-network-sliceid** to version **-12**.</span></p><p style=3D""><span s= tyle=3D"font-size: 10.5pt;font-family: SimSun;">We would greatly appreciate= your review and comments on this new revision.</span></p><p style=3D"">&nb= sp;</p><p style=3D""><span style=3D"font-size: 10.5pt;font-family: SimSun;"= >This document describes a method to encode 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-family: SimSun;">It enables routers al= ong a path to identify the slice and apply specific forwarding treatment, f= acilitating slice-aware traffic steering across an SRv6 domain. </span= ></p><p style=3D""><span style=3D"font-size: 10.5pt;font-family: SimSun;">T= he primary goal of this update is to refine the document's clarity, add= ress security considerations, and enhance its readiness for wider review.&n= bsp;</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;fo= nt-family: SimSun;">**Key updates in version -12 include:**</span></p><p st= yle=3D""><span style=3D"font-size: 10.5pt;font-family: SimSun;"> </spa= n></p><p style=3D""><span style=3D"font-size: 10.5pt;font-family: SimSun;">= 1. **Security Considerations Section:** Significantly expanded to def= ine a concrete trust model for the proposed encoding methods. It now includ= es a threat analysis and discusses mitigation strategies relevant to operat= ional deployment.</span></p><p style=3D""><span style=3D"font-size: 10.5pt;= font-family: SimSun;">2. **Clarification on SPI Encoding Options:** E= nhanced descriptions for both SPI encoding options (Traffic Class bit and S= ource Address prefix), with a clearer comparison of their backward compatib= ility implications.</span></p><p style=3D""><span style=3D"font-size: 10.5p= t;font-family: SimSun;">3. **Backward Compatibility Section:** Update= d to more explicitly detail the deployment and interoperability characteris= tics of each SPI option, helping operators 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 throughout the document to improve readability= .</span></p><p style=3D""><span style=3D"font-size: 10.5pt;font-family: Sim= Sun;"> </span></p><p style=3D""><span style=3D"font-size: 10.5pt;font-= family: SimSun;">Furthermore, the proposed encoding mechanism has undergone= practical validation.It was successfully applied to realize "Lin= k Slicing over SRv6" (use case 3.21)in the 2024 MPLS&SDN Interoper= ability Test=EF=BC=88EANTC=EF=BC=89, enabling cross-vendor source address s= licing 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: #0F= 1115;background: white;">Following advice to socialize this work, we are se= nding this update to the SPRING, 6MAN, and TEAS mailing lists.</span><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;">Thank you for = your time and consideration, looking forward to your feedback.</span></p><p= style=3D""><span style=3D"font-size: 8.5pt;font-family: "Segoe UI&quo= t; , sans-serif;color: #0F1115;background: white;"> </span></p><p styl= e=3D""><span style=3D"font-size: 10.5pt;font-family: SimSun;">Best Regards,= </span></p><p style=3D""><span style=3D"font-size: 10.5pt;font-family: SimS= un;">Liyan</span></p><p> </p><p style=3D"margin-bottom: 12.0pt;">----<= span style=3D"font-family: "Microsoft JhengHei" , sans-serif;">= =E9=82=AE=E4=BB=B6=E5=8E=9F=E6=96=87</span>----<br/><span style=3D"font-fam= ily: "Microsoft JhengHei" , sans-serif;">=E5=8F=91=E4=BB=B6=E4=BA= =BA=EF=BC=9A</span>internet-drafts <<a href=3D"mailto:internet-draf= [email protected]">[email protected]</a>><br/><span style=3D"font-famil= y: "MS Gothic";">=E6=94=B6=E4=BB=B6=E4=BA=BA=EF=BC=9A</span>Chang= wang Lin <<a href=3D"mailto:[email protected]">lincha= [email protected]</a>>,Fenghua Ren <<a href=3D"mailto:re= [email protected]">[email protected]</a>>,Liyan Gong <= ;<a href=3D"mailto:[email protected]">[email protected]</a>= >,Mingyu Wu <<a href=3D"mailto:[email protected]">wumy@centec= .com</a>>,Peiyong Ma <<a href=3D"mailto:mapeiy@chinatelecom= .cn">[email protected]</a>>,Shay Zadok <<a href=3D"mai= lto:[email protected]">[email protected]</a>>,Weiqiang = Cheng <<a href=3D"mailto:[email protected]">chengweiqia= [email protected]</a>>,Xuewei Wang <<a href=3D"mailto:wang= [email protected]">[email protected]</a>>,xuewei wang&n= bsp;<<a href=3D"mailto:[email protected]">[email protected]= .cn</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 Go= thic";">=E6=97=A0</span>)<br/><span style=3D"font-family: "Micros= oft 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<br/><span style=3D"font-family: "= ;MS Gothic";">=E4=B8=BB</span><span style=3D"font-family: "Micros= oft JhengHei" , sans-serif;">=E9=A2=98=EF=BC=9A</span>New Version= Notification for draft-cheng-spring-srv6-encoding-network-s= liceid-12.txt<br/><br/>A new version of Internet-Draft<= br/>draft-cheng-spring-srv6-encoding-network-sliceid-12.txt has b= een successfully<br/>submitted by Liyan Gong and&n= bsp;posted to the<br/>IETF repository.<br/><br/>Name: &= nbsp; draft-cheng-spring-srv6-encoding-network-sliceid<br/= >Revision: 12<br/>Title: Encoding Network&= nbsp;Slice Identification for SRv6<br/>Date: &nbs= p; 2026-01-13<br/>Group: Individual = Submission<br/>Pages: 10<br/>URL: &= nbsp; <a href=3D"https://www.ietf.org/archive/id/draft-cheng-spr= ing-srv6-encoding-network-sliceid-12.txt">https://www.ietf.org/archive/id/d= raft-cheng-spring-srv6-encoding-network-sliceid-12.txt</a><br/>Status: = ; <a href=3D"https://datatracker.ietf.org/doc/draft-cheng-spring= -srv6-encoding-network-sliceid/">https://datatracker.ietf.org/doc/draft-che= ng-spring-srv6-encoding-network-sliceid/</a><br/>HTML: &nb= sp; <a href=3D"https://www.ietf.org/archive/id/draft-cheng-spring-srv6= -encoding-network-sliceid-12.html">https://www.ietf.org/archive/id/draft-ch= eng-spring-srv6-encoding-network-sliceid-12.html</a><br/>HTMLized: <a = href=3D"https://datatracker.ietf.org/doc/html/draft-cheng-spring-srv6-encod= ing-network-sliceid">https://datatracker.ietf.org/doc/html/draft-cheng-spri= ng-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">https://author-tools.ietf.org/iddiff?url2= =3Ddraft-cheng-spring-srv6-encoding-network-sliceid-12</a><br/><br/>Abstrac= t:<br/><br/> A Network Resource Partition&n= bsp;(NRP) is a subset of the network<br/>&nbs= p; resources and associated policies on = ;each of a connected set of links<br/> &= nbsp; in the underlay network. An NRP&n= bsp;could be used as the underlay to<br/>&nbs= p; support one or a group of enhan= ced VPN services. For packet<br/> &nbs= p;forwarding in a specific NRP, some fields&n= bsp;in the data packet are used<br/> &n= bsp;to identify the NRP the packet belongs&nb= sp;to, so that NRP-specific<br/> processing= can be performed on each node along&nbs= p;a path in the NRP.<br/><br/> This&nb= sp;document describes a novel method to encod= e NRP-ID in the outer<br/> IPv6 h= eader of an SRv6 domain, which could be&= nbsp;used to identify the<br/> NRP-specific= processing to be performed on the packe= ts by each<br/> network node along&nbs= p;a network path in the NRP.<br/><br/><br/><br/>Th= e IETF Secretariat<br/><br/><br/><br/>Subject<span style=3D"font-= family: "MS Gothic";">=EF=BC=9A</span>New Version Notif= ication for draft-cheng-spring-srv6-encoding-network-sliceid-12.t= xt<br/><br/>A new version of Internet-Draft<br/>draft-c= heng-spring-srv6-encoding-network-sliceid-12.txt has been su= ccessfully<br/>submitted by Liyan Gong and posted&= nbsp;to the<br/>IETF repository.<br/><br/>Name: = draft-cheng-spring-srv6-encoding-network-sliceid<br/>Revision:&= nbsp;12<br/>Title: Encoding Network Slice&= nbsp;Identification for SRv6<br/>Date: &nb= sp;2026-01-13<br/>Group: Individual Submission<= br/>Pages: 10<br/>URL: = <a href=3D"https://www.ietf.org/archive/id/draft-cheng-spring-srv6-en= coding-network-sliceid-12.txt">https://www.ietf.org/archive/id/draft-cheng-= spring-srv6-encoding-network-sliceid-12.txt</a><br/>Status: &nbs= p;<a href=3D"https://datatracker.ietf.org/doc/draft-cheng-spring-srv6-encod= ing-network-sliceid/">https://datatracker.ietf.org/doc/draft-cheng-spring-s= rv6-encoding-network-sliceid/</a><br/>HTML: <a= href=3D"https://www.ietf.org/archive/id/draft-cheng-spring-srv6-encoding-n= etwork-sliceid-12.html">https://www.ietf.org/archive/id/draft-cheng-spring-= srv6-encoding-network-sliceid-12.html</a><br/>HTMLized: <a href=3D"htt= ps://datatracker.ietf.org/doc/html/draft-cheng-spring-srv6-encoding-network= -sliceid">https://datatracker.ietf.org/doc/html/draft-cheng-spring-srv6-enc= oding-network-sliceid</a><br/>Diff: <a href=3D= "https://author-tools.ietf.org/iddiff?url2=3Ddraft-cheng-spring-srv6-encodi= ng-network-sliceid-12">https://author-tools.ietf.org/iddiff?url2=3Ddraft-ch= eng-spring-srv6-encoding-network-sliceid-12</a><br/><br/>Abstract:<br/><br/= > A Network Resource Partition (NRP)&n= bsp;is a subset of the network<br/> &nb= sp;resources and associated policies on each = of a connected set of links<br/> = in the underlay network. An NRP could&n= bsp;be used as the underlay to<br/> &nb= sp;support one or a group of enhanced VP= N services. For packet<br/> forwardin= g in a specific NRP, some fields in = ;the data packet are used<br/> to = ;identify the NRP the packet belongs to, = ;so that NRP-specific<br/> processing can&n= bsp;be performed on each node along a pa= th in the NRP.<br/><br/> This document= describes a novel method to encode NRP-= ID in the outer<br/> IPv6 header = of an SRv6 domain, which could be used&n= bsp;to identify the<br/> NRP-specific proce= ssing to be performed on the packets by&= nbsp;each<br/> network node along a ne= twork path in the NRP.<br/><br/><br/><br/>The IETF= Secretariat<br/><br/><br/></p></div></blockquote><p><br/></p> ------=_Part_832544_331956354.1768387173737-- --===============4462304096674139265== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18Kc3ByaW5nIG1h aWxpbmcgbGlzdCAtLSBzcHJpbmdAaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFp bCB0byBzcHJpbmctbGVhdmVAaWV0Zi5vcmcK --===============4462304096674139265==--