[dhcwg] Question on DHCPv6 Draft 23.

"Paul Tan" <tanpaul@cwc.nus.edu.sg> Wed, 20 March 2002 06:48 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 BAA16906 for <dhcwg-archive@odin.ietf.org>; Wed, 20 Mar 2002 01:48:38 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id BAA25740 for dhcwg-archive@odin.ietf.org; Wed, 20 Mar 2002 01:48: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 BAA25563; Wed, 20 Mar 2002 01:46:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA25542 for <dhcwg@optimus.ietf.org>; Wed, 20 Mar 2002 01:46:04 -0500 (EST)
Received: from cwcsun41.cwc.nus.edu.sg (cwcsun41.cwc.nus.edu.sg [137.132.163.102]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16849 for <dhcwg@ietf.org>; Wed, 20 Mar 2002 01:46:00 -0500 (EST)
Received: from tanhl (tanhl.cwc.nus.edu.sg [172.16.2.66]) by cwcsun41.cwc.nus.edu.sg (8.9.3/8.9.3) with SMTP id OAA22883 for <dhcwg@ietf.org>; Wed, 20 Mar 2002 14:44:43 +0800 (SGT)
Message-ID: <010501c1cfdc$020b6320$420210ac@tanhl>
From: "Paul Tan" <tanpaul@cwc.nus.edu.sg>
To: <dhcwg@ietf.org>
References: <Pine.OSF.3.95.1020124084540.9559G-100000@www.bit-net.com> <8100000.1011889314@elgar>
Date: Wed, 20 Mar 2002 14:53:57 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] Question on DHCPv6 Draft 23.
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

Hi all,

we are currently trying to implement a DHCPv6 client/server (draft 23) in
Linux environment. Are there any active implementations working on the
latest DHCP draft 23 ?

I have a few questions concerning the DHCPv6 draft 23.

1) After a client sends out a SOLICIT with an IA option attached (no IA Addr
Opt), the server will basically reply with an ADVERTISE message with some
addresses attached in the IA Addr options.

- Does the lifetime for this IA starts after the server sends the ADVERTISE
message ? How does the server knows whether if the client has decided to use
the address advertised by this server, when in fact the client has chosen
some other server ?

2) When the client receives the ADVERTISE message, it will attempt to
configure its interface with the assigned address from the list of server's
ADVERTISE messages.
- Does it need to send a REQUEST message immediately after the ADVERTISE
message to confirm that the client is using the address from a particular
server?
- What is the main purpose of the REQUEST message ? Get the configuration
info of a particular IA ?

3) I'm a bit confused with the following paragraph in the draft...
- ... if the server will not assign any addresses to IAs in a subsequent
REQUEST from the client, the server SHOULD either send an ADV message to the
client that includes only a status code option (AddrUnavail) for the user or
not respond to the SOLICIT message....

Thank you for your kind attention.

Regards,
Paul
Institute for Communications Research



_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg