From fgont at si6networks.com Mon Feb 3 04:26:59 2025 From: fgont at si6networks.com (Fernando Gont) Date: Mon, 3 Feb 2025 04:26:59 -0300 Subject: [ipv6hackers] Fwd: Revision of IETF I-D on IPv6 multi-router, multi-prefix, and... hopefully not NATs! :-) In-Reply-To: References: Message-ID: <76383b66-2791-4809-a0d5-e56006f9ec1d@si6networks.com> Hello, all! Long time no hear! Hope you are all doing okay! We have posted this minor rev of our I-D on the problem statement about IPv6 support for multiple-prefixes and multiple-routers). The revised I-D is here: https://datatracker.ietf.org/doc/html/draft-gont-v6ops-multi-ipv6 We plan to post a revision in two weeks or so (mostly addressing the feedback we got for the -00 version). If you have any comments on the I-D, or thoughts on the topic, please do let us know! -- I'll make my best for your feedback to be addressed in the next rev. Thanks! Regards, Fernando -------- Forwarded Message -------- Subject: New Version Notification for draft-gont-v6ops-multi-ipv6-01.txt Date: Sun, 02 Feb 2025 18:18:48 -0800 From: internet-drafts at ietf.org To: Fernando Gont A new version of Internet-Draft draft-gont-v6ops-multi-ipv6-01.txt has been successfully submitted by Fernando Gont and posted to the IETF repository. Name: draft-gont-v6ops-multi-ipv6 Revision: 01 Title: Problem Statement about IPv6 Support for Multiple Routers and Multiple Prefixes Date: 2025-02-02 Group: Individual Submission Pages: 10 URL: https://www.ietf.org/archive/id/draft-gont-v6ops-multi-ipv6-01.txt Status: https://datatracker.ietf.org/doc/draft-gont-v6ops-multi-ipv6/ HTMLized: https://datatracker.ietf.org/doc/html/draft-gont-v6ops-multi-ipv6 Diff: https://author-tools.ietf.org/iddiff?url2=draft-gont-v6ops-multi-ipv6-01 Abstract: This document discusses current limitations in IPv6 Stateless Address Auto-cofiguration (SLAAC) that prevent support for common multi- router and multi-interface scenarios. It provides discussion on the challenges that these scenarios represent, and why a solution in this space is warranted. Finally, it specifies a number of common scenarios that any solution in this space should be able to address. The IETF Secretariat From fgont at si6networks.com Mon Feb 10 17:53:34 2025 From: fgont at si6networks.com (Fernando Gont) Date: Mon, 10 Feb 2025 17:53:34 -0300 Subject: [ipv6hackers] Fwd: Generation/Selection of IPv6 addresses by DHCPv6 servers (Fwd: New Version Notification for draft-gont-dhcwg-dhcpv6-iids-00.txt) In-Reply-To: <4af5cc1b-5c95-4727-9558-9fbcf1964af1@si6networks.com> References: <4af5cc1b-5c95-4727-9558-9fbcf1964af1@si6networks.com> Message-ID: <8d3577e4-ff2a-4325-9721-b1afb562a46f@si6networks.com> Hi, all, Heads up. This aligns with other work a number of us have been doing in this area, such as RFC7721, RFC7707, and RFC9416. Feedback welcome! Thanks, Fernando -------- Forwarded Message -------- Subject: Generation/Selection of IPv6 addresses by DHCPv6 servers (Fwd: New Version Notification for draft-gont-dhcwg-dhcpv6-iids-00.txt) Date: Mon, 10 Feb 2025 17:51:25 -0300 From: Fernando Gont Organization: SI6 Networks To: dhcwg at ietf.org Hi, all, I recently happened to run into draft-ietf-dhc-rfc8415bis-07, and was glad to find that it does provide some advice regarding the generation of IPv6 addresses by DHCP6 servers. (Coincidentally or not, this is aligns with the recent work in RFC9416 regarding transient numeric identifiers). In that regard, I've posted this I-D (draft-gont-dhcwg-dhcpv6-iids): * URL: https://www.ietf.org/archive/id/draft-gont-dhcwg-dhcpv6-iids-00.txt * HTMLized: https://datatracker.ietf.org/doc/html/draft-gont-dhcwg-dhcpv6-iids with the goal of producing a Standards Track specification of the algorithm in RFC7943, such that it can be better referenced (or recommended, as noted in RFC9416) in future revisions of the DHCPv6 spec (no, I'm not meaning the current draft-ietf-dhc-rfc8415bis effort, but future ones). Feedback will be welcome! Thanks, Fernando -------- Forwarded Message -------- Subject: New Version Notification for draft-gont-dhcwg-dhcpv6-iids-00.txt Date: Mon, 10 Feb 2025 12:40:54 -0800 From: internet-drafts at ietf.org To: Fernando Gont A new version of Internet-Draft draft-gont-dhcwg-dhcpv6-iids-00.txt has been successfully submitted by Fernando Gont and posted to the IETF repository. Name: draft-gont-dhcwg-dhcpv6-iids Revision: 00 Title: A Method for Generating Semantically Opaque IPv6 Interface Identifiers (IIDs) with Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Date: 2025-02-10 Group: Individual Submission Pages: 11 URL: https://www.ietf.org/archive/id/draft-gont-dhcwg-dhcpv6-iids-00.txt Status: https://datatracker.ietf.org/doc/draft-gont-dhcwg-dhcpv6-iids/ HTMLized: https://datatracker.ietf.org/doc/html/draft-gont-dhcwg-dhcpv6-iids Abstract: This document describes a method for selecting IPv6 Interface Identifiers that can be employed by Dynamic Host Configuration Protocol for IPv6 (DHCPv6) servers when leasing non-temporary IPv6 addresses to DHCPv6 clients. This method is a DHCPv6 server-side algorithm that does not require any updates to the existing DHCPv6 specifications. The aforementioned method results in stable addresses within each subnet, even in the presence of multiple DHCPv6 servers or DHCPv6 server reinstallments. It is a DHCPv6 variant of the method specified in RFC 7217 for IPv6 Stateless Address Autoconfiguration (SLAAC). The IETF Secretariat