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

Jim Bound <seamus@bit-net.com> Thu, 24 January 2002 13:58 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 IAA21488 for <dhcwg-archive@odin.ietf.org>; Thu, 24 Jan 2002 08:58:25 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id IAA28438 for dhcwg-archive@odin.ietf.org; Thu, 24 Jan 2002 08:58:28 -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 IAA28248; Thu, 24 Jan 2002 08:48:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA28166 for <dhcwg@optimus.ietf.org>; Thu, 24 Jan 2002 08:48:30 -0500 (EST)
Received: from mail.users.bit-net.com (www.bit-net.com [208.146.132.4]) by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA21307 for <dhcwg@ietf.org>; Thu, 24 Jan 2002 08:48:24 -0500 (EST)
Received: from localhost by mail.users.bit-net.com; (5.65v3.2/1.1.8.2/30Jul96-0143PM) id AA20349; Thu, 24 Jan 2002 08:46:46 -0500
Date: Thu, 24 Jan 2002 08:46:46 -0500
From: Jim Bound <seamus@bit-net.com>
To: Martin Stiemerling <Martin.Stiemerling@ccrle.nec.de>
Cc: Vijay Bhaskar A K <vijayak@india.hp.com>, dhcwg@ietf.org
Subject: Re: [dhcwg] Comments on 22 rev of the draft
In-Reply-To: <9080000.1011864530@elgar>
Message-Id: <Pine.OSF.3.95.1020124084540.9559G-100000@www.bit-net.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
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

Martin,

It is permissable to get addresses from stateless and stateful in IPv6
addr conf.  


/jim


On Thu, 24 Jan 2002, Martin Stiemerling wrote:

> --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 mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg