For the record, I approve the version in the provided md file. Thanks all!
On 23.02.26, 13:45, "Claudio Porfiri" <[email protected] <mailto:[email protected]>> wrote: Dear Editors, we have revised the rfc9928.md file, addressing the indicated points and answering the questions. The updated version is attached. Thank you and best regards Claudio, Mirja, Jari > -----Original Message----- > From: [email protected] <mailto:[email protected]> > <[email protected] <mailto:[email protected]>> > Sent: Wednesday, February 18, 2026 8:01 PM > To: Claudio Porfiri <[email protected] > <mailto:[email protected]>>; [email protected] > <mailto:[email protected]>; > Jari Arkko <[email protected] <mailto:[email protected]>>; Mirja > Kuehlewind > <[email protected] <mailto:[email protected]>> > Cc: [email protected] <mailto:[email protected]>; > [email protected] <mailto:[email protected]>; [email protected] > <mailto:[email protected]>; > [email protected] <mailto:[email protected]>; [email protected] > <mailto:[email protected]>; [email protected] > <mailto:[email protected]> > Subject: Re: AUTH48: RFC-to-be 9928 <draft-ietf-dhc-dhcpv4-over-dhcpv6-ra- > 06> for your review > > Authors, > > While reviewing this document during AUTH48, please resolve (as necessary) the > following questions, which are also in the source file. > > 1) <!-- [rfced] Please review the text below. We were unable to find "L3RA" > used > in > [draft-ietf-dhc-rfc8415bis] (now published as RFC 9915). > > Original: > > Similarly, the specifications for DHCPv6 Relay Agents such as > Lightweight DHCPv6 Relay Agent (LDRA) [RFC6221] or DHCPv6 Relay Agent > (L3RA) [draft-ietf-dhc-rfc8415bis] do not foresee the possibility to > handle legacy DHCPv4, other than implementing DHCP 4o6 in the client. > > --> > > > 2) <!-- [rfced] Section 2: > > a) May we adjust the items in this list to appear in alphabetical order? > > b) May we make these list items consistent as follows? > > Original: > > * DHCP: If not otherwise specified, DHCP refers to DHCPv4 and/or > DHCPv6. > > * DHCPv4: DHCP as defined in [RFC2131]. > > * DHCPv4 over DHCPv6 (or 4o6): The architecture, the procedures, and > the protocols specified in the DHCPv4-over-DHCPv6 document > [RFC7341]. > > * DHCP Relay Agent: This is a concept in all of the following > protocols, although the details differ between them: BOOTP > [RFC951] [RFC1542], DHCPv4 [RFC2131] [RFC2132], and DHCPv6 > [draft-ietf-dhc-rfc8415bis]. > > * Lightweight DHCPv6 Relay Agent (or LDRA): This is an extension of > the original DHCPv6 Relay Agent specification, to allow layer- > 2-only devices to perform a Relay Agent function [RFC6221]. > > * DHCPv4 over DHCPv6 Relay Agent (or 4o6RA): Refers to a Relay Agent > that implements the 4o6 transport as specified in this document. > > Perhaps: > > DHCP: > Refers to DHCPv4 and/or DHCPv6 if not otherwise specified. > > DHCPv4: > Refers to DHCP as defined in [RFC2131]. > > DHCPv4 over DHCPv6 (DHCP 4o6): > Refers to the architecture, the procedures, and the protocols specified in > the DHCPv4-over-DHCPv6 document [RFC7341]. > > (etc.) > > --> > > > 3) <!-- [rfced] Per Section 3.6 of RFC 7322 ("RFC Style Guide"), abbreviations > should be expanded upon first use. How and where should "CPE" be expanded as > it appears in Figure 4? > > Original: > > In a simple case, where the same node hosts the 4o6RA and the DHCP4o6 > server, it might be enough to only use 4o6RA, as shown in Figure 4. > > Perhaps: > > In a simple case, where the same node hosts the 4o6RA and the DHCP 4o6 > server, it might be enough to only use 4o6RA, as shown in Figure 4, where > CPE stands for "Customer Premises Equipment". > > --> > > > 4) <!-- [rfced] Security Considerations: > > a) Would the following adjustment clarify what "the 4o6 DHCP specification" > refers to? > > b) Please note that we have changed "4o6 DHCP" to "DHCP 4o6" in this > section for consistency with the rest of the document. > > Original: > > This document does not change anything else in the 4o6 DHCP specification > and therefore the security considerations of [RFC7341] still apply. > > Perhaps: > > This document does not change anything else in the DHCP 4o6 specification > [RFC7341]; > therefore, the security considerations of that document still apply. > > --> > > > 5) <!-- [rfced] Appendix A: Please review our questions and suggested updates > to > the text below, including the following items: > > a) Should the abbreviation for "Baseband Units (BB)" be updated to "Baseband > Units (BBUs)" > as seen in the text below? If so, please note that we would also update > instances > of > "BB"/"BBs" to "BBU"/"BBUs" accordingly throughout the rest of this section as > well. > > b) Should the abbreviation for "Radio Fronthaul Network (FH)" be adjusted for > clarity? > > Original: > > In 3GPP mobile network architecture, the User Equipments (UE) are > connected via Radio Access Network (RAN). RAN is built up with > Baseband Units (BB) and Radio Units (RU). Radio Fronthaul Network > (FH) connects RU and BB, each of RU and BB is an IP host, they may > support IPv4 only, IPv6 only or both depending on the vendor and the > model. > > Perhaps: > > In 3GPP mobile network architecture, the User Equipment (UE) is > connected via a Radio Access Network (RAN). RAN is built up with > Baseband Units (BBUs) and Radio Units (RUs). A radio Fronthaul (FH) network > connects RUs and BBUs. Each RU and BBU is an IP host, and they may > support IPv4 only, IPv6 only, or both, depending on the vendor and the > model. > > --> > > > 6) <!-- [rfced] Terminology and Abbreviations: > > a) We note that the phrase "4o6" appears a few times by itself throughout this > document. For consistency and context, should these instances be updated to > "DHCP 4o6"? > > We have provided a few examples below: > > the 4o6 transport > are expected to be compliant with 4o6 > the introduction of 4o6 at the edge > moving 4o6 to a intermediate node > a 4o6 client > > > b) We note the following phrases appear after their abbreviations are > introduced. For consistency, should these terms (on the left) be updated to > their abbreviated form (on the right) after first use? > > Expansion -> Abbreviation > > DHCPv4-over-DHCPv6 -> DHCP 4o6 > 4o6 Relay Agent -> 4o6RA > Layer 2 -> L2 > > > c) FYI - We have added expansions for abbreviations upon first use > per Section 3.6 of RFC 7322 ("RFC Style Guide"). Please review each > expansion in the document carefully to ensure correctness. > > Bootstrap Protocol (BOOTP) > Layer 2 (L2) > > --> > > > 7) <!-- [rfced] Please review the "Inclusive Language" portion of the online > Style Guide > <https://www.rfc-/ <https://www.rfc-/> > editor.org%2Fstyleguide%2Fpart2%2F%23inclusive_language&data=05%7C02%7 > Cclaudio.porfiri%40ericsson.com%7C9285bc57404341d4ef7008de6f201c99%7C9 > 2e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C639070381061535298%7CU > nknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCI > sIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata > =NUbm8Awlt6vZFqUs9ZWnwkV%2FsGtuzSfOKBfufYW3wak%3D&reserved=0> > and let us know if any changes are needed. Updates of this nature typically > result in more precise language, which is helpful for readers. > > Note that our script did not flag any words in particular, but this should > still be reviewed as a best practice. --> > > > Thank you. > Alanna Paloma and Kaelin Foody > RFC Production Center > > > On Feb 18, 2026, at 11:00 AM, [email protected] > <mailto:[email protected]> wrote: > > *****IMPORTANT***** > > Updated 2026/02/18 > > RFC Author(s): > -------------- > > Your document has now entered AUTH48. > > The document was edited in kramdown-rfc as part of the RPC pilot test (see > https://www.rfc-/ <https://www.rfc-/> > editor.org%2Frpc%2Fwiki%2Fdoku.php%3Fid%3Dpilot_test_kramdown_rfc&data > =05%7C02%7Cclaudio.porfiri%40ericsson.com%7C9285bc57404341d4ef7008de6 > f201c99%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C639070381061 > 585387%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLj > AuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C% > 7C%7C&sdata=nFyZNpyPND%2FCGqycymyikpPkl%2B4oeBR3v4591LgK%2B%2Bc > %3D&reserved=0). > > Please review the procedures for AUTH48 using kramdown-rfc: > > https://www.rfc-/ <https://www.rfc-/> > editor.org%2Frpc%2Fwiki%2Fdoku.php%3Fid%3Dpilot_test_instructions_completi > ng_auth48_using_kramdown&data=05%7C02%7Cclaudio.porfiri%40ericsson.com > %7C9285bc57404341d4ef7008de6f201c99%7C92e84cebfbfd47abbe52080c6b87 > 953f%7C0%7C0%7C639070381061631454%7CUnknown%7CTWFpbGZsb3d8eyJF > bXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFp > bCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=c03q78ueMElHy2I09RtQanac > um3Md7tmBFTUni7FPE4%3D&reserved=0 > > Once your document has completed AUTH48, it will be published as > an RFC. > > > Files > ----- > > The files are available here: > > https://www.rfc-/ <https://www.rfc-/> > editor.org%2Fauthors%2Frfc9928.md&data=05%7C02%7Cclaudio.porfiri%40erics > son.com%7C9285bc57404341d4ef7008de6f201c99%7C92e84cebfbfd47abbe520 > 80c6b87953f%7C0%7C0%7C639070381061691741%7CUnknown%7CTWFpbGZs > b3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFO > IjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=49d38B3jMkJrjpCFKn > O8Z5LW%2FlLFA2V4LhI%2FsAyAYmo%3D&reserved=0 > > https://www.rfc-/ <https://www.rfc-/> > editor.org%2Fauthors%2Frfc9928.html&data=05%7C02%7Cclaudio.porfiri%40eri > csson.com%7C9285bc57404341d4ef7008de6f201c99%7C92e84cebfbfd47abbe5 > 2080c6b87953f%7C0%7C0%7C639070381061736038%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIk > FOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=w6JoWvKuBuB7t3 > T10qkpeSxlTQBViqTzkaStsKzAoW8%3D&reserved=0 > > https://www.rfc-/ <https://www.rfc-/> > editor.org%2Fauthors%2Frfc9928.pdf&data=05%7C02%7Cclaudio.porfiri%40erics > son.com%7C9285bc57404341d4ef7008de6f201c99%7C92e84cebfbfd47abbe520 > 80c6b87953f%7C0%7C0%7C639070381061775326%7CUnknown%7CTWFpbGZs > b3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFO > IjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=5pvzTMFBG88PiOjYe > %2B%2FqoTQ5oJlrIoVa%2B0rshYygerw%3D&reserved=0 > > https://www.rfc-/ <https://www.rfc-/> > editor.org%2Fauthors%2Frfc9928.txt&data=05%7C02%7Cclaudio.porfiri%40erics > son.com%7C9285bc57404341d4ef7008de6f201c99%7C92e84cebfbfd47abbe520 > 80c6b87953f%7C0%7C0%7C639070381061810730%7CUnknown%7CTWFpbGZs > b3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFO > IjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Y0Snjgf9uNWXkJj1j7 > GCMyN43%2Fyx8jwUp0poBTKzZd4%3D&reserved=0 > > Diff file of the text: > > https://www.rfc-/ <https://www.rfc-/> > editor.org%2Fauthors%2Frfc9928- > diff.html&data=05%7C02%7Cclaudio.porfiri%40ericsson.com%7C9285bc5740434 > 1d4ef7008de6f201c99%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C > 639070381061863119%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRy > dWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D > %3D%7C0%7C%7C%7C&sdata=V%2BxMgUetp%2BO4AExrAlqiPMyTHNDUI993SK > fju9OrJtM%3D&reserved=0 > > https://www.rfc-/ <https://www.rfc-/> > editor.org%2Fauthors%2Frfc9928- > rfcdiff.html&data=05%7C02%7Cclaudio.porfiri%40ericsson.com%7C9285bc57404 > 341d4ef7008de6f201c99%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0% > 7C639070381061913085%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOn > RydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3 > D%3D%7C0%7C%7C%7C&sdata=K4cPdoooMGBvlkqreh0i9yN0UDh1AU8%2F3i5C > rF%2B2YkQ%3D&reserved=0 (side by side) > > Diff of the kramdown: > > https://www.rfc-/ <https://www.rfc-/> > editor.org%2Fauthors%2Frfc9928-md- > diff.html&data=05%7C02%7Cclaudio.porfiri%40ericsson.com%7C9285bc5740434 > 1d4ef7008de6f201c99%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C > 639070381061956519%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRy > dWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D > %3D%7C0%7C%7C%7C&sdata=XL90fWqUcvNutj8Ws%2BFNklxLkZjIL%2FfjfM9SZ > Hxk8Jw%3D&reserved=0 > > https://www.rfc-/ <https://www.rfc-/> > editor.org%2Fauthors%2Frfc9928-md- > rfcdiff.html&data=05%7C02%7Cclaudio.porfiri%40ericsson.com%7C9285bc57404 > 341d4ef7008de6f201c99%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0% > 7C639070381061996806%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOn > RydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3 > D%3D%7C0%7C%7C%7C&sdata=MB6wj%2BAD0%2BwFIQMBHKlxnVH%2Bgf3aU > KAT6M4itoZ%2F9mU%3D&reserved=0 (side by side) > > > Tracking progress > ----------------- > > The details of the AUTH48 status of your document are here: > https://www.rfc-/ <https://www.rfc-/> > editor.org%2Fauth48%2Frfc9928&data=05%7C02%7Cclaudio.porfiri%40ericsson. > com%7C9285bc57404341d4ef7008de6f201c99%7C92e84cebfbfd47abbe52080c6 > b87953f%7C0%7C0%7C639070381062044083%7CUnknown%7CTWFpbGZsb3d8 > eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiT > WFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=uSJsYr8%2Fl%2B2Aq2z2n > 5VQwmhlvGIJyTgFdrGnHOL9dsQ%3D&reserved=0 > > > Please let us know if you have any questions. > > Thank you for your cooperation, > > RFC Editor > > -------------------------------------- > RFC9928 (draft-ietf-dhc-dhcpv4-over-dhcpv6-ra-06) > > Title : DHCPv4-over-DHCPv6 with Relay Agent Support > Author(s) : C. Porfiri, S. Krishnan, J. Arkko, M. Kühlewind > WG Chair(s) : Timothy Winters, Bernie Volz > > Area Director(s) : Erik Kline, Éric Vyncke -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
