Hi all,
there's a fresh new -00 suggesting a new DHCPv4 option to carry an IPv6 nexthop for an IPv4 route (for use with RFC5549 style setups, also cf. draft-chroboczek-intarea-v4-via-v6-01). This is intended to reduce IPv4 wastage when assigning individual IPv4 addresses as /32s, by removing the need for the router(s) to have an IPv4 address. If DHCP4o6 is used, the DHCP server/relay doesn't need an IPv4 address either, allowing the end host to be the only system on a broadcast domain that has an IPv4 address. Cheers, equi ----- Forwarded message from internet-dra...@ietf.org ----- Subject: New Version Notification for draft-equinox-intarea-dhcpv4-route4via6-00.txt Date: Mon, 21 Oct 2024 09:53:56 -0700 Name: draft-equinox-intarea-dhcpv4-route4via6 Revision: 00 Title: DHCPv4 Option for IPv4 routes with IPv6 nexthops Date: 2024-10-21 Group: Individual Submission Pages: 8 URL: https://www.ietf.org/archive/id/draft-equinox-intarea-dhcpv4-route4via6-00.txt Status: https://datatracker.ietf.org/doc/draft-equinox-intarea-dhcpv4-route4via6/ HTML: https://www.ietf.org/archive/id/draft-equinox-intarea-dhcpv4-route4via6-00.html HTMLized: https://datatracker.ietf.org/doc/html/draft-equinox-intarea-dhcpv4-route4via6 Abstract: // This draft lives at https://github.com/eqvinox/dhc-route4via6 As a result of the shortage of IPv4 addresses, installations are increasingly recovering IPv4 addresses from uses where they are not strictly necessary. One such situation is in establishing next hops for IPv4 routes, replacing this use with IPv6 addresses. This document describes how to provision DHCP-configured hosts with their routes in such a situation. _______________________________________________ Int-area mailing list -- int-area@ietf.org To unsubscribe send an email to int-area-le...@ietf.org
