Estimad*s,
Comenzo el WGLC (Working Group Last Call) de uno de nuestros drafts de
IETF.
Este doc apunta a mejorar la situacion actual en esta materia. creo que
es un paso enorme en la direccion correcta (por algun lugar se empieza).
* El llamado esta aqui:
https://mailarchive.ietf.org/arch/msg/ipv6/hdw9xtL-GUGRCrNsDrCauM9gTs4/
* El doc aqui: https://datatracker.ietf.org/doc/draft-ietf-6man-slaac-renum/
* Y una buena cancion sobre el Diego aqui:
https://www.youtube.com/watch?v=o9rILjy1WK4&list=RDo9rILjy1WK4. (la
letra esta aun mejor que la musica)
Dime si amas al Diego, y te dire quien eres....
Fer
-------- Forwarded Message --------
Subject: WG Last Call: draft-ietf-6man-slaac-renum-10 (Ends 2025-09-26)
Resent-Date: Fri, 12 Sep 2025 08:14:41 -0700 (PDT)
Resent-From: [email protected]
Resent-To: [email protected], [email protected], [email protected],
[email protected]
Date: Fri, 12 Sep 2025 08:14:41 -0700
From: Bob Hinden via Datatracker <[email protected]>
Reply-To: Bob Hinden <[email protected]>
To: [email protected], [email protected],
[email protected]
Subject: WG Last Call: draft-ietf-6man-slaac-renum-10 (Ends 2025-09-26)
This message starts a 2-week WG Last Call for this document.
Abstract:
In scenarios where network configuration information becomes invalid
without explicit notification to the local network, local hosts may
end up employing stale information for an unacceptably long period of
time, thus resulting in interoperability problems. This document
improves the reaction of IPv6 Stateless Address Autoconfiguration to
such configuration changes. It formally updates RFC 4191, RFC 4861,
RFC 4862, and RFC 8106.
File can be retrieved from:
https://datatracker.ietf.org/doc/draft-ietf-6man-slaac-renum/
Please review and indicate your support or objection to proceed with the
publication of this document by replying to this email keeping [email protected]
in copy. Objections should be motivated and suggestions to resolve them are
highly appreciated.
Authors, and WG participants in general, are reminded again of the
Intellectual Property Rights (IPR) disclosure obligations described in
BCP 79
[1]. Appropriate IPR disclosures required for full conformance with the
provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of
any. Sanctions available for application to violators of IETF IPR Policy can
be found at [3].
Thank you.
[1] https://datatracker.ietf.org/doc/bcp78/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/
--
Fernando Gont
SI6 Networks
e-mail: [email protected]
PGP Fingerprint: F242 FF0E A804 AF81 EB10 2F07 7CA1 321D 663B B494
_______________________________________________
Lista mailing list
[email protected]
http://mailmancabase.interdotnet.com.ar/mailman/listinfo/lista
