On Fri, 21 Dec 2007, Stephane Bortzmeyer wrote:
Among the many dummy things he mentions, this one is probably the best
:-) May be someone should tell him there are name resolution services
(and they existed even before the DNS)?
But someone has to configure those things. That most likely will mean
humans having more difficulty typing longer addresses accurately.
Sometimes the resolution service is not working. Trouble shooting
generally means digging down to lower levels, etc.
Perhaps in some future time, we'll have applications which just do this
stuff more effectively. In the interim, I can only be grateful for my USB
memory stick as an improvement over postits as a mechanism for carrying IP
addresses around.
Given the sorry state of DHCP / DNS integration (I work with and around
common products used on Windows and Linux) ... I find a lot of bogus data
accrues over time ... I find automatic updates which can't cope with
laptops which move from wired to wireless. I've discovered that DHCP (as
deployed at least) can't provide a name suffix search list, etc.
As a network operations groupie, I can understand why a network operator
might not feel happy about having to embrace IPv6. They deal with what
curretly is, not what might be.
So rather that attacking folks out where the rubber meets the road, we
need to listen so we can understand their root problems and then we need
to get integrated solutions in place.
Having one or more carefully planned IPv6 network operations working
sessions over the next year and using the IETF meetings as the focal point
is a good way to gather experience, clarify requirements for
infrastructure tools, etc.
Disrupting a meeting funded for a different purpose will/would be an
offensive colossal waste of resources.
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf