RE: [dhcwg] dhcpv6-24: movement detection and Confirm message

"Bound, Jim" <Jim.Bound@hp.com> Sun, 12 May 2002 13:50 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16727 for <dhcwg-archive@odin.ietf.org>; Sun, 12 May 2002 09:50:20 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id JAA20893 for dhcwg-archive@odin.ietf.org; Sun, 12 May 2002 09:50:31 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20265; Sun, 12 May 2002 09:45:07 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA25433 for <dhcwg@optimus.ietf.org>; Sun, 12 May 2002 00:57:40 -0400 (EDT)
Received: from zmamail03.zma.compaq.com (zmamail03.zma.compaq.com [161.114.64.103]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28800 for <dhcwg@ietf.org>; Sun, 12 May 2002 00:57:27 -0400 (EDT)
Received: from tayexg11.americas.cpqcorp.net (tayexg11.americas.cpqcorp.net [16.103.130.96]) by zmamail03.zma.compaq.com (Postfix) with ESMTP id BEBF58D64; Sun, 12 May 2002 00:57:38 -0400 (EDT)
Received: from tayexc13.americas.cpqcorp.net ([16.103.130.26]) by tayexg11.americas.cpqcorp.net with Microsoft SMTPSVC(5.0.2195.2966); Sun, 12 May 2002 00:57:38 -0400
x-mimeole: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Subject: RE: [dhcwg] dhcpv6-24: movement detection and Confirm message
Date: Sun, 12 May 2002 00:57:38 -0400
Message-ID: <9C422444DE99BC46B3AD3C6EAFC9711B022D2A5C@tayexc13.americas.cpqcorp.net>
Thread-Topic: [dhcwg] dhcpv6-24: movement detection and Confirm message
Thread-Index: AcH3V4PJUN5PVx7lTziczGQXriaNzQBfXSSA
From: "Bound, Jim" <Jim.Bound@hp.com>
To: Thomas Narten <narten@us.ibm.com>, "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>
Cc: dhcwg@ietf.org
X-OriginalArrivalTime: 12 May 2002 04:57:38.0622 (UTC) FILETIME=[8A1335E0:01C1F971]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id AAA25434
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org
Content-Transfer-Encoding: 8bit

How about we drop it and permit Renew to to confirm if it wants to?

/jim

> -----Original Message-----
> From: Thomas Narten [mailto:narten@us.ibm.com]
> Sent: Thursday, May 09, 2002 8:42 AM
> To: Bernie Volz (EUD)
> Cc: dhcwg@ietf.org
> Subject: Re: [dhcwg] dhcpv6-24: movement detection and 
> Confirm message 
> 
> 
> > It is just one of the ways a client could determine whether it
> > moved; it really isn't a requirement to have within the DHCP
> > specification.
> 
> Right.
> 
> > Do note however that since RAs don't have a unique link ID (yet?)
> > and a RA might contain no prefixes (just have the "M" flag set), and
> > in this case Confirm could be useful.
> 
> I think that future work might better handle this.
> 
> One approach might be to leave the Confirm stuff in for now, and if
> better or more general ways of detecting movement are defined, drop
> the config stuff in a revision. On the other hand, once its in the
> spec, servers will have to implement it forever, so taking it out only
> effects clients...
> 
> Thomas
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg
> 


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