At 6:07 PM -0400 10/2/02, Rob Austein wrote:
>The key phrase in your explanation is "the admin assigns". The
>addr-arch doc says "admin-local scope is the smallest scope that must
>be administratively configured". So which is it?
You omitted the full description:
admin-local scope is the smallest scope that must be
administratively configured, i.e., not automatically
derived from physical connectivity or other, non-
multicast-related configuration.
Subnet-local scope is an example of automatic derivation from "other,
non-multicast-related configuration".
Specifically, you don't directly configure a router to know which
subnet-scope boundaries pass through it (as you must do with larger
scopes). Rather, you (typically, manually) configure the router
with subnet info -- including, perhaps, enabling or disabling
multilink-subnet behavior -- as required for unicast routing, and
then you automatically derive subnet-scope boundary information from
that "other, non-multicast-related configuration".
Or saying it more concisely: you don't administratively configure
subnet scope; you adminstratively configure subnet info for unicast
purposes, and then automatically derive subnet scope from that.
Steve
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
