Re: [dhcwg] Comments on 22 rev of the draft
Martin Stiemerling <Martin.Stiemerling@ccrle.nec.de> Thu, 24 January 2002 09:37 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18334 for <dhcwg-archive@odin.ietf.org>; Thu, 24 Jan 2002 04:37:47 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id EAA20477 for dhcwg-archive@odin.ietf.org; Thu, 24 Jan 2002 04:37:49 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA19665; Thu, 24 Jan 2002 04:29:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA19645 for <dhcwg@optimus.ietf.org>; Thu, 24 Jan 2002 04:29:24 -0500 (EST)
Received: from yamato.ccrle.nec.de (yamato.ccrle.nec.de [195.37.70.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18197 for <dhcwg@ietf.org>; Thu, 24 Jan 2002 04:29:20 -0500 (EST)
Received: from citadel.mobility.ccrle.nec.de ([192.168.156.1]) by yamato.ccrle.nec.de (8.11.6/8.10.1) with ESMTP id g0O9TRj04415; Thu, 24 Jan 2002 10:29:27 +0100 (CET)
Received: from elgar (elgar.heidelberg.ccrle.nec.de [192.168.102.180]) by citadel.mobility.ccrle.nec.de (Postfix on SuSE eMail Server 2.0) with ESMTP id AFE71C05B; Thu, 24 Jan 2002 10:28:53 +0100 (CET)
Date: Thu, 24 Jan 2002 10:28:50 +0100
From: Martin Stiemerling <Martin.Stiemerling@ccrle.nec.de>
To: Vijay Bhaskar A K <vijayak@india.hp.com>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Comments on 22 rev of the draft
Message-ID: <9080000.1011864530@elgar>
In-Reply-To: <200201231840.AAA04214@dce.india.hp.com>
References: <200201231840.AAA04214@dce.india.hp.com>
X-Mailer: Mulberry/2.1.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org
Content-Transfer-Encoding: 7bit
--On Donnerstag, Januar 24, 2002 00:10:27 +0530 Vijay Bhaskar A K <vijayak@india.hp.com> wrote: >> What possible use can there be in allowing the client to select the >> prefix that it wants? > > Please go through the follow scenario. Router is advertising 3ffe::/64 > prefix and a host has generated an address of prefix 3ffe::/64 using > router advertisements. Now, the host needs some more addresses of > prefix 3ffe::/64. It chooses to use stateful autoconf (dhcpv6). The The client has nothing to choose! When the IPv6 router says in his router advertisements "use stateless autoconfiguration" (Flags in router advertisement are M=0, O=0), the client has to use stateless autoconfiguration, i.e. form an IPv6 address with the advertised prefix. When the router says "use stateful autoconfiguration" (Flags in router advertisement are M=1, O=1), the client has to use stateful autoconfiguration, i.e. request an IPv6 address from a DHCPv6 server. See RFC 2641, section 4.2, and RFC 2462, section 5.2. We can't change the base IPv6 specification for DHCPv6. > server sends advertise saying that, it can allocate addresses in > 3ffe::/64 and 5ffe::/64. Since, the client's wish is to get only > 3ffe::/64, it can tell the server its preference for the prefix while > sending Request. This will help in server not allocating the addresses > that the client doesn't want. > > Moreover, if the client wants to communicate with the external site, it > requires global rather than site local addresses. Here also, it can > show the preference. > > DHCP clients are intended to arrange for ad-hoc >> connections. Under what circumstances would the client have any >> knowledge of what prefixes might be better than others? > > Obviosuly, the client using the stateless autoconf, knows the prefixes > in the link, (by router advertisements). From the Advertise messages of > the various servers, it knows about the prefixes in the link. > > > > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www1.ietf.org/mailman/listinfo/dhcwg > Martin Stiemerling NEC Europe Ltd. -- Network Laboratories Martin.Stiemerling@ccrle.nec.de IPv4: http://www.ccrle.nec.de IPv6: http://www.ipv6.ccrle.nec.de _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Comments on 22 rev of the draft Vijay Bhaskar A K
- RE: [dhcwg] Comments on 22 rev of the draft Bernie Volz (EUD)
- RE: [dhcwg] Comments on 22 rev of the draft Ralph Droms
- Re: [dhcwg] Comments on 22 rev of the draft Vijay Bhaskar A K
- Re: [dhcwg] Comments on 22 rev of the draft Vijay Bhaskar A K
- RE: [dhcwg] Comments on 22 rev of the draft Bernie Volz (EUD)
- RE: [dhcwg] Comments on 22 rev of the draft Bernie Volz (EUD)
- Re: [dhcwg] Comments on 22 rev of the draft Vijay Bhaskar A K
- Re: [dhcwg] Comments on 22 rev of the draft Vijay Bhaskar A K
- RE: [dhcwg] Comments on 22 rev of the draft Bernie Volz (EUD)
- RE: [dhcwg] Comments on 22 rev of the draft Vijayabhaskar A K
- RE: [dhcwg] Comments on 22 rev of the draft Bernie Volz (EUD)
- Re: [dhcwg] Comments on 22 rev of the draft Ralph Droms
- Re: [dhcwg] Comments on 22 rev of the draft Vijay Bhaskar A K
- Re: [dhcwg] Comments on 22 rev of the draft Vijay Bhaskar A K
- Re: [dhcwg] Comments on 22 rev of the draft Ted Lemon
- Re: [dhcwg] Comments on 22 rev of the draft Vijay Bhaskar A K
- Re: [dhcwg] Comments on 22 rev of the draft Ted Lemon
- Re: [dhcwg] Comments on 22 rev of the draft Ted Lemon
- Re: [dhcwg] Comments on 22 rev of the draft Martin Stiemerling
- Re: [dhcwg] Comments on 22 rev of the draft Jim Bound
- Re: [dhcwg] Comments on 22 rev of the draft Martin Stiemerling
- [dhcwg] Question on DHCPv6 Draft 23. Paul Tan