[spring] Re: New Version Notification for draft-cheng-spring -srv6-encoding-network-sliceid-12.txt
Liyan Gong <[email protected]> Tue, 13 Jan 2026 18:28:03 +0800 (CST)
| Newsgroups | gmane.ietf.spring,gmane.ietf.ipv6 |
|---|---|
| Message-ID | <2afe696617762a5-0006b.Richmail.00004002254980008077@chinamobile.com> |
--===============7370229565073376299== Content-Type: multipart/alternative; boundary="----=_Part_510382_1879626081.1768300083855" ------=_Part_510382_1879626081.1768300083855 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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. 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. 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 ----=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_510382_1879626081.1768300083855 Content-Type: text/html;charset=UTF-8 Content-Transfer-Encoding: quoted-printable <p style=3D"text-wrap-mode: wrap;"><span style=3D"font-family: =E5=AE=8B=E4= =BD=93; font-size: 14px; letter-spacing: 0px;">Dear All,</span></p><p style= =3D"text-wrap-mode: wrap;"><span style=3D"font-family: =E5=AE=8B=E4=BD=93; = letter-spacing: 0px; font-size: 14px;"> </span></p><p style=3D"text-wr= ap-mode: wrap;"><span style=3D"font-family: =E5=AE=8B=E4=BD=93; letter-spac= ing: 0px; font-size: 14px;">We have updated the individual draft **draft-ch= eng-spring-srv6-encoding-network-sliceid** to version **-12**.</span></p><p= style=3D"text-wrap-mode: wrap;"><span style=3D"font-family: =E5=AE=8B=E4= =BD=93; letter-spacing: 0px; font-size: 14px;"><span style=3D"font-family: = =E5=AE=8B=E4=BD=93; font-size: 14px; text-wrap-mode: wrap;">We would greatl= y appreciate your review and comments on this new revision.</span></span></= p><p style=3D"text-wrap-mode: wrap;"><span style=3D"font-family: =E5=AE=8B= =E4=BD=93; font-size: 14px; letter-spacing: 0px;"><br/></span></p><p style= =3D"text-wrap-mode: wrap;"><span style=3D"font-family: =E5=AE=8B=E4=BD=93; = letter-spacing: 0px; font-size: 14px;">This document describes a method to = encode a Network Slice Identifier(NRP-ID) within the outer IPv6 header of S= Rv6 packets.</span></p><p style=3D"text-wrap-mode: wrap;"><span style=3D"fo= nt-family: =E5=AE=8B=E4=BD=93; letter-spacing: 0px; font-size: 14px;">It en= ables routers along a path to identify the slice and apply specific forward= ing treatment, facilitating slice-aware traffic steering across an SRv6 dom= ain.</span><span style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 14px;= letter-spacing: 0px;"> </span></p><p style=3D"text-wrap-mode: wrap;">= <span style=3D"font-family: =E5=AE=8B=E4=BD=93; letter-spacing: 0px; font-s= ize: 14px;">The primary goal of this update is to refine the document's= clarity, address security considerations, and enhance its readiness for wi= der review. </span></p><p style=3D"text-wrap-mode: wrap;"><span style= =3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 14px; letter-spacing: 0px;"= > </span></p><p style=3D"text-wrap-mode: wrap;"><span style=3D"font-fa= mily: =E5=AE=8B=E4=BD=93; letter-spacing: 0px; font-size: 14px;">**Key upda= tes in version -12 include:**</span></p><p style=3D"text-wrap-mode: wrap;">= <span style=3D"font-family: =E5=AE=8B=E4=BD=93; letter-spacing: 0px; font-s= ize: 14px;"> </span></p><p style=3D"text-wrap-mode: wrap;"><span style= =3D"font-family: =E5=AE=8B=E4=BD=93; letter-spacing: 0px; font-size: 14px;"= >1. **Security Considerations Section:** Significantly expanded to de= fine a concrete trust model for the proposed encoding methods. It now inclu= des a threat analysis and discusses mitigation strategies relevant to opera= tional deployment.</span></p><p style=3D"text-wrap-mode: wrap;"><span style= =3D"font-family: =E5=AE=8B=E4=BD=93; letter-spacing: 0px; font-size: 14px;"= >2. **Clarification on SPI Encoding Options:** Enhanced descriptions = for both SPI encoding options (Traffic Class bit and Source Address prefix)= , with a clearer comparison of their backward compatibility implications.</= span></p><p style=3D"text-wrap-mode: wrap;"><span style=3D"font-family: =E5= =AE=8B=E4=BD=93; letter-spacing: 0px; font-size: 14px;">3. **Backward= Compatibility Section:** Updated to more explicitly detail the deployment = and interoperability characteristics of each SPI option, helping operators = understand the migration path.</span></p><p style=3D"text-wrap-mode: wrap;"= ><span style=3D"font-family: =E5=AE=8B=E4=BD=93; letter-spacing: 0px; font-= size: 14px;">4. **Editorial Improvements:** Various text refinements,= structure adjustments, and typo fixes throughout the document to improve r= eadability.</span></p><p style=3D"text-wrap-mode: wrap;"><span style=3D"fon= t-family: =E5=AE=8B=E4=BD=93; letter-spacing: 0px; font-size: 14px;"> = </span></p><p style=3D"text-wrap-mode: wrap;"><span style=3D"font-family: = =E5=AE=8B=E4=BD=93; letter-spacing: 0px; font-size: 14px;">Furthermore, the= proposed encoding mechanism has undergone practical validation.It was succ= essfully applied to realize "Link Slicing over SRv6" (use ca= se 3.21)in the 2024 MPLS&SDN Interoperability Test</span><span style=3D= "font-family: =E5=AE=8B=E4=BD=93; letter-spacing: 0px; font-size: 14px;">= =EF=BC=88EANTC=EF=BC=89</span><span style=3D"font-family: =E5=AE=8B=E4=BD= =93; letter-spacing: 0px; font-size: 14px;">, enabling cross-vendor source = address slicing integration. The insights from this implementation have inf= ormed the refinements in this document version.</span></p><p style=3D"text-= wrap-mode: wrap;"><span style=3D"font-family: =E5=AE=8B=E4=BD=93; letter-sp= acing: 0px; font-size: 14px;"><br/></span></p><p style=3D"text-wrap-mode: w= rap;"><span style=3D"font-family: =E5=AE=8B=E4=BD=93; letter-spacing: 0px; = font-size: 14px;"><span style=3D"color: #0F1115; font-family: =E5=AE=8B=E4= =BD=93, NSimSun, SimSun; background-color: #FFFFFF;">Following advice to so= cialize this work, we are sending this update to the SPRING, 6MAN, and TEAS= mailing lists.</span> </span></p><p style=3D"text-wrap-mode: wrap;"><= span style=3D"font-family: =E5=AE=8B=E4=BD=93; letter-spacing: 0px; font-si= ze: 14px;">Thank you for your time and consideration, looking forward to yo= ur feedback.</span></p><p style=3D"text-wrap-mode: wrap;"><span style=3D"fo= nt-family: "Segoe UI"; color: #0F1115; letter-spacing: 0px; font-= size: 11px; background: #FFFFFF;"> </span></p><p style=3D"text-wrap-mo= de: wrap;"><span style=3D"font-family: =E5=AE=8B=E4=BD=93; letter-spacing: = 0px; font-size: 14px;">Best Regards,</span></p><p style=3D"text-wrap-mode: = wrap;"><span style=3D"font-family: =E5=AE=8B=E4=BD=93; letter-spacing: 0px;= font-size: 14px;">Liyan</span></p><p><br/></p><p>----=E9=82=AE=E4=BB=B6=E5= =8E=9F=E6=96=87----<br/>=E5=8F=91=E4=BB=B6=E4=BA=BA=EF=BC=9Ainternet-drafts= <[email protected]><br/>=E6=94=B6=E4=BB=B6=E4=BA=BA=EF= =BC=9AChangwang Lin <[email protected]>,Fenghua&nb= sp;Ren <[email protected]>,Liyan Gong <gongliya= [email protected]>,Mingyu Wu <[email protected]>,Peiyong&n= bsp;Ma <[email protected]>,Shay Zadok <shay.za= [email protected]>,Weiqiang Cheng <chengweiqiang@chinamobile= .com>,Xuewei Wang <[email protected]>,xuewei&nbs= p;wang <[email protected]><br/>=E6=8A=84=E3=80=80=E9=80= =81: (=E6=97=A0)<br/>=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4=EF=BC=9A2026= -01-13 18:00:24<br/>=E4=B8=BB=E9=A2=98=EF=BC=9ANew Version N= otification for draft-cheng-spring-srv6-encoding-network-sliceid-= 12.txt<br/><br/>A new version of Internet-Draft<br/>dra= ft-cheng-spring-srv6-encoding-network-sliceid-12.txt has been&nbs= p;successfully<br/>submitted by Liyan Gong and pos= ted to the<br/>IETF repository.<br/><br/>Name: &n= bsp; draft-cheng-spring-srv6-encoding-network-sliceid<br/>Revisi= on: 12<br/>Title: Encoding Network Sl= ice Identification for SRv6<br/>Date:  = ; 2026-01-13<br/>Group: Individual Submiss= ion<br/>Pages: 10<br/>URL: &n= bsp; https://www.ietf.org/archive/id/draft-cheng-spring-srv6-encoding-= network-sliceid-12.txt<br/>Status: https://datatracker.iet= f.org/doc/draft-cheng-spring-srv6-encoding-network-sliceid/<br/>HTML: = https://www.ietf.org/archive/id/draft-cheng-spring-= srv6-encoding-network-sliceid-12.html<br/>HTMLized: https://datatracke= r.ietf.org/doc/html/draft-cheng-spring-srv6-encoding-network-sliceid<br/>Di= ff: https://author-tools.ietf.org/iddiff?url2= =3Ddraft-cheng-spring-srv6-encoding-network-sliceid-12<br/><br/>Abstract:<b= r/><br/> A Network Resource Partition = (NRP) is a subset of the network<br/> &n= bsp; resources and associated policies on eac= h of a connected set of links<br/>  = ; in the underlay network. An NRP = could be used as the underlay to<br/> &n= bsp; support one or a group of enhanced&= nbsp;VPN services. For packet<br/> fo= rwarding in a specific NRP, some fields = in the data packet are used<br/> = to identify the NRP the packet belongs t= o, so that NRP-specific<br/> processing&nbs= p;can be performed on each node along a&= nbsp;path in the NRP.<br/><br/> This d= ocument describes a novel method to encode&nb= sp;NRP-ID in the outer<br/> IPv6 heade= r of an SRv6 domain, which could be = ;used to identify the<br/> NRP-specific&nbs= p;processing to be performed on the packets&n= bsp;by each<br/> network node along a&= nbsp;network path in the NRP.<br/><br/><br/><br/>The&nb= sp;IETF Secretariat<br/><br/><br/><br/>Subject=EF=BC=9ANew Versio= n Notification for draft-cheng-spring-srv6-encoding-network-= sliceid-12.txt<br/><br/>A new version of Internet-Draft= <br/>draft-cheng-spring-srv6-encoding-network-sliceid-12.txt has = been successfully<br/>submitted by Liyan Gong and&= nbsp;posted to the<br/>IETF repository.<br/><br/>Name: = draft-cheng-spring-srv6-encoding-network-sliceid<br= />Revision: 12<br/>Title: Encoding Network= Slice Identification for SRv6<br/>Date: &nb= sp; 2026-01-13<br/>Group: Individual = ;Submission<br/>Pages: 10<br/>URL: = https://www.ietf.org/archive/id/draft-cheng-spring-srv6-e= ncoding-network-sliceid-12.txt<br/>Status: https://datatra= cker.ietf.org/doc/draft-cheng-spring-srv6-encoding-network-sliceid/<br/>HTM= L: https://www.ietf.org/archive/id/draft-cheng= -spring-srv6-encoding-network-sliceid-12.html<br/>HTMLized: https://da= tatracker.ietf.org/doc/html/draft-cheng-spring-srv6-encoding-network-slicei= d<br/>Diff: https://author-tools.ietf.org/iddi= ff?url2=3Ddraft-cheng-spring-srv6-encoding-network-sliceid-12<br/><br/>Abst= ract:<br/><br/> A Network Resource Partitio= n (NRP) is a subset of the network<br/>&= nbsp; resources and associated policies on&n= bsp;each of a connected set of links<br/>&nbs= p; in the underlay network. An NR= P could be used as the underlay to<br/>&= nbsp; support one or a group of en= hanced VPN services. For packet<br/> &= nbsp;forwarding in a specific NRP, some field= s in the data packet are used<br/>  = ; to identify the NRP the packet belongs= to, so that NRP-specific<br/> process= ing can be performed on each node along&= nbsp;a path in the NRP.<br/><br/> This= document describes a novel method to en= code NRP-ID in the outer<br/> IPv6&nbs= p;header of an SRv6 domain, which could = be used to identify the<br/> NRP-speci= fic processing to be performed on the pa= ckets by each<br/> network node along&= nbsp;a network path in the NRP.<br/><br/><br/><br/= >The IETF Secretariat<br/><br/><br/><br/></p> ------=_Part_510382_1879626081.1768300083855-- --===============7370229565073376299== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18Kc3ByaW5nIG1h aWxpbmcgbGlzdCAtLSBzcHJpbmdAaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFp bCB0byBzcHJpbmctbGVhdmVAaWV0Zi5vcmcK --===============7370229565073376299==--