Re: [dhcwg] behavior on lifetime expiration (Re: commentson draft-ietf-dhc-lifetime-01.txt)

JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp> Tue, 31 August 2004 16:56 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 MAA04649; Tue, 31 Aug 2004 12:56:03 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2BaZ-0001f1-UP; Tue, 31 Aug 2004 12:34:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2B9N-0007fL-EI for dhcwg@megatron.ietf.org; Tue, 31 Aug 2004 12:06:25 -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 MAA28464 for <dhcwg@ietf.org>; Tue, 31 Aug 2004 12:06:23 -0400 (EDT)
Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2BBL-0006uZ-Mz for dhcwg@ietf.org; Tue, 31 Aug 2004 12:08:30 -0400
Received: from ocean.jinmei.org (unknown [2001:200:0:8002:7516:52ec:cfc0:15e1]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 59CCC1525D; Wed, 1 Sep 2004 01:06:21 +0900 (JST)
Date: Wed, 01 Sep 2004 01:06:20 +0900
Message-ID: <y7vwtzf70n7.wl@ocean.jinmei.org>
From: JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp>
To: Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] behavior on lifetime expiration (Re: commentson draft-ietf-dhc-lifetime-01.txt)
In-Reply-To: <001601c48a40$8a411e80$6401a8c0@amer.cisco.com>
References: <y7vfz6cenvy.wl@ocean.jinmei.org> <001601c48a40$8a411e80$6401a8c0@amer.cisco.com>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: dhcwg@ietf.org, 'Ted Lemon' <mellon@nominum.com>
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

>>>>> On Tue, 24 Aug 2004 21:12:07 -0400, 
>>>>> "Bernie Volz" <volz@cisco.com> said:

> You'd prefer IPv4 based information over IPv6?

No, in that example, I assumed a dual-stack host.

> And DHCPv4, if Inform was used, doesn't have *ANY* time to expire the
> information - so I don't think you'd want to use this information in
> preference to DHCPv6 information with a time?

I think I would, since in this case I'd regard the "expired" DHCPv6
information as less reliable than DHCPv4 information without any
expiration time.

But I won't stick to this point any more as I (perhaps implicitly)
said in my response to Ted.   Let's just throw away this
mostly-imaginary scenario.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

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