[rtgwg] Fw:New Version Notification fordraft-gong-spring-nd- advertise-srv6-locator-04.txt
Liyan Gong <[email protected]> Wed, 25 Feb 2026 17:55:11 +0800 (CST)
| Newsgroups | gmane.ietf.rtgwg,gmane.ietf.spring,gmane.ietf.ipv6 |
|---|---|
| Message-ID | <2afd699ebc9bd62-000a9.Richmail.00003082153940001067@chinamobile.com> |
--===============7979053858602435303== Content-Type: multipart/alternative; boundary="----=_Part_1145740_1645374322.1772013311963" ------=_Part_1145740_1645374322.1772013311963 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: quoted-printable Dear All, We are sharing an updated version of draft-gong-spring-nd-advertise-srv6-lo= cator(revision-04) for your review and feedback. This document proposes a method for SRv6 endpoints(e.g., hosts or CPEs) to = advertise their SRv6 locators to a neighboring router using IPv6 Neighbor D= iscovery (ND) extensions. This approach aims to simplify deployment in controlled scenarios where end= points do not run traditional routing protocols. This draft was previously presented at IETF 122 in the SPRING WG. Based on = the valuable feedback received, we have revised the document with substanti= al clarifications and enhancements. Key updates in version -04 include: 1. Enhanced motivation and applicability section, clarifying use cases such= as SRv6 on hosts in data centers and static CPE deployments. 2. Explicit trust boundary and security guidance, emphasizing that the mech= anism is designed for single administrative domains and is NOT RECOMMENDED = for untrusted environments. 3. Scalability consideration: Added text suggesting that access routers may= aggregate fine-grained locators before advertising to the core. 4. Structural improvements: Reorganized sections for better readability (e.= g., separating Motivation and Process). 5. Editorial refinements throughout the text for clarity and alignment with= RFC language conventions. Following the suggestion from the meeting, we are also sending this update = to the SPRING, RTGWG, and 6MAN mailing lists.=20 We welcome your comments on any aspect of the draft.Thank you for your time= and consideration. 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=9AAcee Lindem <[email protected]>,Changwang Lin <linchangwang.0441= [email protected]>,Liyan Gong <[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-02-25 17:= 31:28=E4=B8=BB=E9=A2=98=EF=BC=9ANew Version Notification for draft-gong-spr= ing-nd-advertise-srv6-locator-04.txtA new version of Internet-Draftdraft-go= ng-spring-nd-advertise-srv6-locator-04.txt has been successfullysubmitted b= y Liyan Gong and posted to theIETF repository.Name: draft-gong-spring-n= d-advertise-srv6-locatorRevision: 04Title: Advertise SRv6 Locator Inform= ation by IPv6 Neighbor DiscoveryDate: 2026-02-25Group: Individual Su= bmissionPages: 11URL: https://www.ietf.org/archive/id/draft-gong-sp= ring-nd-advertise-srv6-locator-04.txtStatus: https://datatracker.ietf.org= /doc/draft-gong-spring-nd-advertise-srv6-locator/HTML: https://www.ietf= .org/archive/id/draft-gong-spring-nd-advertise-srv6-locator-04.htmlHTMLized= : https://datatracker.ietf.org/doc/html/draft-gong-spring-nd-advertise-srv6= -locatorDiff: https://author-tools.ietf.org/iddiff?url2=3Ddraft-gong-sp= ring-nd-advertise-srv6-locator-04Abstract: In an SRv6 network, each SRv6 = segment endpoint has at least one SRv6 Locator. Through the SRv6 locator= routes, other SRv6 segment nodes can steer traffic to that node. This d= ocument describes a method for an SRv6 endpoint (e.g., a host or a custom= er provider edge (CPE)) to advertise its SRv6 locator to a neighboring SR= v6-aware router using extensions to the IPv6 Neighbor Discovery (ND) prot= ocol. This approach eliminates the need to run a full routing protocol s= tack on simple endpoints, facilitating SRv6 deployment in controlled, tru= sted domains such as data centers and managed access networks.The IETF Se= cretariatSubject=EF=BC=9ANew Version Notification for draft-gong-spring-nd-= advertise-srv6-locator-04.txtA new version of Internet-Draftdraft-gong-spri= ng-nd-advertise-srv6-locator-04.txt has been successfullysubmitted by Liyan= Gong and posted to theIETF repository.Name: draft-gong-spring-nd-adver= tise-srv6-locatorRevision: 04Title: Advertise SRv6 Locator Information b= y IPv6 Neighbor DiscoveryDate: 2026-02-25Group: Individual Submissio= nPages: 11URL: https://www.ietf.org/archive/id/draft-gong-spring-nd= -advertise-srv6-locator-04.txtStatus: https://datatracker.ietf.org/doc/dr= aft-gong-spring-nd-advertise-srv6-locator/HTML: https://www.ietf.org/ar= chive/id/draft-gong-spring-nd-advertise-srv6-locator-04.htmlHTMLized: https= ://datatracker.ietf.org/doc/html/draft-gong-spring-nd-advertise-srv6-locato= rDiff: https://author-tools.ietf.org/iddiff?url2=3Ddraft-gong-spring-nd= -advertise-srv6-locator-04Abstract: In an SRv6 network, each SRv6 segment= endpoint has at least one SRv6 Locator. Through the SRv6 locator routes= , other SRv6 segment nodes can steer traffic to that node. This document= describes a method for an SRv6 endpoint (e.g., a host or a customer prov= ider edge (CPE)) to advertise its SRv6 locator to a neighboring SRv6-awar= e router using extensions to the IPv6 Neighbor Discovery (ND) protocol. = This approach eliminates the need to run a full routing protocol stack on= simple endpoints, facilitating SRv6 deployment in controlled, trusted = domains such as data centers and managed access networks.The IETF Secretari= at ------=_Part_1145740_1645374322.1772013311963 Content-Type: text/html;charset=UTF-8 Content-Transfer-Encoding: quoted-printable <p>Dear All,</p><p style=3D""><br/></p><p style=3D""><span style=3D"font-fa= mily: =E5=AE=8B=E4=BD=93 , NSimSun , SimSun;background-color: #FFFFFF;color= : #0F1115;">We are sharing an updated version of </span><span style=3D= "font-family: =E5=AE=8B=E4=BD=93 , NSimSun , SimSun;background-color: #FFFF= FF;color: #0F1115;">draft-gong-spring-nd-advertise-srv6-locator</span><span= style=3D"font-family: =E5=AE=8B=E4=BD=93 , NSimSun , SimSun;background-col= or: #FFFFFF;color: #0F1115;">(revision</span><span style=3D"font-family: = =E5=AE=8B=E4=BD=93 , NSimSun , SimSun;background-color: #FFFFFF;color: #0F1= 115;">-04</span><span style=3D"font-family: =E5=AE=8B=E4=BD=93 , NSimSun , = SimSun;background-color: #FFFFFF;color: #0F1115;">) for your review and fee= dback.</span></p><p class=3D"ds-markdown-paragraph" style=3D"margin-top: 16= .0px;margin-bottom: 16.0px;color: rgb(15,17,21);background-color: rgb(255,2= 55,255);"><span style=3D"font-family: =E5=AE=8B=E4=BD=93 , NSimSun , SimSun= ;">This document proposes a method for SRv6 endpoints(e.g., hosts or CPEs) = to advertise their SRv6 locators to a neighboring router using IPv6 Neighbo= r Discovery (ND) extensions.</span></p><p class=3D"ds-markdown-paragraph" s= tyle=3D"margin-top: 16.0px;margin-bottom: 16.0px;color: rgb(15,17,21);backg= round-color: rgb(255,255,255);"><span style=3D"font-family: =E5=AE=8B=E4=BD= =93 , NSimSun , SimSun;">This approach aims to simplify deployment in contr= olled scenarios where endpoints do not run traditional routing protocols.</= span></p><p class=3D"ds-markdown-paragraph" style=3D"margin-top: 16.0px;mar= gin-bottom: 16.0px;color: rgb(15,17,21);background-color: rgb(255,255,255);= "><span style=3D"font-family: =E5=AE=8B=E4=BD=93 , NSimSun , SimSun;">This = draft was previously presented at IETF 122 in the SPRING WG. Based on the v= aluable feedback received, we have revised the document with substantial cl= arifications and enhancements.</span></p><p class=3D"ds-markdown-paragraph"= style=3D"margin-top: 16.0px;margin-bottom: 16.0px;color: rgb(15,17,21);bac= kground-color: rgb(255,255,255);"><span style=3D"font-family: =E5=AE=8B=E4= =BD=93 , NSimSun , SimSun;">Key updates in version -04 include:</span></p><= p class=3D"ds-markdown-paragraph" style=3D""><span style=3D"font-family: = =E5=AE=8B=E4=BD=93 , NSimSun , SimSun;">1. Enhanced motivation and applicab= ility section, clarifying use cases such as SRv6 on hosts in data centers a= nd static CPE deployments.</span></p><p class=3D"ds-markdown-paragraph" sty= le=3D""><span style=3D"font-family: =E5=AE=8B=E4=BD=93 , NSimSun , SimSun;"= >2. Explicit trust boundary and security guidance, emphasizing that the mec= hanism is designed for single administrative domains and is NOT RECOMMENDED= for untrusted environments.</span></p><p class=3D"ds-markdown-paragraph" s= tyle=3D""><span style=3D"font-family: =E5=AE=8B=E4=BD=93 , NSimSun , SimSun= ;">3. Scalability consideration: Added text suggesting that access routers = may aggregate fine-grained locators before advertising to the core.</span><= /p><p class=3D"ds-markdown-paragraph" style=3D""><span style=3D"font-family= : =E5=AE=8B=E4=BD=93 , NSimSun , SimSun;">4. Structural improvements: Reorg= anized sections for better readability (e.g., separating Motivation and Pro= cess).</span></p><p class=3D"ds-markdown-paragraph" style=3D""><span style= =3D"font-family: =E5=AE=8B=E4=BD=93 , NSimSun , SimSun;">5. Edi</span><span= style=3D"font-family: =E5=AE=8B=E4=BD=93 , NSimSun , SimSun;">torial refin= ements throughout the text for clarity and alignment with RFC language= conventions.</span></p><p class=3D"ds-markdown-paragraph" style=3D"margin-= top: 16.0px;margin-bottom: 16.0px;color: rgb(15,17,21);background-color: rg= b(255,255,255);"><span style=3D"font-family: =E5=AE=8B=E4=BD=93 , NSimSun ,= SimSun;">Following the suggestion from the meeting,</span><span style=3D"f= ont-family: =E5=AE=8B=E4=BD=93 , NSimSun , SimSun;"> we are also sending th= is update to the SPRING, RTGWG, and 6MAN mailing lists. </span></p><p = class=3D"ds-markdown-paragraph" style=3D"margin-top: 16.0px;margin-bottom: = 16.0px;color: rgb(15,17,21);background-color: rgb(255,255,255);"><span styl= e=3D"font-family: =E5=AE=8B=E4=BD=93 , NSimSun , SimSun;">We welcome your c= omments on any aspect of the draft.Thank you for your time and consideratio= n.</span></p><p class=3D"ds-markdown-paragraph" style=3D"margin-top: 16.0px= ;margin-bottom: 16.0px;color: rgb(15,17,21);background-color: rgb(255,255,2= 55);"><span style=3D"font-family: =E5=AE=8B=E4=BD=93 , NSimSun , SimSun;">B= est regards,</span></p><p class=3D"ds-markdown-paragraph" style=3D"margin-t= op: 16.0px;margin-bottom: 16.0px;color: rgb(15,17,21);background-color: rgb= (255,255,255);">Liyan</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=9AAcee&= nbsp;Lindem <[email protected]>,Changwang Lin <li= [email protected]>,Liyan Gong <gongliyan@chinamobile= .com><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-02-25 17:31:28<br/>=E4=B8=BB=E9= =A2=98=EF=BC=9ANew Version Notification for draft-gong-= spring-nd-advertise-srv6-locator-04.txt<br/><br/>A new version&nb= sp;of Internet-Draft<br/>draft-gong-spring-nd-advertise-srv6-locator-0= 4.txt has been successfully<br/>submitted by Liyan= Gong and posted to the<br/>IETF repository.<= br/><br/>Name: draft-gong-spring-nd-advertise-= srv6-locator<br/>Revision: 04<br/>Title: Advert= ise SRv6 Locator Information by IPv6 Neighbor= Discovery<br/>Date: 2026-02-25<br/>Group= : Individual Submission<br/>Pages: &= nbsp; 11<br/>URL: https://www.ietf.= org/archive/id/draft-gong-spring-nd-advertise-srv6-locator-04.txt<br/>Statu= s: https://datatracker.ietf.org/doc/draft-gong-spring-nd-a= dvertise-srv6-locator/<br/>HTML: https://www.i= etf.org/archive/id/draft-gong-spring-nd-advertise-srv6-locator-04.html<br/>= HTMLized: https://datatracker.ietf.org/doc/html/draft-gong-spring-nd-a= dvertise-srv6-locator<br/>Diff: https://author= -tools.ietf.org/iddiff?url2=3Ddraft-gong-spring-nd-advertise-srv6-locator-0= 4<br/><br/>Abstract:<br/><br/> In an SRv6 n= etwork, each SRv6 segment endpoint has at&nbs= p;least one SRv6<br/> Locator. Throug= h the SRv6 locator routes, other SRv6 se= gment nodes<br/> can steer traffic to&= nbsp;that node. This document describes a&nb= sp;method for<br/> an SRv6 endpoint (e= .g., a host or a customer provider edge&= nbsp;(CPE)) to<br/> advertise its SRv6 = ;locator to a neighboring SRv6-aware router u= sing<br/> extensions to the IPv6 Neigh= bor Discovery (ND) protocol. This<br/>  = ; approach eliminates the need to run a&= nbsp;full routing protocol stack on<br/> &nb= sp;simple endpoints, facilitating SRv6 deployment = in controlled, trusted<br/> domains such&nb= sp;as data centers and managed access network= s.<br/><br/><br/><br/>The IETF Secretariat<br/><br/><br/><br/>Sub= ject=EF=BC=9ANew Version Notification for draft-gong-sp= ring-nd-advertise-srv6-locator-04.txt<br/><br/>A new version = ;of Internet-Draft<br/>draft-gong-spring-nd-advertise-srv6-locator-04.= txt has been successfully<br/>submitted by Liyan&n= bsp;Gong and posted to the<br/>IETF repository.<br= /><br/>Name: draft-gong-spring-nd-advertise-sr= v6-locator<br/>Revision: 04<br/>Title: Advertis= e SRv6 Locator Information by IPv6 Neighbor&n= bsp;Discovery<br/>Date: 2026-02-25<br/>Group:&= nbsp; Individual Submission<br/>Pages: &nb= sp; 11<br/>URL: https://www.ietf.or= g/archive/id/draft-gong-spring-nd-advertise-srv6-locator-04.txt<br/>Status:= https://datatracker.ietf.org/doc/draft-gong-spring-nd-adv= ertise-srv6-locator/<br/>HTML: https://www.iet= f.org/archive/id/draft-gong-spring-nd-advertise-srv6-locator-04.html<br/>HT= MLized: https://datatracker.ietf.org/doc/html/draft-gong-spring-nd-adv= ertise-srv6-locator<br/>Diff: https://author-t= ools.ietf.org/iddiff?url2=3Ddraft-gong-spring-nd-advertise-srv6-locator-04<= br/><br/>Abstract:<br/><br/> In an SRv6 net= work, each SRv6 segment endpoint has at = least one SRv6<br/> Locator. Through&= nbsp;the SRv6 locator routes, other SRv6 segm= ent nodes<br/> can steer traffic to&nb= sp;that node. This document describes a = ;method for<br/> an SRv6 endpoint (e.g= ., a host or a customer provider edge&nb= sp;(CPE)) to<br/> advertise its SRv6 l= ocator to a neighboring SRv6-aware router usi= ng<br/> extensions to the IPv6 Neighbo= r Discovery (ND) protocol. This<br/> &= nbsp;approach eliminates the need to run a&nb= sp;full routing protocol stack on<br/>  = ;simple endpoints, facilitating SRv6 deployment in= controlled, trusted<br/> domains such = ;as data centers and managed access networks.= <br/><br/><br/><br/>The IETF Secretariat<br/><br/><br/><br/></p> ------=_Part_1145740_1645374322.1772013311963-- --===============7979053858602435303== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcnRnd2cgbWFp bGluZyBsaXN0IC0tIHJ0Z3dnQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNlbmQgYW4gZW1haWwg dG8gcnRnd2ctbGVhdmVAaWV0Zi5vcmcK --===============7979053858602435303==--