Re: [dhcwg] Comments on 22 rev of the draft

Vijay Bhaskar A K <vijayak@india.hp.com> Wed, 23 January 2002 18:51 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 NAA20427 for <dhcwg-archive@odin.ietf.org>; Wed, 23 Jan 2002 13:51:40 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id NAA11248 for dhcwg-archive@odin.ietf.org; Wed, 23 Jan 2002 13:51:39 -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 NAA10549; Wed, 23 Jan 2002 13:36:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA10527 for <dhcwg@optimus.ietf.org>; Wed, 23 Jan 2002 13:36:42 -0500 (EST)
Received: from palrel11.hp.com (palrel11.hp.com [156.153.255.246]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19744 for <dhcwg@ietf.org>; Wed, 23 Jan 2002 13:36:40 -0500 (EST)
Received: from dce.india.hp.com (dce.india.hp.com [15.10.45.122]) by palrel11.hp.com (Postfix) with ESMTP id AC28CE004A4; Wed, 23 Jan 2002 10:36:09 -0800 (PST)
Received: (from vijayak@localhost) by dce.india.hp.com (8.8.6 (PHNE_17190)/8.8.6 SMKit7.02) id AAA04214; Thu, 24 Jan 2002 00:10:28 +0530 (IST)
From: Vijay Bhaskar A K <vijayak@india.hp.com>
Message-Id: <200201231840.AAA04214@dce.india.hp.com>
Subject: Re: [dhcwg] Comments on 22 rev of the draft
To: mellon@nominum.com
Date: Thu, 24 Jan 2002 00:10:27 +0530 (IST)
Cc: dhcwg@ietf.org, vijayak@india.hp.com
In-Reply-To: <51B1D23E-1024-11D6-AF3C-00039317663C@nominum.com> from Ted Lemon at Jan "23, " 2002 "06:12:02" pm
X-Mailer: ELM [$Revision: 1.17.214.2 $]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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

> 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
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