From: "Dave Cridland" <dave(_at_)cridland(_dot_)net>
FWIW, I'm pretty sure that the vast majority of renumbering activity *is*
automated, we've simply forgotten that it's already done. We've got
autoconf, we've got DHCP, we have oodles of technology that's deployed
already.
My apologies for intruding, because I haven't been following the technology
during the past couple of years, but V6OPS did an informational RFC on
renumbering without a flag day (http://www.ietf.org/rfc/rfc4192.txt) in
2005.
I thought the document was helpful when I last looked at it
(prepublication).
There may be additional types of devices that have become more widely
deployed during the past couple of years, that would be affected by
renumbering - I'm thinking about SBCs, or Session Border Controllers, as one
example - but I think the document addresses these devices in a generic
way - the extreme form of caching addresses is sticking them in
configuration files, but this is a difference of degree, not of kind, from
the caching discussion in the document.
I'm copying the v6ops chairs, so perhaps they can clarify something...
This RFC identified a couple of opportunities:
4. Call to Action for the IETF
The more automated one can make the renumbering process, the better
for everyone. Sadly, there are several mechanisms that either have
not been automated or have not been automated consistently across
platforms.
4.1. Dynamic Updates to DNS Across Administrative Domains
4.2. Management of the Reverse Zone
Have these holes been filled in during the past couple of years?
Thanks,
Spencer
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf