Your summary looks right to me... - Ralph
On Tue, 2005-07-26 at 23:22 +0900, JINMEI Tatuya / 神明達哉 wrote: > Hello, > > I've (re)read the whole big thread on the recent discussion about the > RA M/O flags starting at around end of May. We even had a meta-level > discussion about whether those flags might better be removed > altogether (again!), but it looks we agreed that we need at least some > kind of indication in RA. > > While opinions on the details so varied, we seem to have agreed that > we need to fix the requirements for those flags (or something > similar/replacement in RA) first. > > Based on a nice initial attempt by Ralph... > > http://www1.ietf.org/mail-archive/web/ipv6/current/msg05141.html > > ...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) > > Am I missing anything? Note that I'm not saying we need all of them; > I'm currently trying to list all major points raised in the past > discussion. Some of those may turn out to be a non-requirement. > > Once we can fix the list, we'll then start the main discussion of > which is really necessary and how to do that. (And I'd like to not > start that type of discussion at the moment so that we can move > forward step-by-step, avoiding further confusion or divergence). > > JINMEI, Tatuya > Communication Platform Lab. > Corporate R&D Center, Toshiba Corp. > [EMAIL PROTECTED] > > _______________________________________________ > dhcwg mailing list > [email protected] > https://www1.ietf.org/mailman/listinfo/dhcwg -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
