> In message <[EMAIL PROTECTED]>, rbrabson@us.
> ib
> m.com writes:
>
>
> >So, to make SL work, we need changes to the DNS name server, changes
> >to the resolver, routers to advertise the scope zones, hosts to
> >learn the scope zones from routers and include them on DDNS
> >registrations and use them in making routing decisions, updates to
> >routing protocols, IANA needs to manage a new zone scope naming
> >space, and who knows what else.
> >
> >Wouldn't it make sense to hold off on SL until we at least have
> >some proposals on the table which describe the changes necessary to
> >make SL work, at which time we could have a discussion on the
> >technical merits of the proposal(s)? Until that time, though, the
> >SL unicast address space should either be reserved or moved to
> >experimental.
> >
>
> I think this is the key point. Regardless of the possible benefits of
> site-local addresses -- and I'm willing to withhold judgment on that
> point -- we don't know in detail how to make them work. At a minimum,
> we need changes in routing and the DNS. We may need new global
> namespaces as well, with all that implies for co-ordination and
> administrative overhead.
Well we already have a global managed namespace. The
scopename would be just be a name within the namespace
already delegated to you.
host1.example.com. SA <SL-IPV6-address> site1.example.com.
host1.example.com. SA <SL-IPV6-address> site2.example.com.
host1.example.com. SA <global-IPV6-address> .
host2.example.com. SA <SL-IPV6-address> site2.example.com.
host2.example.com. SA <global-IPV6-address> .
host3.example.com. SA <SL-IPV6-address> site1.example.com.
host3.example.com. SA <global-IPV6-address> .
Here host2.example.com and host3.example.com would have to
communicate using global addresses while host1.example.com
and host2.example.com could choose to use there site2.example.com
SL address and host1.example.com and host3.example.com could
choose to use there site1.example.com SL address.
Mark
> --Steve Bellovin, http://www.research.att.com/~smb (me)
> http://www.wilyhacker.com ("Firewalls" book)
>
>
> --------------------------------------------------------------------
> 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]
> --------------------------------------------------------------------
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED]
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
