I share your concern about mandating the implementation of a possibly
extraneous state variable. Perhaps replacing your suggested text:
On receipt of a valid Router Advertisement (as defined in
[DISCOVERY]), a host copies the value of the advertisement's M bit
into ManagedFlag, which saves the mostly recently received value of
the M bit.
with:
The details of how a host uses the M bit from a valid Router
Advertisement it receives will be described in a separate document.
would indicate that the use of the M bit is left to the implementation but
is not prescribed here?
- Ralph
At 03:17 PM 5/18/2004 -0700, Christian Huitema wrote:
> I'm certainly not implying any API.
> Why do you think the text with the forward reference to "a separate
> document"
> implies any API?
The forward reference is asking the implementers to manage an extraneous
state variable. As far as ND is concerned, the host can be entirely
conformant and interoperate fine with others without that state variable.
So, the only reason for the state variable is to facilitate the
implementation of something else than ND, which will use the value of the
state variable. For that you need some form of API.
-- Christian Huitema
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
