Re: Node Req: Issue31: DHCPv6 text (ignore previous mails)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Node Req: Issue31: DHCPv6 text (ignore previous mails)
Comments (mostly editorial) in line...
- Ralph
At 11:12 AM 11/20/2003 +0200, john.loughney@nokia.com wrote:
Hi all,
Please ignore previous mails on this topic, here is the proposed text:
thanks,
John
> > In addition, in the absence of a router,
> > IPv6 Nodes that implement DHCP MUST attempt to use DHCP.
> >
> > ==> what does "in the absence of a router" mean? maybe this needs to be
> > made slightly more explicit to be unambiguous..
>
> Suggested text?
reword:
For those IPv6 nodes that implement DHCP, those nodes MUST use DHCP
upon the receipt of a Router Advertisement with the 'M' flag set (see
section 5.5.3 of RFC2462). In addition, in the absence of a router,
IPv6 Nodes that implement DHCP MUST attempt to use DHCP.
to:
Nodes that implement DHCP MUST use DHCP upon the receipt of a
Router Advertisement with the 'M' flag set (see section 5.5.3 of
RFC2462). In addition, in the absence of a router,
How about replacing "in the absence of a router" with "if the node does not
receive any Router Advertisements"? Please ignore my suggestion if I'm
leading us down a previously explored rathole.
IPv6 Nodes that implement DHCP MUST attempt to use DHCP. In this
Is the capitalization of "Nodes" consistent with the rest of the doc
(seems to be, based on the text snippets included here?)?
context, 'use DHCP' means trying to obtain both address(es) and
other configuration information through DHCP.
As was suggested elsewhere, substituting DHCPv6 for DHCP throughout
wouldn't hurt (but certainly isn't critical).
> > For those IPv6 Nodes (acting as hosts) that implement DHCP, those
> > nodes MUST use DHCP upon the receipt of a Router Advertisement with
> > the 'O' flag set (see section 5.5.3 of RFC2462). In addition, in the
> > absence of a router, hosts that implement DHCP MUST attempt to use
> > DHCP.
> >
> > ==> attempt to use DHCP _for what_ ? Getting stateful information, of
> > course, not the addresses?
>
> Suggested text?
reword:
For those IPv6 Nodes (acting as hosts) that implement DHCP, those
nodes MUST use DHCP upon the receipt of a Router Advertisement with
the 'O' flag set (see section 5.5.3 of RFC2462). In addition, in the
absence of a router, hosts that implement DHCP MUST attempt to use
DHCP. For IPv6 Nodes that do not implement DHCP, the 'O' flag of a
Router Advertisement can be ignored. Furthermore, in the absence of
a router, these types of node are not required to initiate DHCP.
s/types of node/such Nodes/ (for clarity and consistency)?
to:
IPv6 Nodes (acting as hosts) that implement DHCP, MUST use DHCP upon
Is there a reason to differentiate between nodes acting as hosts here, but
not in the paragraph describing the behavior in response to the 'M' bit?
I'd suggest, in fact, that only hosts want to use DHCPv6 for address
assignment, while both hosts and routers want to use DHCPv6 for other
configuration information. Again, please ignore my suggestion if the issue
has already been explored.
the receipt of a Router Advertisement with the 'O' flag set (see
section 5.5.3 of RFC2462). In addition, in the
absence of a router, hosts that implement DHCP MUST attempt to use
My comment above about "in the absence of a router" applies here, too.
DHCP. In this context, 'use DHCP' means trying to obtain only other
configuration information through DHCP, not address(es).
IPv6 Nodes that do not implement DHCP can ignore the 'O' flag
of a Router Advertisement.
Is there a specific reason that a similar sentence does not appear in the
text about the 'M' bit?
Furthermore, in the absence of
a router, these types of node are not required to initiate DHCP.
s/types of node/such Nodes/ (for clarity and consistency)?
(these are not only editorial issues IMHO, especially the latter one,
if someone is envisioning that in absence of a router, DHCP should try
to get an address as well, from the context of other config
information)
I'm afraid I don't understand the parenthetical comment...
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.