One more "easy" point:
>>>>> On Mon, 16 Aug 2004 18:43:04 +0100,
>>>>> "Elwyn Davies" <[EMAIL PROTECTED]> said:
>> > As mentioned elsewhere the para on the use of the M and O
>> flags in s.4
>> > should reiterate the requirement that hosts have stateless
>> autoconfiguration
>> > enabled by default when thay come out of the box to ensure full
>> > 'plug-and-play' behaviour.
>>
>> (I'm not sure what "As mentioned elsewhere" means, but in any event)
>> I personally do not see the need for this...IMO, this would rather be
>> a matter of the node requirement document (and, in my understanding,
>> the node-req document is already pretty clear on this).
> Elsewhere refers to S 5.5 which says (referring to creation of Global
> Addresses from info in RAs '...the processing described below MUST be
> enabled by default'. I think this is sufficiently important (it goes to the
> heart of plug and play operation) that it is worth a sentence in the
> Protocol Overview - the words on M and O in previous versions didn't allow
> any ambiguity. How about adding a sentence after the para at the top of
> page 10 (ending '...in a separate document.'):
> However a host uses the M and O flags, and local configuration to control
> autoconfiguration, the default setting will result in received Router
> Advertisements being processed.
Hmm, I still don't see the strong need for this, but it is a minor
change that may help, so I don't mind to add this with a small
modification: "received Router Advertisements being processed" is
ambiguous. I'd reword this to:
the default setting will result in received Router Advertisements
being processed for stateless address autoconfiguration.
JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba Corp.
[EMAIL PROTECTED]
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
