On 26-jul-2005, at 16:22, JINMEI Tatuya / 神明達哉 wrote:
...I'd summarize the requirements raised in the thread as follows:
1) Ability to indicate to a host "DHCP is not available on this link",
with the expectation that the host won't send any DHCP messages
1') Some people (one person?) also wanted the ability to indicate
to a host "a particular type of DHCPv6 (i.e., ICB or HCB) is not
available on this link" (This is probably a combination like
M=0&&O=1 would currently indicate)
2) Ability for a host to get all desired and available DHCP
configuration with a single DHCP message exchange
- if a host wants HCB, it sends an HCB request (Solicit) and
receives
HCB and/or ICB replies
- if a host wants ICB, it sends an ICB request (Information-
request)
and receives ICB replies
3) Ability to do DHCP without having to configure routers
(e.g., by ignoring RA with M=0 and/or O=0 and invoking HCB and/or
ICB anyway)
Can't remember HCB and ICB stand for right now, so maybe I'm missing
some of the finer points...
Anyway, I believe it's important that clients know that they should
ask for addresses + other info over DHCPv6, or other information
only. (I'll be happy to explain why at length in private email or in
person next week if anyone cares.)
Someone implmenting or deploying DHCPv6 would probably want to know
whether they should have stateful or stateless servers or both, and
stateful or stateless clients or both.
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
