[spring] Re: [Teas] Re: New Version Notification for d raft-cheng-spring-srv6-encoding-network-sliceid-12.txt
"Adrian Farrel" <[email protected]> Tue, 13 Jan 2026 12:08:54 -0000
| Newsgroups | gmane.ietf.spring,gmane.ietf.ipv6 |
|---|---|
| Organization | Old Dog Consulting |
| Message-ID | <[email protected]> |
This is a multipart message in MIME format. --===============8295961812116633591== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0191_01DC8485.63D17360" Content-Language: en-gb This is a multipart message in MIME format. ------=_NextPart_000_0191_01DC8485.63D17360 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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 = other work on network slicing. =20 For example: * 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 between slice and NRP, this is = unlikely to be normal. * There may be a difference between a network resource partition = identifier (NRP-ID) and a network resource partition selector identifier = (NRPS ID) (draft-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]>=20 Sent: 13 January 2026 10:28 To: [email protected]; 6man <[email protected]>; TEAS WG <[email protected]>; IPv6 = List <[email protected]> Cc: Changwang Lin <[email protected]>; Fenghua Ren = <[email protected]>; Mingyu Wu <[email protected]>; Peiyong Ma = <[email protected]>; Shay Zadok <[email protected]>; Weiqiang = Cheng <[email protected]>; Xuewei Wang = <[email protected]> Subject: [Teas] Re: New Version Notification for = draft-cheng-spring-srv6-encoding-network-sliceid-12.txt =20 Dear All, =20 We have updated the individual draft = **draft-cheng-spring-srv6-encoding-network-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-ID) within the outer IPv6 header of SRv6 packets. It enables routers along a path to identify the slice and apply specific = forwarding treatment, facilitating slice-aware traffic steering across = an SRv6 domain.=20 The primary goal of this update is to refine the document's clarity, = address 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 = both 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 the deployment and interoperability characteristics of each SPI = option, helping operators understand the migration path. 4. **Editorial Improvements:** Various text refinements, structure = adjustments, and typo fixes throughout the document to improve = readability. =20 Furthermore, the proposed encoding mechanism has undergone practical = validation.It was successfully 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. =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] <mailto:[email protected]> > =E6=94=B6=E4=BB=B6=E4=BA=BA=EF=BC=9AChangwang Lin = <[email protected] <mailto:[email protected]> = >,Fenghua Ren <[email protected] <mailto:[email protected]> = >,Liyan Gong <[email protected] = <mailto:[email protected]> >,Mingyu Wu <[email protected] = <mailto:[email protected]> >,Peiyong Ma <[email protected] = <mailto:[email protected]> >,Shay Zadok <[email protected] = <mailto:[email protected]> >,Weiqiang Cheng = <[email protected] <mailto:[email protected]> = >,Xuewei Wang <[email protected] = <mailto:[email protected]> >,xuewei wang = <[email protected] <mailto:[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.txt A new version of Internet-Draft draft-cheng-spring-srv6-encoding-network-sliceid-12.txt has been = successfully submitted by Liyan Gong and posted to the IETF repository. Name: draft-cheng-spring-srv6-encoding-network-sliceid Revision: 12 Title: Encoding Network Slice Identification for SRv6 Date: 2026-01-13 Group: Individual Submission Pages: 10 URL: = https://www.ietf.org/archive/id/draft-cheng-spring-srv6-encoding-network-= sliceid-12.txt Status: = https://datatracker.ietf.org/doc/draft-cheng-spring-srv6-encoding-network= -sliceid/ HTML: = https://www.ietf.org/archive/id/draft-cheng-spring-srv6-encoding-network-= sliceid-12.html HTMLized: = https://datatracker.ietf.org/doc/html/draft-cheng-spring-srv6-encoding-ne= twork-sliceid Diff: = https://author-tools.ietf.org/iddiff?url2=3Ddraft-cheng-spring-srv6-encod= ing-network-sliceid-12 Abstract: 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-ID in the outer IPv6 header of an SRv6 domain, which could be used to identify the NRP-specific processing to be performed on the packets by each network node along a network path in the NRP. The IETF Secretariat Subject=EF=BC=9ANew Version Notification for = draft-cheng-spring-srv6-encoding-network-sliceid-12.txt A new version of Internet-Draft draft-cheng-spring-srv6-encoding-network-sliceid-12.txt has been = successfully submitted by Liyan Gong and posted to the IETF repository. Name: draft-cheng-spring-srv6-encoding-network-sliceid Revision: 12 Title: Encoding Network Slice Identification for SRv6 Date: 2026-01-13 Group: Individual Submission Pages: 10 URL: = https://www.ietf.org/archive/id/draft-cheng-spring-srv6-encoding-network-= sliceid-12.txt Status: = https://datatracker.ietf.org/doc/draft-cheng-spring-srv6-encoding-network= -sliceid/ HTML: = https://www.ietf.org/archive/id/draft-cheng-spring-srv6-encoding-network-= sliceid-12.html HTMLized: = https://datatracker.ietf.org/doc/html/draft-cheng-spring-srv6-encoding-ne= twork-sliceid Diff: = https://author-tools.ietf.org/iddiff?url2=3Ddraft-cheng-spring-srv6-encod= ing-network-sliceid-12 Abstract: 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-ID in the outer IPv6 header of an SRv6 domain, which could be used to identify the NRP-specific processing to be performed on the packets by each network node along a network path in the NRP. The IETF Secretariat ------=_NextPart_000_0191_01DC8485.63D17360 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" = xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" = xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta = http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta = name=3DGenerator content=3D"Microsoft Word 15 (filtered = medium)"><style><!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0;} @font-face {font-family:SimSun; panose-1:2 1 6 0 3 1 1 1 1 1;} @font-face {font-family:"MS Gothic"; panose-1:2 11 6 9 7 2 5 8 2 4;} @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Aptos;} @font-face {font-family:"\@SimSun"; panose-1:2 1 6 0 3 1 1 1 1 1;} @font-face {font-family:"Segoe UI"; panose-1:2 11 5 2 4 2 4 2 2 3;} @font-face {font-family:"Microsoft JhengHei"; panose-1:2 11 6 4 3 5 4 4 2 4;} @font-face {font-family:"\@Microsoft JhengHei";} @font-face {font-family:"\@MS Gothic"; panose-1:2 11 6 9 7 2 5 8 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; font-size:12.0pt; font-family:"Aptos",sans-serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:#0563C1; text-decoration:underline;} p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {mso-style-priority:34; margin-top:0cm; margin-right:0cm; margin-bottom:0cm; margin-left:36.0pt; font-size:12.0pt; font-family:"Aptos",sans-serif;} span.EmailStyle20 {mso-style-type:personal-reply; font-family:"Calibri",sans-serif; color:windowtext;} .MsoChpDefault {mso-style-type:export-only; font-size:11.0pt; mso-fareast-language:EN-US;} @page WordSection1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt;} div.WordSection1 {page:WordSection1;} /* List Definitions */ @list l0 {mso-list-id:2069918024; mso-list-type:hybrid; mso-list-template-ids:2058370270 112110694 134807555 134807557 = 134807553 134807555 134807557 134807553 134807555 134807557;} @list l0:level1 {mso-level-start-at:0; mso-level-number-format:bullet; mso-level-text:-; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt; font-family:"Calibri",sans-serif; mso-fareast-font-family:Calibri;} @list l0:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt; font-family:"Courier New";} @list l0:level3 {mso-level-number-format:bullet; mso-level-text:=EF=82=A7; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt; font-family:Wingdings;} @list l0:level4 {mso-level-number-format:bullet; mso-level-text:=EF=82=B7; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt; font-family:Symbol;} @list l0:level5 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt; font-family:"Courier New";} @list l0:level6 {mso-level-number-format:bullet; mso-level-text:=EF=82=A7; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt; font-family:Wingdings;} @list l0:level7 {mso-level-number-format:bullet; mso-level-text:=EF=82=B7; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt; font-family:Symbol;} @list l0:level8 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt; font-family:"Courier New";} @list l0:level9 {mso-level-number-format:bullet; mso-level-text:=EF=82=A7; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt; font-family:Wingdings;} ol {margin-bottom:0cm;} ul {margin-bottom:0cm;} --></style></head><body lang=3DEN-GB link=3D"#0563C1" vlink=3D"#954F72" = style=3D'word-wrap:break-word'><div class=3DWordSection1><p = class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-la= nguage:EN-US'>Hello,<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-la= nguage:EN-US'><o:p> </o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-la= nguage:EN-US'>Thanks for continuing to work on your = draft.<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-la= nguage:EN-US'><o:p> </o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-la= nguage:EN-US'>I think it would be really helpful to try to align your = terminology with other work on network slicing.<o:p></o:p></span></p><p = class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-la= nguage:EN-US'><o:p> </o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-la= nguage:EN-US'>For example:<o:p></o:p></span></p><ul = style=3D'margin-top:0cm' type=3Ddisc><li class=3DMsoListParagraph = style=3D'margin-left:0cm;mso-list:l0 level1 lfo1'><span = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-la= nguage:EN-US'>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 between slice and NRP, = this is unlikely to be normal.<o:p></o:p></span></li><li = class=3DMsoListParagraph style=3D'margin-left:0cm;mso-list:l0 level1 = lfo1'><span = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-la= nguage:EN-US'>There may be a difference between a network resource = partition identifier (NRP-ID) and a network resource partition selector = identifier (NRPS ID) (draft-ietf-teas-nrp-scalability section 5.2 and = draft-ietf-teas-ns-ip-mpls)<o:p></o:p></span></li></ul><p = class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-la= nguage:EN-US'><o:p> </o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-la= nguage:EN-US'>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.<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-la= nguage:EN-US'><o:p> </o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-la= nguage:EN-US'>Cheers,<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-la= nguage:EN-US'>Adrian<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-la= nguage:EN-US'><o:p> </o:p></span></p><div = style=3D'border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm = 0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span><= /b><span lang=3DEN-US = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif'> Liyan Gong = <[email protected]> <br><b>Sent:</b> 13 January 2026 = 10:28<br><b>To:</b> [email protected]; 6man <[email protected]>; TEAS WG = <[email protected]>; IPv6 List <[email protected]><br><b>Cc:</b> = Changwang Lin <[email protected]>; Fenghua Ren = <[email protected]>; Mingyu Wu <[email protected]>; = Peiyong Ma <[email protected]>; Shay Zadok = <[email protected]>; Weiqiang Cheng = <[email protected]>; Xuewei Wang = <[email protected]><br><b>Subject:</b> [Teas] Re: New = Version Notification for = draft-cheng-spring-srv6-encoding-network-sliceid-12.txt<o:p></o:p></span>= </p></div><p class=3DMsoNormal><o:p> </o:p></p><p><span = style=3D'font-size:10.5pt;font-family:SimSun'>Dear = All,</span><o:p></o:p></p><p style=3D'text-wrap-mode: wrap'><span = style=3D'font-size:10.5pt;font-family:SimSun'> </span><o:p></o:p></p= ><p style=3D'text-wrap-mode: wrap'><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><o:p></o:p></p><p style=3D'text-wrap-mode: = wrap'><span style=3D'font-size:10.5pt;font-family:SimSun'>We would = greatly appreciate your review and comments on this new = revision.</span><o:p></o:p></p><p style=3D'text-wrap-mode: = wrap'><o:p> </o:p></p><p style=3D'text-wrap-mode: wrap'><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><o:p></o:p></p><p = style=3D'text-wrap-mode: wrap'><span = style=3D'font-size:10.5pt;font-family:SimSun'>It enables routers along a = path to identify the slice and apply specific forwarding treatment, = facilitating slice-aware traffic steering across an SRv6 = domain. </span><o:p></o:p></p><p style=3D'text-wrap-mode: = wrap'><span style=3D'font-size:10.5pt;font-family:SimSun'>The primary = goal of this update is to refine the document's clarity, address = security considerations, and enhance its readiness for wider = review. </span><o:p></o:p></p><p style=3D'text-wrap-mode: = wrap'><span = style=3D'font-size:10.5pt;font-family:SimSun'> </span><o:p></o:p></p= ><p style=3D'text-wrap-mode: wrap'><span = style=3D'font-size:10.5pt;font-family:SimSun'>**Key updates in version = -12 include:**</span><o:p></o:p></p><p style=3D'text-wrap-mode: = wrap'><span = style=3D'font-size:10.5pt;font-family:SimSun'> </span><o:p></o:p></p= ><p style=3D'text-wrap-mode: wrap'><span = style=3D'font-size:10.5pt;font-family:SimSun'>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.</span><o:p></o:p></p><p style=3D'text-wrap-mode: wrap'><span = style=3D'font-size:10.5pt;font-family:SimSun'>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><o:p></o:p></p><p style=3D'text-wrap-mode: = wrap'><span style=3D'font-size:10.5pt;font-family:SimSun'>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><o:p></o:p></p><p style=3D'text-wrap-mode: wrap'><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><o:p></o:p></p><p style=3D'text-wrap-mode: = wrap'><span = style=3D'font-size:10.5pt;font-family:SimSun'> </span><o:p></o:p></p= ><p style=3D'text-wrap-mode: wrap'><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 "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><o:p></o:p></p><p = style=3D'text-wrap-mode: wrap'><o:p> </o:p></p><p = style=3D'text-wrap-mode: wrap'><span = style=3D'font-size:10.5pt;font-family:SimSun;color:#0F1115;background:whi= te'>Following advice 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-family:SimSun'> </span><o:p></o:p></p= ><p style=3D'text-wrap-mode: wrap'><span = style=3D'font-size:10.5pt;font-family:SimSun'>Thank you for your time = and consideration, looking forward to your = feedback.</span><o:p></o:p></p><p style=3D'text-wrap-mode: wrap'><span = style=3D'font-size:8.5pt;font-family:"Segoe = UI",sans-serif;color:#0F1115;background:white'> </span><o:p></o:p></= p><p style=3D'text-wrap-mode: wrap'><span = style=3D'font-size:10.5pt;font-family:SimSun'>Best = Regards,</span><o:p></o:p></p><p style=3D'text-wrap-mode: wrap'><span = style=3D'font-size:10.5pt;font-family:SimSun'>Liyan</span><o:p></o:p></p>= <p><o:p> </o: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-family:"Microsoft = JhengHei",sans-serif'>=E5=8F=91=E4=BB=B6=E4=BA=BA=EF=BC=9A</span>internet= -drafts <<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&nb= sp;<<a = href=3D"mailto:[email protected]">[email protected]</a>= >,Fenghua Ren <<a = href=3D"mailto:[email protected]">[email protected]</a>>,Liyan= Gong <<a = href=3D"mailto:[email protected]">[email protected]</a>&g= t;,Mingyu Wu <<a = href=3D"mailto:[email protected]">[email protected]</a>>,Peiyong Ma&n= bsp;<<a = href=3D"mailto:[email protected]">[email protected]</a>>,Sha= y Zadok <<a = href=3D"mailto:[email protected]">[email protected]</a>>,W= eiqiang Cheng <<a = href=3D"mailto:[email protected]">[email protected]= om</a>>,Xuewei Wang <<a = href=3D"mailto:[email protected]">[email protected]</a>&g= t;,xuewei wang <<a = href=3D"mailto:[email protected]">[email protected]</a>&g= t;<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><span = 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<br><span style=3D'font-family:"MS = Gothic"'>=E4=B8=BB</span><span style=3D'font-family:"Microsoft = JhengHei",sans-serif'>=E9=A2=98=EF=BC=9A</span>New Version Noti= fication for draft-cheng-spring-srv6-encoding-network-sliceid-1= 2.txt<br><br>A new version of Internet-Draft<br>draft= -cheng-spring-srv6-encoding-network-sliceid-12.txt has been&nbs= p;successfully<br>submitted by Liyan Gong and po= sted to the<br>IETF repository.<br><br>Name: &n= bsp; draft-cheng-spring-srv6-encoding-network-sliceid<br>Revis= ion: 12<br>Title: Encoding Network = Slice Identification for SRv6<br>Date: &n= bsp; 2026-01-13<br>Group: Individual Sub= mission<br>Pages: 10<br>URL: &nbs= p; <a = href=3D"https://www.ietf.org/archive/id/draft-cheng-spring-srv6-encoding-= network-sliceid-12.txt">https://www.ietf.org/archive/id/draft-cheng-sprin= g-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-cheng-spring-sr= v6-encoding-network-sliceid/</a><br>HTML: <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-cheng-spri= ng-srv6-encoding-network-sliceid-12.html</a><br>HTMLized: <a = href=3D"https://datatracker.ietf.org/doc/html/draft-cheng-spring-srv6-enc= oding-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/iddiff?url2=3Ddraft-cheng-spring-sr= v6-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>&nb= sp; resources and associated policies on&n= bsp;each of a connected set of links<br>&nb= sp; in the underlay network. An = ;NRP could be used as the underlay to<= br> support one or a group of&n= bsp;enhanced VPN services. For packet<br> = forwarding in a specific NRP, some&n= bsp;fields in the data packet are used<br>&= nbsp; to identify the NRP the packet&= nbsp;belongs to, so that NRP-specific<br> = processing can be performed on each n= ode along a path in the NRP.<br><br> &= nbsp; This document describes a novel metho= d to encode NRP-ID in the outer<br> &n= bsp; IPv6 header of an SRv6 domain, wh= ich could be used to identify the<br> = NRP-specific processing to be performed&n= bsp;on the packets by each<br> netwo= rk node along a network path in the&nb= sp;NRP.<br><br><br><br>The IETF Secretariat<br><br><br><br>Subj= ect<span style=3D'font-family:"MS = Gothic"'>=EF=BC=9A</span>New Version Notification for = ;draft-cheng-spring-srv6-encoding-network-sliceid-12.txt<br><br>A ne= w version of Internet-Draft<br>draft-cheng-spring-srv6-enc= oding-network-sliceid-12.txt has been successfully<br>subm= itted by Liyan Gong and posted to the<= br>IETF repository.<br><br>Name: draft-= cheng-spring-srv6-encoding-network-sliceid<br>Revision: 12<br>Title:= Encoding Network Slice Identificat= ion for SRv6<br>Date: 2026-01-13<b= r>Group: Individual Submission<br>Pages: = ; 10<br>URL: <a = href=3D"https://www.ietf.org/archive/id/draft-cheng-spring-srv6-encoding-= network-sliceid-12.txt">https://www.ietf.org/archive/id/draft-cheng-sprin= g-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-cheng-spring-sr= v6-encoding-network-sliceid/</a><br>HTML: <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-cheng-spri= ng-srv6-encoding-network-sliceid-12.html</a><br>HTMLized: <a = href=3D"https://datatracker.ietf.org/doc/html/draft-cheng-spring-srv6-enc= oding-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/iddiff?url2=3Ddraft-cheng-spring-sr= v6-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>&nb= sp; resources and associated policies on&n= bsp;each of a connected set of links<br>&nb= sp; in the underlay network. An = ;NRP could be used as the underlay to<= br> support one or a group of&n= bsp;enhanced VPN services. For packet<br> = forwarding in a specific NRP, some&n= bsp;fields in the data packet are used<br>&= nbsp; to identify the NRP the packet&= nbsp;belongs to, so that NRP-specific<br> = processing can be performed on each n= ode along a path in the NRP.<br><br> &= nbsp; This document describes a novel metho= d to encode NRP-ID in the outer<br> &n= bsp; IPv6 header of an SRv6 domain, wh= ich could be used to identify the<br> = NRP-specific processing to be performed&n= bsp;on the packets by each<br> netwo= rk node along a network path in the&nb= sp;NRP.<br><br><br><br>The IETF Secretariat<br><br><br><o:p></o= :p></p></div></body></html> ------=_NextPart_000_0191_01DC8485.63D17360-- --===============8295961812116633591== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18Kc3ByaW5nIG1h aWxpbmcgbGlzdCAtLSBzcHJpbmdAaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFp bCB0byBzcHJpbmctbGVhdmVAaWV0Zi5vcmcK --===============8295961812116633591==--