[dhcwg] IPv4 address use for 4o6RA [was: Re: New Version Notification for draft-porfiri-dhc-dhcpv4-over-dhcpv6-ra-02.tx t]

Hi all,

besides removing the topology discovery specific part and moving the RAN use case into the appendix, we also added a short section on deployment consideration to address the question of IPv4 address usage with the following text:

" As the client is not aware of the 4o6RA, the network deployment needs
           to ensure that all DHCPv4 broad- and unicast messages from the client
           are routed over the 4o6RA.  This can e.g. be achieved by placing the
           4o6RA in a central position that can observe all traffic from the
           clients or use of address translation with the 4o6RA address for
           unicast messages."

In summary, we believe we can leave this decision to the deployment and do not need to specify anything more strictly here. Please comment and let us know if that approach is reasonable!

Thanks,
Mirja



On 12.09.24, 11:20, "Claudio Porfiri" <[email protected] <mailto:[email protected]>> wrote:




We updated the previous draft by implementing the comments from the discussion from IETF120 as well as from the mail thread.
Focus has been moved from being based on the RAN use case to a generic network problem, thus giving a general solution.




A new version of Internet-Draft draft-porfiri-dhc-dhcpv4-over-dhcpv6-ra-02.txt
has been successfully submitted by Mirja Kühlewind and posted to the
IETF repository.


Name: draft-porfiri-dhc-dhcpv4-over-dhcpv6-ra
Revision: 02
Title: DHCPv4 over DHCPv6 with Relay Agent Support
Date: 2024-09-12
Group: Individual Submission
Pages: 10
URL: https://www.ietf.org/archive/id/draft-porfiri-dhc-dhcpv4-over-dhcpv6-ra-02.txt <https://www.ietf.org/archive/id/draft-porfiri-dhc-dhcpv4-over-dhcpv6-ra-02.txt>
Status: https://datatracker.ietf.org/doc/draft-porfiri-dhc-dhcpv4-over-dhcpv6-ra/ <https://datatracker.ietf.org/doc/draft-porfiri-dhc-dhcpv4-over-dhcpv6-ra/>
HTML: https://www.ietf.org/archive/id/draft-porfiri-dhc-dhcpv4-over-dhcpv6-ra-02.html <https://www.ietf.org/archive/id/draft-porfiri-dhc-dhcpv4-over-dhcpv6-ra-02.html>
HTMLized: https://datatracker.ietf.org/doc/html/draft-porfiri-dhc-dhcpv4-over-dhcpv6-ra <https://datatracker.ietf.org/doc/html/draft-porfiri-dhc-dhcpv4-over-dhcpv6-ra>
Diff: https://author-tools.ietf.org/iddiff?url2=draft-porfiri-dhc-dhcpv4-over-dhcpv6-ra-02 <https://author-tools.ietf.org/iddiff?url2=draft-porfiri-dhc-dhcpv4-over-dhcpv6-ra-02>


Abstract:


This document describes a mechanism for networks with legacy
IPv4-only clients to use services provided by DHCPv6 using DHCPv4-
over-DHCPv6 (DHCP 4o6) in a Relay Agent. RFC7341 specifies use of
DHCPv4-over-DHCPv6 in the client only. This document specifies a
RFC7341-based approach that allows DHCP 4o6 to be deployed as a Relay
Agent (4o6RA) that implements the 4o6 DHCP en- and decapsulation if
this is not possible at the client.






The IETF Secretariat







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