Matt,
| I imagine that your routers have no difficulty in carrying a separate route
| for each of your customers, so there's no need for you to get involved in
| assigning them address prefixes. As for tracking the possible changes in
| their prefixes, you (and your customers) will have to make that effort part of
| the cost of your service. Whether it's easy or hard is still an open
| question, partly hining (IMHO) on DNS choices to be made in the near future.
In the near future will routers, which currently carry almost all of the route
policying
and most of the traffic filtering in large distributed networks, use v6 "DNSSEC" to get
the IPv6 address information they need to apply against arriving packets (rather than
manually coding IPv6 addresses into the routers configuration)? If so, would there be
any
examples of vendors that are participating in this effort? One cannot look to
vaporware
to build a network.
It seems that the new Internet is more DNS and less everything else (except if you are
an
ISP). Maybe it would be better to use DNS name to route packets instead of
fixed-length
64-bit addresses (just kidding of course).
AI
P.S. I wonder if there is an illustration of the IPng "vision". A picture is better
than
a thousand words.
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
