Subject: RE: question on sending request to multiple servers

From: Bernie Volz <[email-masked]>
Date: Sun, 21 Jan 2001 20:20:40 -0500

I believe these problems will be solved by using a different message type
(number) for a renewal vs a new address request. Thus, if the packet is
multicast, all of the servers will see that it is a renewal request and can
respond correctly.

Please note that the draft that is out today doesn't have a unique message
type for initial requests, vs renewals, vs checks on boot, etc. Please see
the DHC WG notes from the San Diego IETF for more details.

- Bernie

-----Original Message-----
From: Vijaya Bhaskar A K [mailto:[email-masked]]
Sent: Saturday, January 20, 2001 2:51 AM
To: DHCPv6 discussion list
Subject: question on sending request to multiple servers

It is mentioned in the draft that at the expiration of T2,
the client initiates the request/reply message exchange.
This request message will be sent to a multicast address.
i have few questions on this.

1) Is this the request for assignment of a new ip-address to an IA? 
(OR) 
2) renewal of the a particular ip-address assigned to an IA?

case 1)
Since  this is a  multicast  message,  more than  server  can  assign an
IP-address.  This  means  for a single  reqeust,  the  client  gets many
IP-address.

case 2)
assume the server A which has assigned the particular ip-address
to the client is down. then, how can a server B renew the lease
for the ip-address assigned by server A? 

So, what is the actual use of sending the request message to mutiple
servers after the expiration of T2.

Regards,
Vijay