IETF Logo Mail Archive

Re: [dhcwg] dhc-lifetime-01: dropping omitted options

Ted Lemon <mellon@fugue.com> Tue, 31 August 2004 17:07 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05603; Tue, 31 Aug 2004 13:07:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2BzV-00024l-Fz; Tue, 31 Aug 2004 13:00:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2Bd7-0003UM-Hp for dhcwg@megatron.ietf.org; Tue, 31 Aug 2004 12:37:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02154 for <dhcwg@ietf.org>; Tue, 31 Aug 2004 12:37:07 -0400 (EDT)
Received: from toccata.fugue.com ([204.152.186.142]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2Bf5-00086W-EE for dhcwg@ietf.org; Tue, 31 Aug 2004 12:39:14 -0400
Received: from [10.0.2.8] (neubayern.net [66.93.162.100]) by toccata.fugue.com (Postfix) with ESMTP id D48201B22C8 for <dhcwg@ietf.org>; Tue, 31 Aug 2004 11:35:28 -0500 (CDT)
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <20040831120208.GM2203@sverresborg.uninett.no>
References: <000e01c486b3$66af02b0$6401a8c0@amer.cisco.com> <6493.1093586912@munnari.OZ.AU> <20040831120208.GM2203@sverresborg.uninett.no>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <F9E926EB-FB6B-11D8-8C0B-000D93C4B69A@fugue.com>
Content-Transfer-Encoding: 7bit
From: Ted Lemon <mellon@fugue.com>
Subject: Re: [dhcwg] dhc-lifetime-01: dropping omitted options
Date: Tue, 31 Aug 2004 09:36:58 -0700
To: dhcwg@ietf.org
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: 7bit
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
Content-Transfer-Encoding: 7bit

On Aug 31, 2004, at 5:02 AM, Stig Venaas wrote:
> I did not say any about what should happen if some config data is
> removed from one client update to the next. Do you really want that
> in? I'm not sure I do, since as also some others agreed to, it's a
> more generic problem. If I were to write text, I would say that it
> should indeed be removed.

I think we need to collect some experience on this, and that we should 
update the RFC later when we have more information.   For now, we 
should not say what to do.   I can easily think of a byzantine set of 
specifications for how to do this, but I'm not sure they're either 
necessary or correct.


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

v2.13.0 | Report a Bug | By Email