> The discussions always ended up on the same kind of conclusion: in
> theory it is a fine idea, but we would have to change existing
> implementation,

Assuming implementations have to be changed, then this means that it'll take
a few years for the functionality to get out there, but otherwise this is
not a good reason not to do it per se.

But speaking of existing implementations, what would happen if an existing
router advertised to an existing host that one of the host's prefixes
contained a site ID (that is, a site-local with a non-zero 38-bit number).
Presumably the host would accept it?

And, if you were running two-faced DNS, then when the host did a DNS lookup
on another host in the same site (apologies to those of you who hate
two-faced DNS, but lots of folks use it so this would be valuable for at
least some of the community), it would get back a site-ID-based address and
all would be fine, yes?  Same as with site-IDs.

For those sites that don't want to run two-faced DNS but do want site-IDs,
they'd have to wait a few years.  (As it stands today with existing
implementaitons if you don'trun two-faced DNS you can't use site-locals
anyway.)

> and besides it is not easy to allocate unique numbers.
> There are basically four ways to allocate random numbers, and none of
> them is particularly attractive:
>

Agreed that it isn't easy to allocate unique numbers.  Is that a good enough
reason not to pursue this?  I mean, lets say we design how to do site-IDs
and get buy-in from the gang.  Then we go off to ICANN or whoever, and they
screw it up.  Ok then it was a failure and too bad.  (Or, we go off and
create a renegade registry...that'd be interesting  :-)  (Or, do the
renegade registry first and force ICANN's hand...)

Either way, the exercise would be a learning experience for the IPv6 group,
and the time wasted would mainly be just the poor disillusioned souls that
worked on the draft...

PF





--------------------------------------------------------------------
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]
--------------------------------------------------------------------

Reply via email to