>>>>> On Mon, 31 Oct 2005 14:17:17 -0500,
>>>>> Ralph Droms <[EMAIL PROTECTED]> said:
> Suppose the nodes on a link are to be restricted to the use of addresses
> assigned through DHCP, and precluded from the use of autonomous address-
> configuration.
> It seems there are two ways to accomplish this goal:
> 1) Don't include any prefixes in router advertisements
> 2) Include the prefixes assigned to the link in router advertisements,
> with the A (autonomous address-configuration) flag set to FALSE
> There may be a subtle problem with (2): the text in RFC 2462 does not
> include RFC 2119 words absolutely precluding the use of autonomous
> address-configuration:
> a) If the Autonomous flag is not set, silently ignore the
> Prefix Information
> option.
> Note the lack of "MUST" before "silently ignore".
I cannot speak for the authors/designers, but my interpretation is
that there is an 'imaginary' MUST which covers the entire procedure
from 5.5.3 (a) through (e).
If this is the intent, and the original text was not very clear for
many others, we might add to 2462bis something like:
5.5.3 Router Advertisement Processing
A host configured to create global addresses using Router
Advertisements MUST perform the followings for each
Prefix-Information option in the Router Advertisement:
BTW: the following part of Section 5.5 may have some relevant point:
Creation of global and site-local addresses and configuration of
other parameters as described in this section SHOULD be locally
configurable. However, the processing described below MUST be enabled
by default.
With the deprecation of site-local addresses and ignoring the "other
parameters" part, it reads:
"Creation of global addresses SHOULD be locally configurable."
I'm not 100% sure what "locally configurable" means, but I think this
generally controls whether the node performs entire 5.5.3 or doesn't
perform any part of 5.5.3 at all, rather than allowing finest-grained
flexibility, e.g., whether or not follow some specific part of the
rules such as 5.5.3 a. If there is ambiguity here also, we may have
to fix it 2462bis.
> Is there a reason to prefer one of these two ways of precluding the use
> of autonomous address-configuration? Is there a problem with using
> technique (1)?
One possible issue is how the hosts know on-link prefixes then. They
can still rely on routers and (optionally) redirects, but it's not
really efficient.
JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba Corp.
[EMAIL PROTECTED]
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
