Dave Thaler wrote:
>>From: Brian Haberman [mailto:[EMAIL PROTECTED]]
>>
>>>>The more I think about it, the more I realize that "automagically"
>>>>creating the subnet-local scope zone id isn't going to work.
>>>>Especially with multiple prefixes per interface.
>>>
>
> Why not? Can you elaborate?
> Shouldn't it always be true that if any two interfaces have the
> same (non-link-local) subnet prefix, then their subnet-local
> zone id MUST be the same?
What happens to the zone ids when:
1. Interface 1 has prefix1 and prefix2
2. Interface 2 has prefix1 and prefix3
3. Interface 3 has prefix2 and prefix4
>
>
>>>So, this would be consistent with the suggestion that we
>>>change the Addr Arch document to list subnet-local and larger
>>>scopes as administratively defined (instead of just admin-local
>>>and higher)?
>>
>>Yes. Given the issues with magically setting the subnet-local
>>zone id when multiple prefixes are enabled on an interface I
>>would agree with that change.
>
>
> I would disagree with that change.
>
>
>>>Another possibility is that we could default to a non-multi-link
>>>subnet case and declare the default to be subnet-local scope
>>>== link-local scope.
>>
>>We may need this as well. Typically, the default behavior for
>>any less than global scope zone id is that all interfaces are
>>in the same zone. I don't think we want that behavior with
>>subnet-local, it should default to being equivalent to link-local.
>
>
> I agree. This also is what we implemented.
>
>
>>>>>In other words, I think that routers should default to the
>>>>>single-link subnet case, unless mutli-link subnetting has been
>>>>>explicitly configured.
>>>>
>
> I agree with one important clarification.
> "Explicitly configured" != "administratively configured".
Totally agree.
>
> The zero-config counter argument is a box that is labeled as
> having its default configuration be that interfaces are on the
> same subnet different but different links (e.g. guaranteed
> to be different because they're different media, like an
> 802.11 access point with a wired Ethernet link). Here
> the explicitly configuration was done by the factory, not
> by the admin.
Yep.
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]
--------------------------------------------------------------------
