Date: Mon, 27 Nov 2000 12:07:49 -0500
From: "Brian Haberman" <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
| We have a concern though,
| about having multiple routers on the same network requesting multiple
| prefixes for use on it.
Yes...
I have always been of the view that it ought be prefectly safe for routers
to acquire a prefix on a net the same way that hosts do - listen for RAs
from other routers... (and like hosts, also via static config optionally).
Then, I'd only be asking for prefix allocation for a net in the case
that there were no other routers on the link.
This even fits well with divided cables, that end up with one router on
each, each of which is connected to the outside world (when they boot,
or when one of them boots - as in after a power off restart, where the
switch supposed to connect the segments doesn't recover) - then they
can each go get a prefix from their servers, and depending up how they're
set up, might each get handed the same prefix (perhaps with some glue
added, like instructions to build a tunnel, and bridge, between themselves)
or they might each be given a different prefix, as they are at least
temporarily disjoint nets, and then allow one of the prefixes to die out
after the nets reconnect.
There's lots of scope for good work here...
Unfortunately, there are (or at least were) also lots of people who
seem to strongly believe that any kind of router autoconfiguration us
something so dangerous, that it can never be permitted.
| I also have a concern about having this protocol
| look like DHCPv6 (replace addresses with prefixes).
I had the same thought, but more along the lines of merging the two...
(ie: just use DHCPv6 to fetch the prefix, the DHCP servers have
just about all the mechanism to do everything that is needed here).
kre
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
