From fgont en si6networks.com  Mon Feb  3 20:53:57 2025
From: fgont en si6networks.com (Fernando Gont)
Date: Mon, 3 Feb 2025 20:53:57 -0300
Subject: [lacnog] Revision de IETF I-D sobre IPv6 multi-router,
 multi-prefix, y... la pequenia ; -) chance de *no* utilizar IPv6 NAT! :-)
In-Reply-To: <e3e2350d-4172-45d7-986d-632a3e009b85@si6networks.com>
References: <e3e2350d-4172-45d7-986d-632a3e009b85@si6networks.com>
Message-ID: <cd7a7154-282e-4be8-988a-73d340109598@si6networks.com>

Estimado/a(s),

Publicamos un revision de nuestro IETF I-D "Problem Statement about IPv6 
Support for Multiple Routers and Multiple Prefixes"

Link: https://datatracker.ietf.org/doc/html/draft-gont-v6ops-multi-ipv6

Si tienen comentarios, seran mas que bienvenidos. Sino, nos vemos en 
unos anios desplegando IPv6 NAT. :-***

Slds!

Regards,
Fernando
Iglesia de los Testigos de Diego Armando



-------- 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 en ietf.org
To: Fernando Gont <fgont en si6networks.com>

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