Margaret Wasserman wrote:
>
> At 02:25 PM 10/10/02, Robert Elz wrote:
>
>> So would I. The change I would make is to delete all references
>> of subnet-local from the addr-arch doc, and simply leave those values
>> as "to be defined" and then define them in the scoping-arch doc.
>
>
> This seems reasonable to me.
>
> It moves this issue out of the IPv6 addr arch, allowing that document
> to move ahead, and let's us work out the details in the scoped addr
> arch and/or the multi-link subnets doc.
>
> Good idea, Robert.
>
> What do other folks think?
I would go a step further. Since almost no one has implemented the
routing/forwarding of scoped addresses (multicast & unicast site
locals), I recommend:
1. Move all discussion of multicast scopes out of the addr-arch
and into the scoped addr-arch doc
2. Move all text on site-local unicasts out of the addr-arch
doc and into the scoped addr-arch doc
3. Add explicit text to the scoped addr-arch doc to define
how/when/where these scopes should be used
This would allow the addr-arch doc to progress to DS without being
hung up on text involving scoped addresses but still describing the
pieces that we know work (e.g. global and link-local). It would also
make a clean delineation between global and scoped addresses.
The scoped addr-arch doc can then be the home for future work on
scoped addresses.
My reasoning is based on actually having implemented scoped routing
and forwarding. It is not trivial or for the weak of heart.
Brian
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
