[dhcwg] Re: RFC 9928 on DHCPv4 over DHCPv6 with Relay Agent Support

"Eric Vyncke \(evyncke\)" <[email protected]> Thu, 2 Apr 2026 07:57:47 +0000
Newsgroups gmane.ietf.dhc
Message-ID <PH0PR11MB49660BE0EC39FDC491EFED11A951A@PH0PR11MB4966.namprd11.prod.outlook.com>
--===============0241144613608853470==
Content-Language: en-GB
Content-Type: multipart/alternative;
 boundary="_000_PH0PR11MB49660BE0EC39FDC491EFED11A951APH0PR11MB4966namp_"

--_000_PH0PR11MB49660BE0EC39FDC491EFED11A951APH0PR11MB4966namp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Congratulations to the authors (especially to Claudio as I think it is your=
 first RFC). This draft has morphed a lot since the -00, a long path but it=
 is now published.

Regards

-=E9ric

From: [email protected] <[email protected]>
Date: Tuesday, 31 March 2026 at 22:06
To: [email protected] <[email protected]>, [email protected]=
g <[email protected]>
Cc: [email protected] <[email protected]>, drafts-update-re=
[email protected] <[email protected]>, [email protected] <[email protected]>
Subject: [dhcwg] RFC 9928 on DHCPv4 over DHCPv6 with Relay Agent Support

A new Request for Comments is now available in online RFC libraries.


        RFC 9928

        Title:      DHCPv4 over DHCPv6 with Relay Agent Support
        Author:     C. Porfiri,
                    S. Krishnan,
                    J. Arkko,
                    M. K=FChlewind
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2026
        Mailbox:    [email protected],
                    [email protected],
                    [email protected],
                    [email protected]
        Pages:      12
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dhc-dhcpv4-over-dhcpv6-ra-06.txt

        URL:        https://www.rfc-editor.org/info/rfc9928

        DOI:        10.17487/RFC9928

This document describes a mechanism for networks with legacy
IPv4-only clients to use services provided by DHCPv4 over DHCPv6 in a
Relay Agent. RFC 7341 specifies the use of DHCPv4 over DHCPv6 in the
client only. This document specifies an approach based on RFC 7341
that allows a Relay Agent to implement the DHCPv4-over-DHCPv6
encapsulation and decapsulation of DHCPv4 messages in DHCPv6 messages
on behalf of a DHCPv4 client.

This document is a product of the Dynamic Host Configuration Working Group =
of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestion=
s
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team

_______________________________________________
dhcwg mailing list -- [email protected]
To unsubscribe send an email to [email protected]

--_000_PH0PR11MB49660BE0EC39FDC491EFED11A951APH0PR11MB4966namp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body>
<div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se=
rif; font-size: 12pt; color: rgb(0, 0, 0);">
Congratulations to the authors (especially to Claudio as I think it is your=
 first RFC). This draft has morphed a lot since the -00, a long path but it=
 is now published.</div>
