nice idea, but I'm fairly convinced that it's impractical. there are
just too many interfaces, many of them nonstandard and application
specific, that need to know about IP addresses.
maybe we could come up with a 90% solution, but that 10% is still a bear.
I'm back to thinking that we have to find some way to provide PI space
to everyone. and I'm not convinced that it doesn't scale to give
customers PI space and have PI addresses in IP packets, even though I'm
fairly convinced that trying to do routing in terms of customer PI space
doesn't scale.
sound to me that what we need is a new way to
- configure hosts
- configure routers
- configure ACL on routers/firewall/wherever
- services (http, mail ++++)
- dns (a bit special, more about it further down)
where it is possible to do the change ONE place and get all other
fields like the same changed at the same place in all of the above
place and other I have forgotten... and at the same place have the
changes be done transparent or with as short outages as possible,
less than 1minut I would say. In other word.
We need to get totaly ride of the manual configuration that has to
be done when changing IP addresses, changing domain names
etc. NA/RA build into IPv6 has some of this but it just make it possible
to configure IP on the host...
DNS is one place this could be done, but DNS isn't trustworthy enough
yet, and we also have the NAT/RFC1918 ip addresses that make it
harder.
But without such a automatic system we are forever bound to IP
addresses, or hostnames wherever we go.
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf