Re: Version 6 Question: Client trying to get new parameters

Charlie Perkins <charliep@watson.ibm.com> Fri, 12 April 1996 12:58 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa12266; 12 Apr 96 8:58 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa12262; 12 Apr 96 8:58 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa06625; 12 Apr 96 8:58 EDT
Received: from localhost by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA08669; Fri, 12 Apr 1996 08:55:40 -0400
Date: Fri, 12 Apr 1996 08:55:40 -0400
Message-Id: <9604121231.AA33522@hawpub1.watson.ibm.com>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
X-Orig-Sender: dhcp-v4@bucknell.edu
Precedence: bulk
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Charlie Perkins <charliep@watson.ibm.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: Version 6 Question: Client trying to get new parameters
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4

> In the latest draft concerning DHCPv6 the way to reconfigure at least one 
> DHCP client is that the server sends a DHCP Reconfigure message to the 
> host(s) with the parameters that have to be changed.
> 
> But what if a client states that some of its parameters aren't valid 
> anymore? In the draft, I don't see how a client can ask for a new 
> configuration if the old one doesn't "fit" any more besides cancelling 
> his connection. So, the client is urged to start a new configuration 
> process, which is rather superfluous in my oppinion. 

The client can ask for a new configuration whether or not its
old configuration fits, although I'm not sure exactly what "fit"
means here.  Can you give some more concrete examples?  In the
worst case, when the client cannot identify to the server anything
about its old configuration, presumably the server will just carry
the old configuration as excess baggage until it expires.  Part of
our job with DHCPv6 will be to minimize the number of cases where
such excess baggage cannot be eliminated.

> Gernot Riegert

Charles Perkins