[dhcwg] Re: WG Last Call: draft-ietf-spring-dhc-distribute -srv6-locator-dhcp-09 (Ends 2025-09-11)
Bernie Volz <[email protected]> Wed, 3 Sep 2025 11:01:19 -0400
| Newsgroups | gmane.ietf.dhc,gmane.ietf.spring |
|---|---|
| Message-ID | <[email protected]> |
--===============6870831034789419166== Content-Type: multipart/alternative; boundary=Apple-Mail-C319F209-3768-48DF-91B1-C05DE5BA38DE Content-Transfer-Encoding: 7bit --Apple-Mail-C319F209-3768-48DF-91B1-C05DE5BA38DE Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D= utf-8"></head><body dir=3D"auto">Hi:<div><br></div><div>While I am not a SRv= 6 expert, I think I understand the essentials. And I am writing this with dh= c wg co-chair hat off.</div><div><br></div><div>In terms of DHCPv6 aspects, I= do have two issues to point out:</div><div><br></div><div>1. In section 4.2= ,</div><div><br></div><div>=E2=80=9CWhen the sum LB-len, LN-len, Fun-len, an= d Arg-len exceeds 128 bits, the packet is deemed erroneous and must be disca= rded.=E2=80=9D</div><div><br></div><div>This kind of goes against the norm f= or DHCPv6. And is different for T1 greater than T2 and preferred vs valid li= fetime handling in the document.</div><div><br></div><div>Instead, this shou= ld just invalidate that particular option and processing should continue. A =E2= =80=9Cminor=E2=80=9D configuration or implementation issue should not preven= t other DHCPv6 data in the packet from not being used and can cause a packet= storm as clients keep sending messages without making (at least some) progr= ess.</div><div><br></div><div><br></div><div>2. For Prefix Delegation, which= seems to be the model for SRv6 locators, Confirm messages are not used. Hen= ce, it should be removed from section 5.2?</div><div><br></div><div><br></di= v><div>And a couple of minor nits =E2=80=A6</div><div><br></div><div>1. In s= ection 4.2 there is a reference to 8415bis section 10.2.10.1. The =E2=80=9CT= he details about use of these values=E2=80=A6=E2=80=9D is a bit underclear a= s to whether it is referring to infinity values (which are never mentioned i= n 10.2.10.1) or just the lifetime values in general. Perhaps replace =E2=80=9C= these=E2=80=9D with =E2=80=9Clifetime=E2=80=9D?</div><div><br></div><div>2. I= n section 5.1, first paragraph it might be better to use Solicit, Request, A= dvertise, and Reply instead of lowercase?</div><div><br></div><div>Thanks.</= div><div><div><br id=3D"lineBreakAtBeginningOfSignature"><div dir=3D"ltr">- B= ernie Volz</div><div dir=3D"ltr"><br><blockquote type=3D"cite">On Aug 28, 20= 25, at 4:22=E2=80=AFPM, Alvaro Retana <[email protected]> wrote:<= br><br></blockquote></div><blockquote type=3D"cite"><div dir=3D"ltr">=EF=BB=BF= <style>body { font-family: Helvetica, Arial; font-size: 13px; }</style><= div id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1= 3px;margin:0px;line-height:auto">[cc=E2=80=99iing the dhc WG. Sorry fo= r the extra message, but the datatracker doesn=E2=80=99t have a way to add r= ecipients to the automated message.]</div> <br><p class=3D"airmail_on">On Au= gust 28, 2025 at 4:20:21=E2=80=AFPM, Alvaro Retana via Datatracker (<a href=3D= "mailto:[email protected]">[email protected]</a>) wrote:</p> <blockquote type=3D= "cite" class=3D"clean_bq"><span><div><div></div><div> <br>Subject: WG Last Call: draft-ietf-spring-dhc-distribute-srv6-locator-dhc= p-09 <br>(Ends 2025-09-11) <br> <br>This message starts a 2-week WG Last Call for this document. <br> <br>Abstract: <br> In an SRv6 network, each SRv6 Segment Endpoint Node must be assigned <br> an SRv6 locator, and segment IDs are generated within the address <br> space of this SRv6 locator. This document describes a method for <br> assigning SRv6 locators to SRv6 Segment Endpoint Nodes through <br> DHCPv6. <br> <br>File can be retrieved from: <br><a href=3D"https://datatracker.ietf.org/doc/draft-ietf-spring-dhc-distri= bute-srv6-locator-dhcp/">https://datatracker.ietf.org/doc/draft-ietf-spring-= dhc-distribute-srv6-locator-dhcp/</a> <br> <br>Please review and indicate your support or objection to proceed with the= <br>publication of this document by replying to this email keeping <br><a href=3D"mailto:[email protected]">[email protected]</a> in copy. Objectio= ns should be motivated and suggestions to <br>resolve them are highly appreciated. <br> <br>Authors, and WG participants in general, are reminded again of the <br>Intellectual Property Rights (IPR) disclosure obligations described in B= CP 79 <br>[1]. Appropriate IPR disclosures required for full conformance with the <br>provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware o= f <br>any. Sanctions available for application to violators of IETF IPR Policy= can <br>be found at [3]. <br> <br>Thank you. <br> <br>[1] <a href=3D"https://datatracker.ietf.org/doc/bcp78/">https://datatrac= ker.ietf.org/doc/bcp78/</a> <br>[2] <a href=3D"https://datatracker.ietf.org/doc/bcp79/">https://datatrac= ker.ietf.org/doc/bcp79/</a> <br>[3] <a href=3D"https://datatracker.ietf.org/doc/rfc6701/">https://datatr= acker.ietf.org/doc/rfc6701/</a> <br> <br> <br> <br></div></div></span></blockquote> <div id=3D"bloop_sign_17564124458097989= 12" class=3D"bloop_sign"></div> </div></blockquote></div></div></body></html>= --Apple-Mail-C319F209-3768-48DF-91B1-C05DE5BA38DE-- --===============6870831034789419166== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZGhjd2cgbWFp bGluZyBsaXN0IC0tIGRoY3dnQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNlbmQgYW4gZW1haWwg dG8gZGhjd2ctbGVhdmVAaWV0Zi5vcmcK --===============6870831034789419166==--