Re: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6-ra-mo-flags-01.txt
Thomas Narten <narten@us.ibm.com> Wed, 18 May 2005 16:31 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DYRRn-0002uN-6X; Wed, 18 May 2005 12:31:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DYRRk-0002to-O2; Wed, 18 May 2005 12:31:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09520; Wed, 18 May 2005 12:30:55 -0400 (EDT)
Received: from e5.ny.us.ibm.com ([32.97.182.145]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DYRig-000091-He; Wed, 18 May 2005 12:48:32 -0400
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e5.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id j4IGUjMk031569; Wed, 18 May 2005 12:30:45 -0400
Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay02.pok.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j4IGUjPE154700; Wed, 18 May 2005 12:30:45 -0400
Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.11/8.13.3) with ESMTP id j4IGUdUB006546; Wed, 18 May 2005 12:30:39 -0400
Received: from cichlid.raleigh.ibm.com (sig-9-48-34-201.mts.ibm.com [9.48.34.201]) by d01av03.pok.ibm.com (8.12.11/8.12.11) with ESMTP id j4IGUd0e006523; Wed, 18 May 2005 12:30:39 -0400
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.13.1/8.12.5) with ESMTP id j4IGTKmt005705; Wed, 18 May 2005 12:29:20 -0400
Message-Id: <200505181629.j4IGTKmt005705@cichlid.raleigh.ibm.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Subject: Re: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6-ra-mo-flags-01.txt
In-Reply-To: Message from "Bernie Volz \(volz\)" <volz@cisco.com> of "Mon, 16 May 2005 09:56:26 EDT." <8E296595B6471A4689555D5D725EBB212B33DE@xmb-rtp-20a.amer.cisco.com>
Date: Wed, 18 May 2005 12:29:20 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: dhcwg@ietf.org, "Ralph Droms (rdroms)" <rdroms@cisco.com>, IPv6 WG <ipv6@ietf.org>, Pekka Savola <pekkas@netcore.fi>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
Let me just start off by saying I pretty much agree completely with what Bernie just said. I've also reviewed this document, and I am really wondering what this document is trying to achieve. It seems to me that its added a lot of text (that IMO is not really needed). In particular, I don't think either Section 6 or 7 are necessary or appropriate. There are really only two behaviors a client should be doing. If a client doesn't implement DHC, well, then it obviously shouldn't/can't invoke DHC. End of story. If it does implement DHC, well, it should use it. Moreover, it shold never really be a "client" choice whether to invoke use DHC or not. If the sys admin has stuff available via DHC, the client should (in the SHOULD sense) be getting it and using it. Why on earth would we want to disable that via a configuration knob? Indeed, when I look at Section 2, "Background", I find that the wording that it quotes from RFC 2461 really does say pretty much what should be said. That is, these bits are "hints" that the local sys admin has a DHC server that is giving out addresses and/or other configuration information. Seems to me, if the local access network is giving out config information, clients SHOULD try and get it, because if they don't, they will presumably operate at some sort of reduced level of functionality -- after all, if a sys admin set up a DHC server, there must be a reason for this (e.g., to provide DNS recursive name server service, addresses not available via stateless addrconf, etc.). So, these bits should just provide clients with a stronger indication that they should be using DHC to get the information that is available. If the original 2461 text is really deemed insufficient, how about something like: o M : 1-bit "Managed address configuration" flag. When set, it indicates that addresses are available via Dynamic Host Configuration Protocol [DHCPv6], including addresses that were not configured via stateless address autoconfiguration. Clients SHOULD use DHC to obtain addresses (and associated configuration information) as described in [ADDRCONF]. Note that when the M bit is set, the setting of the O bit is irrelevant, since the DHC server will return "other" configuration information together with addresses. o O : 1-bit "Other configuration" flag. When set, it indicates that [DHCPv6lite] is available for autoconfiguration of other (non-address) information. Examples of such information are DNS-related information or information on other servers within the network. When set, - If the M bit is also set, clients SHOULD use DHC to obtain addresses (and associated configuration information) as described above. - If the M bit is not set, clients SHOULD use DHC as described in RFC 3736. Is more than something like the above _really_ needed? If so, why? Thomas _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] [Fwd: IPv6 WG Last Call:draft-ietf-ipv6-r… Ralph Droms
- [dhcwg] [Fwd: Re: IPv6 WG Last Call:draft-ietf-ip… Ralph Droms
- [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6-ra-… Ralph Droms
- [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6-ra-… Pekka Savola
- [dhcwg] [Resolving Issues]IPv6 WG Last Call:draft… Soohong Daniel Park@SAMSUNG.COM
- [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6-ra-… JINMEI Tatuya / 神明達哉
- RE: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6… Bernie Volz (volz)
- RE: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6… Bernie Volz (volz)
- Re: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6… Stig Venaas
- RE: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6… Bernie Volz (volz)
- RE: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6… Pekka Savola
- RE: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6… Bernie Volz (volz)
- RE: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6… Bernie Volz (volz)
- RE: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6… Bernie Volz (volz)
- Re: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6… JINMEI Tatuya / 神明達哉
- Re: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6… Thomas Narten
- Re: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6… Bob Hinden
- Re: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6… JINMEI Tatuya / 神明達哉
- Re: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6… Syam Madanapalli
- Re: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6… Ralph Droms
- Re: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6… Ralph Droms
- Re: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6… Thomas Narten
- RE: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6… Bernie Volz (volz)
- Re: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6… JINMEI Tatuya / 神明達哉
- RE: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6… timothy enos
- RE: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6… timothy enos
- [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6-ra-… Bob Hinden
- [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6-ra-… Pekka Savola
- [dhcwg] RE: IPv6 WG Last Call:draft-ietf-ipv6-ra-… john.loughney
- [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6-ra-… Bob Hinden
- [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6-ra-… Tim Hartrick
- Re: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6… Ralph Droms
- [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6-ra-… Ralph Droms
- [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6-ra-… Ralph Droms
- [dhcwg] RE: IPv6 WG Last Call:draft-ietf-ipv6-ra-… Soliman, Hesham
- [dhcwg] RE: IPv6 WG Last Call:draft-ietf-ipv6-ra-… Bound, Jim
- [dhcwg] RE: IPv6 WG Last Call:draft-ietf-ipv6-ra-… Bound, Jim
- [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6-ra-… JINMEI Tatuya / 神明達哉
- [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6-ra-… Tim Hartrick
- Re: [dhcwg] dhc wg last call on "DHCP Relay Agent… Thomas Narten