IETF Logo Mail Archive

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

Ted Lemon <Ted.Lemon@nominum.com> Wed, 01 September 2004 18:21 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 OAA17964; Wed, 1 Sep 2004 14:21:05 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2ZIB-0006ki-Am; Wed, 01 Sep 2004 13:53:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2Yfv-0005r6-41 for dhcwg@megatron.ietf.org; Wed, 01 Sep 2004 13:13:35 -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 NAA11674 for <dhcwg@ietf.org>; Wed, 1 Sep 2004 13:13:31 -0400 (EDT)
Received: from toccata.fugue.com ([204.152.186.142]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2Yi8-00062O-76 for dhcwg@ietf.org; Wed, 01 Sep 2004 13:15:53 -0400
Received: from [10.0.2.8] (neubayern.net [66.93.162.100]) by toccata.fugue.com (Postfix) with ESMTP id 125E41B225E for <dhcwg@ietf.org>; Wed, 1 Sep 2004 12:11:50 -0500 (CDT)
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <20040901123029.GI15000@sverresborg.uninett.no>
References: <y7vhdrl56ol.wl@ocean.jinmei.org> <20040803033357.GA20506@sverresborg.uninett.no> <y7veklyqkbx.wl@ocean.jinmei.org> <A9C62C40-F510-11D8-AE27-000A95D9C74C@nominum.com> <y7vfz6cenvy.wl@ocean.jinmei.org> <6C20AA0D-F5DF-11D8-8541-000A95D9C74C@nominum.com> <y7vy8jv70uo.wl@ocean.jinmei.org> <20040901123029.GI15000@sverresborg.uninett.no>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <3EA34C4F-FC3A-11D8-8C0B-000D93C4B69A@nominum.com>
Content-Transfer-Encoding: 7bit
From: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] behavior on lifetime expiration (Re: comments on draft-ietf-dhc-lifetime-01.txt)
Date: Wed, 01 Sep 2004 10:13:29 -0700
To: dhcwg@ietf.org
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
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 Sep 1, 2004, at 5:30 AM, Stig Venaas wrote:
> What worries me though, is that it might not be possible for
> a client to distinguish between movement and renumbering. The fact
> that a new prefix is announced in RAs is not sufficient.

I would like to point out the work that they're doing in the DNA 
working group.   This is what I had in mind when I spoke earlier about 
detecting that the client had moved.   This work does not depend on 
noticing differences in RA messages.


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

v2.23.0 | Report a Bug | By Email