[spring] Re: [SRv6OPS] Second WG Last Call: draft-ietf -spring-srv6-security-14 (Ends 2026-06-02)
Weiqiang Cheng <[email protected]> Wed, 20 May 2026 12:53:20 +0800 (CST)
| Newsgroups | gmane.ietf.spring,gmane.ietf.ipv6 |
|---|---|
| Message-ID | <2b006a0d3b94739-00016.Richmail.00003012868091865446@chinamobile.com> |
--===============1446671397929430723== Content-Type: multipart/alternative; boundary="----=_Part_69170_1482586514.1779252800091" ------=_Part_69170_1482586514.1779252800091 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, I have reviewed the draft and support its publication.=20 Two minor comments to help define scope earlier: Section 2 could note that inter-SR-domain scenarios are out of scope (as al= ready stated in Section 4). The point that SRv6 inherits IPv6 vulnerabilities but that this is out of s= cope (currently in Section 6.2.4) could also be mentioned in Section 2 or t= he introduction. This would help readers understand the document=E2=80=99s boundaries from t= he start. Best Regards,=20 Weiqiang -----Original Message-----From: Alvaro Retana via Datatracker <noreply@ietf= .org> Sent: Tuesday, May 19, 2026 3:45 AMTo: draft-ietf-spring-srv6-securit= [email protected] [email protected] [email protected] [email protected]: srv6ops= @ietf.org [email protected]: [spring] Second WG Last Call: draft-ietf-sp= ring-srv6-security-14 (Ends 2026-06-02)This message starts a Second WG Last= Call for:draft-ietf-spring-srv6-security-14This Working Group Last Call en= ds on 2026-06-02Abstract: SRv6 is a traffic engineering, encapsulation an= d steering mechanism utilizing IPv6 addresses to identify segments in a p= re-defined policy. This document discusses security considerations in SR= v6 networks, including the potential threats and the possible mitigation = methods. The document does not define any new security protocols or ex= tensions to existing protocols.File can be retrieved from:Please review and= indicate your support or objection to proceed with the publication of this= document by replying to this email keeping [email protected] in copy. Object= ions should be explained and suggestions to resolve them are highly appreci= ated.Authors, and WG participants in general, are reminded of the Intellect= ual Property Rights (IPR) disclosure obligations described in BCP 79 [1].Ap= propriate IPR disclosures required for full conformance with the provisions= of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.Sancti= ons available for application to violators of IETF IPR Policy can be found = at [3].Thank you.[1] https://datatracker.ietf.org/doc/bcp78/[2] https://dat= atracker.ietf.org/doc/bcp79/[3] https://datatracker.ietf.org/doc/rfc6701/Th= e IETF datatracker status page for this Internet-Draft is:https://datatrack= er.ietf.org/doc/draft-ietf-spring-srv6-security/There is also an HTML versi= on available at:https://www.ietf.org/archive/id/draft-ietf-spring-srv6-secu= rity-14.htmlA diff from the previous version is available at:https://author= -tools.ietf.org/iddiff?url2=3Ddraft-ietf-spring-srv6-security-14___________= ____________________________________spring mailing list -- [email protected]= o unsubscribe send an email to [email protected]_______________________= ________________________SRv6OPS mailing list -- [email protected] unsubscr= ibe send an email to [email protected]=EF=BC=9A[SRv6OPS] Re: [s= pring] Second WG Last Call: draft-ietf-spring-srv6-security-14 (Ends 2026-0= 6-02)I support the WGLC. This is an important work for SRv6.Thanks to the a= uthors.Cheng-----Original Message-----From: Alvaro Retana via Datatracker <= [email protected]> Sent: Tuesday, May 19, 2026 3:45 AMTo: draft-ietf-spring-= [email protected] [email protected] [email protected] [email protected]= mCc: [email protected] [email protected]: [spring] Second WG Last Call: d= raft-ietf-spring-srv6-security-14 (Ends 2026-06-02)This message starts a Se= cond WG Last Call for:draft-ietf-spring-srv6-security-14This Working Group = Last Call ends on 2026-06-02Abstract: SRv6 is a traffic engineering, enca= psulation and steering mechanism utilizing IPv6 addresses to identify seg= ments in a pre-defined policy. This document discusses security consider= ations in SRv6 networks, including the potential threats and the possible= mitigation methods. The document does not define any new security proto= cols or extensions to existing protocols.File can be retrieved from:Pleas= e review and indicate your support or objection to proceed with the publica= tion of this document by replying to this email keeping [email protected] in = copy. Objections should be explained and suggestions to resolve them are hi= ghly appreciated.Authors, and WG participants in general, are reminded of t= he Intellectual Property Rights (IPR) disclosure obligations described in B= CP 79 [1].Appropriate IPR disclosures required for full conformance with th= e provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware o= f any.Sanctions available for application to violators of IETF IPR Policy c= an be found at [3].Thank you.[1] https://datatracker.ietf.org/doc/bcp78/[2]= https://datatracker.ietf.org/doc/bcp79/[3] https://datatracker.ietf.org/do= c/rfc6701/The IETF datatracker status page for this Internet-Draft is:https= ://datatracker.ietf.org/doc/draft-ietf-spring-srv6-security/There is also a= n HTML version available at:https://www.ietf.org/archive/id/draft-ietf-spri= ng-srv6-security-14.htmlA diff from the previous version is available at:ht= tps://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-spring-srv6-security-1= 4_______________________________________________spring mailing list -- spri= [email protected] unsubscribe send an email to [email protected]___________= ____________________________________SRv6OPS mailing list -- [email protected]= gTo unsubscribe send an email to [email protected] ------=_Part_69170_1482586514.1779252800091 Content-Type: text/html;charset=UTF-8 Content-Transfer-Encoding: quoted-printable <p><span style=3D"background-color: #FFFFFF; color: #0F1115; font-family: q= uote-cjk-patch, Inter, system-ui, -apple-system, BlinkMacSystemFont, "= Segoe UI", Roboto, Oxygen, Ubuntu, Cantarell, "Open Sans", &= quot;Helvetica Neue", sans-serif;">Hi,</span></p><p class=3D"ds-markdo= wn-paragraph" style=3D"margin: 16px 0px; color: rgb(15, 17, 21); font-famil= y: quote-cjk-patch, Inter, system-ui, -apple-system, BlinkMacSystemFont, &q= uot;Segoe UI", Roboto, Oxygen, Ubuntu, Cantarell, "Open Sans"= ;, "Helvetica Neue", sans-serif; white-space: normal; background-= color: rgb(255, 255, 255);"><span class=3D""><span style=3D"color: #0F1115;= font-family: quote-cjk-patch, Inter, system-ui, -apple-system, BlinkMacSys= temFont, "Segoe UI", Roboto, Oxygen, Ubuntu, Cantarell, "Ope= n Sans", "Helvetica Neue", sans-serif; background-color: #FF= FFFF;">I have reviewed the draft and support its publication. </span><= /span></p><p class=3D"ds-markdown-paragraph" style=3D"margin: 16px 0px; col= or: rgb(15, 17, 21); font-family: quote-cjk-patch, Inter, system-ui, -apple= -system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxygen, Ubuntu, = Cantarell, "Open Sans", "Helvetica Neue", sans-serif; w= hite-space: normal; background-color: rgb(255, 255, 255);"><span class=3D""= ></span></p><p class=3D"ds-markdown-paragraph" style=3D"margin: 16px 0px; c= olor: rgb(15, 17, 21); font-family: quote-cjk-patch, Inter, system-ui, -app= le-system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxygen, Ubuntu= , Cantarell, "Open Sans", "Helvetica Neue", sans-serif;= white-space: normal; background-color: rgb(255, 255, 255);"><span class=3D= "">Two minor comments to help define scope earlier:</span></p><ol start=3D"= 1" style=3D"margin: 0px; padding: 0px 0px 0px 30px; color: rgb(15, 17, 21);= font-family: quote-cjk-patch, Inter, system-ui, -apple-system, BlinkMacSys= temFont, "Segoe UI", Roboto, Oxygen, Ubuntu, Cantarell, "Ope= n Sans", "Helvetica Neue", sans-serif; white-space: normal; = background-color: rgb(255, 255, 255); width: 95%;" class=3D" list-paddingle= ft-2"><li style=3D"background-position: 0px 3px; background-repeat: no-repe= at; clear: both;"><p class=3D"ds-markdown-paragraph"><span class=3D"">Secti= on 2 could note that inter-SR-domain scenarios are out of scope (as already= stated in Section 4).</span></p></li><li style=3D"background-position: 0px= 3px; background-repeat: no-repeat; clear: both;"><p class=3D"ds-markdown-p= aragraph"><span class=3D"">The point that SRv6 inherits IPv6 vulnerabilitie= s but that this is out of scope (currently in Section 6.2.4) could also be = mentioned in Section 2 or the introduction.</span></p></li></ol><p class=3D= "ds-markdown-paragraph" style=3D"margin: 16px 0px; color: rgb(15, 17, 21); = font-family: quote-cjk-patch, Inter, system-ui, -apple-system, BlinkMacSyst= emFont, "Segoe UI", Roboto, Oxygen, Ubuntu, Cantarell, "Open= Sans", "Helvetica Neue", sans-serif; white-space: normal; b= ackground-color: rgb(255, 255, 255);"><span class=3D"">This would help read= ers understand the document=E2=80=99s boundaries from the start.</span></p>= <p class=3D"ds-markdown-paragraph" style=3D"margin-top: 16px; color: rgb(15= , 17, 21); font-family: quote-cjk-patch, Inter, system-ui, -apple-system, B= linkMacSystemFont, "Segoe UI", Roboto, Oxygen, Ubuntu, Cantarell,= "Open Sans", "Helvetica Neue", sans-serif; white-space= : normal; background-color: rgb(255, 255, 255);"><span class=3D"">Best Rega= rds, </span></p><p class=3D"ds-markdown-paragraph" style=3D"margin-top= : 16px; color: rgb(15, 17, 21); font-family: quote-cjk-patch, Inter, system= -ui, -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxyge= n, Ubuntu, Cantarell, "Open Sans", "Helvetica Neue", sa= ns-serif; white-space: normal; background-color: rgb(255, 255, 255);"><span= class=3D"">Weiqiang</span></p><p><br/></p><p><br/><br/></p><br/><p><br/><b= r/><br/>-----Original Message-----<br/>From: Alvaro Retana&n= bsp;via Datatracker <[email protected]> <br/>Sent: = ;Tuesday, May 19, 2026 3:45 AM<br/>To: draft-= [email protected]; [email protected]; sprin= [email protected]; [email protected]<br/>Cc: [email protected]; ipv6@ie= tf.org<br/>Subject: [spring] Second WG Last Call:&= nbsp;draft-ietf-spring-srv6-security-14 (Ends 2026-06-02)<br/><br= />This message starts a Second WG Last C= all for:<br/>draft-ietf-spring-srv6-security-14<br/><br/>This Wor= king Group Last Call ends on 2026-06-02<br/><= br/>Abstract:<br/> SRv6 is a traffic e= ngineering, encapsulation and steering mechanism<br/>&n= bsp; utilizing IPv6 addresses to identify&nb= sp;segments in a pre-defined<br/> policy.&n= bsp; This document discusses security consideratio= ns in SRv6<br/> networks, including th= e potential threats and the possible mitigati= on<br/> methods. The document does&nb= sp;not define any new security protocols or<b= r/> extensions to existing protocols.<br/><= br/>File can be retrieved from:<br/><br/>Please re= view and indicate your support or objection&n= bsp;to proceed with the publication of this&n= bsp;document by replying to this email keepin= g [email protected] in copy. Objections should = be explained and suggestions to resolve them&= nbsp;are highly appreciated.<br/><br/>Authors, and WG&n= bsp;participants in general, are reminded of = the Intellectual Property Rights (IPR) disclosure&= nbsp;obligations described in BCP 79 [1].<br/>Appr= opriate IPR disclosures required for full con= formance with the provisions of BCP 78 [= 1] and BCP 79 [2] must be filed, if= you are aware of any.<br/>Sanctions availabl= e for application to violators of IETF I= PR Policy can be found at [3].<br/><br/>Thank= you.<br/><br/>[1] https://datatracker.ietf.org/doc/bcp78/<br/>[2= ] https://datatracker.ietf.org/doc/bcp79/<br/>[3] https://datatra= cker.ietf.org/doc/rfc6701/<br/><br/>The IETF datatracker sta= tus page for this Internet-Draft is:<br/>https://d= atatracker.ietf.org/doc/draft-ietf-spring-srv6-security/<br/><br/>There&nbs= p;is also an HTML version available at:<br/>h= ttps://www.ietf.org/archive/id/draft-ietf-spring-srv6-security-14.html<br/>= <br/>A diff from the previous version is = ;available at:<br/>https://author-tools.ietf.org/iddiff?url2=3Ddraft-i= etf-spring-srv6-security-14<br/><br/>______________________________________= _________<br/>spring mailing list -- [email protected]<br= />To unsubscribe send an email to spring-leav= [email protected]<br/>_______________________________________________<br/>SRv6OPS&= nbsp;mailing list -- [email protected]<br/>To unsubscrib= e send an email to [email protected]<br/><br/= >Subject=EF=BC=9A[SRv6OPS] Re: [spring] Second WG = Last Call: draft-ietf-spring-srv6-security-14 (Ends 202= 6-06-02)<br/><br/>I support the WGLC. This is = ;an important work for SRv6.<br/><br/>Thanks to&nb= sp;the authors.<br/><br/>Cheng<br/><br/><br/><br/>-----Original M= essage-----<br/>From: Alvaro Retana via Datatracker&nbs= p;<[email protected]> <br/>Sent: Tuesday, May 19,&= nbsp;2026 3:45 AM<br/>To: draft-ietf-spring-srv6-security@ie= tf.org; [email protected]; [email protected]; zali@cisco.= com<br/>Cc: [email protected]; [email protected]<br/>Subject: [sp= ring] Second WG Last Call: draft-ietf-spring-srv6-= security-14 (Ends 2026-06-02)<br/><br/>This message sta= rts a Second WG Last Call for:<br/>draft-ietf= -spring-srv6-security-14<br/><br/>This Working Group Last&nb= sp;Call ends on 2026-06-02<br/><br/>Abstract:<br/> &nbs= p; SRv6 is a traffic engineering, encapsulati= on and steering mechanism<br/> utilizing&nb= sp;IPv6 addresses to identify segments in a&n= bsp;pre-defined<br/> policy. This document= discusses security considerations in SRv6<br/>&nb= sp; networks, including the potential threat= s and the possible mitigation<br/> met= hods. The document does not define any&= nbsp;new security protocols or<br/> extensi= ons to existing protocols.<br/><br/>File can be&nb= sp;retrieved from:<br/><br/>Please review and indicate&= nbsp;your support or objection to proceed wit= h the publication of this document by re= plying to this email keeping [email protected] = in copy. Objections should be explained and&n= bsp;suggestions to resolve them are highly ap= preciated.<br/><br/>Authors, and WG participants in&nbs= p;general, are reminded of the Intellectual P= roperty Rights (IPR) disclosure obligations descri= bed in BCP 79 [1].<br/>Appropriate IPR disclo= sures required for full conformance with the&= nbsp;provisions of BCP 78 [1] and BCP 79= [2] must be filed, if you are awar= e of any.<br/>Sanctions available for application&= nbsp;to violators of IETF IPR Policy can = ;be found at [3].<br/><br/>Thank you.<br/><br/>[1] = ;https://datatracker.ietf.org/doc/bcp78/<br/>[2] https://datatracker.i= etf.org/doc/bcp79/<br/>[3] https://datatracker.ietf.org/doc/rfc6701/<b= r/><br/>The IETF datatracker status page for = this Internet-Draft is:<br/>https://datatracker.ietf.org/doc/draf= t-ietf-spring-srv6-security/<br/><br/>There is also an = HTML version available at:<br/>https://www.ietf.org/archive/= id/draft-ietf-spring-srv6-security-14.html<br/><br/>A diff from&n= bsp;the previous version is available at:<br/>http= s://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-spring-srv6-security-14<= br/><br/>_______________________________________________<br/>spring ma= iling list -- [email protected]<br/>To unsubscribe s= end an email to [email protected]<br/>_____________= __________________________________<br/>SRv6OPS mailing list = -- [email protected]<br/>To unsubscribe send an ema= il to [email protected]<br/><br/></p> ------=_Part_69170_1482586514.1779252800091-- --===============1446671397929430723== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18Kc3ByaW5nIG1h aWxpbmcgbGlzdCAtLSBzcHJpbmdAaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFp bCB0byBzcHJpbmctbGVhdmVAaWV0Zi5vcmcK --===============1446671397929430723==--