<div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se=
rif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se=
rif; font-size: 12pt; color: rgb(0, 0, 0);">
Regards</div>
<div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se=
rif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se=
rif; font-size: 12pt; color: rgb(0, 0, 0);">
-=E9ric</div>
<div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se=
rif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id=3D"mail-editor-reference-message-container">
<div class=3D"ms-outlook-mobile-reference-message skipProofing">
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
</div>
<div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"te=
xt-align: left; padding: 3pt 0in 0in; border-width: 1pt medium medium; bord=
er-style: solid none none; border-color: rgb(181, 196, 223) currentcolor cu=
rrentcolor; font-family: Aptos; font-size: 12pt; color: black;">
<b>From: </b>[email protected] &lt;[email protected]&gt;<br=
>
<b>Date: </b>Tuesday, 31 March 2026 at 22:06<br>
<b>To: </b>[email protected] &lt;[email protected]&gt;, rfc-dist@=
rfc-editor.org &lt;[email protected]&gt;<br>
<b>Cc: </b>[email protected] &lt;[email protected]&gt;, dra=
[email protected] &lt;[email protected]&gt;, [email protected] =
&lt;[email protected]&gt;<br>
<b>Subject: </b>[dhcwg] RFC 9928 on DHCPv4 over DHCPv6 with Relay Agent Sup=
port<br>
<br>
</div>
<div class=3D"PlainText" style=3D"font-size: 11pt;">A new Request for Comme=
nts is now available in online RFC libraries.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; RFC 9928<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Title:&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; DHCPv4 over DHCPv6 with Relay Agent Support<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Author:&nbsp;&nbsp;&nbsp;&nbsp; =
C. Porfiri,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; S. Krishnan,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; J. Arkko,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; M. K=FChlewind<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Status:&nbsp;&nbsp;&nbsp;&nbsp; =
Standards Track<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Stream:&nbsp;&nbsp;&nbsp;&nbsp; =
IETF<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Date:&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; March 2026<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mailbox:&nbsp;&nbsp;&nbsp; claud=
[email protected],<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [email protected],<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [email protected],<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [email protected]<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Pages:&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; 12<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Updates/Obsoletes/SeeAlso:&nbsp;=
&nbsp; None<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I-D Tag:&nbsp;&nbsp;&nbsp; draft=
-ietf-dhc-dhcpv4-over-dhcpv6-ra-06.txt<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; URL:&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; <a href=3D"https://www.rfc-editor.org/info/rfc9928" data-out=
look-id=3D"f46414c2-02d6-430f-8ed8-26512d5a1526">
https://www.rfc-editor.org/info/rfc9928</a><br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DOI:&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; 10.17487/RFC9928<br>
<br>
This document describes a mechanism for networks with legacy<br>
IPv4-only clients to use services provided by DHCPv4 over DHCPv6 in a<br>
Relay Agent. RFC 7341 specifies the use of DHCPv4 over DHCPv6 in the<br>
client only. This document specifies an approach based on RFC 7341<br>
that allows a Relay Agent to implement the DHCPv4-over-DHCPv6<br>
encapsulation and decapsulation of DHCPv4 messages in DHCPv6 messages<br>
on behalf of a DHCPv4 client.<br>
<br>
This document is a product of the Dynamic Host Configuration Working Group =
of the IETF.<br>
<br>
This is now a Proposed Standard.<br>
<br>
STANDARDS TRACK: This document specifies an Internet Standards Track<br>
protocol for the Internet community, and requests discussion and suggestion=
s<br>
for improvements.&nbsp; Please refer to the current edition of the Official=
<br>
Internet Protocol Standards (<a href=3D"https://www.rfc-editor.org/standard=
s" data-outlook-id=3D"8c2c4925-475b-44f7-8393-655b6b2284bf">https://www.rfc=
-editor.org/standards</a>) for the<br>
standardization state and status of this protocol.&nbsp; Distribution of th=
is<br>
memo is unlimited.<br>
<br>
This announcement is sent to the IETF-Announce and rfc-dist lists.<br>
To subscribe or unsubscribe, see<br>
&nbsp; <a href=3D"https://www.ietf.org/mailman/listinfo/ietf-announce" data=
-outlook-id=3D"aee1a9f0-c914-4d5a-a4be-137481d2d4fa">
https://www.ietf.org/mailman/listinfo/ietf-announce</a><br>
&nbsp; <a href=3D"https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist"=
 data-outlook-id=3D"6b9f0e8b-7813-4571-86d1-cf055a5c158f">
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist</a><br>
<br>
For searching the RFC series, see <a href=3D"https://www.rfc-editor.org/sea=
rch" data-outlook-id=3D"644cc0fa-00c0-435d-85b4-d441ee58005b">
https://www.rfc-editor.org/search</a><br>
For downloading RFCs, see <a href=3D"https://www.rfc-editor.org/retrieve/bu=
lk" data-outlook-id=3D"f5b6dd03-292e-4326-ac30-06711bb06458">
https://www.rfc-editor.org/retrieve/bulk</a><br>
<br>
Requests for special distribution should be addressed to either the<br>
author of the RFC in question, or to [email protected].&nbsp; Unles=
s<br>
specifically noted otherwise on the RFC itself, all RFCs are for<br>
unlimited distribution.<br>
<br>
<br>
The RFC Editor Team<br>
<br>
_______________________________________________<br>
dhcwg mailing list -- [email protected]<br>
To unsubscribe send an email to [email protected]<br>
</div>
</div>
</body>
</html>

--_000_PH0PR11MB49660BE0EC39FDC491EFED11A951APH0PR11MB4966namp_--


--===============0241144613608853470==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZGhjd2cgbWFp
bGluZyBsaXN0IC0tIGRoY3dnQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNlbmQgYW4gZW1haWwg
dG8gZGhjd2ctbGVhdmVAaWV0Zi5vcmcK

--===============0241144613608853470==--