IETF Logo Mail Archive

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

Ted Lemon <Ted.Lemon@nominum.com> Wed, 08 May 2002 21:54 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 RAA24846 for <dhcwg-archive@odin.ietf.org>; Wed, 8 May 2002 17:54:16 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id RAA00876 for dhcwg-archive@odin.ietf.org; Wed, 8 May 2002 17:54:24 -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 RAA00770; Wed, 8 May 2002 17:52:47 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA00738 for <dhcwg@optimus.ietf.org>; Wed, 8 May 2002 17:52:46 -0400 (EDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24796 for <dhcwg@ietf.org>; Wed, 8 May 2002 17:52:37 -0400 (EDT)
Received: from green.bisbee.fugue.com (dsl-64-193-175-153.telocity.com [64.193.175.153]) by toccata.fugue.com (8.11.3/8.6.11) with ESMTP id g48LphS10430; Wed, 8 May 2002 14:51:43 -0700 (PDT)
Received: from tongpanyi (localhost [127.0.0.1]) by green.bisbee.fugue.com (8.10.2/8.6.11) with ESMTP id g48Lqg600560; Wed, 8 May 2002 16:52:42 -0500 (CDT)
Date: Wed, 08 May 2002 16:52:42 -0500
Subject: Re: [dhcwg] dhcpv6-24: movement detection and Confirm message
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v481)
Cc: Thomas Narten <narten@us.ibm.com>, dhcwg@ietf.org
To: "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <66F66129A77AD411B76200508B65AC69B4D3CE@EAMBUNT705>
Message-Id: <EC3A1CCB-62CD-11D6-A5AB-00039367340A@nominum.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.481)
Content-Transfer-Encoding: 7bit
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: 7bit

Probably the right way to do this is to say that if the client has reason 
to believe, based on the listed reasons or any other reasons, that it is on 
a different link, but that it cannot be sure it is on a different link, it 
SHOULD send a Confirm message.   If it is _sure_ that it is on another link 
(e.g., based on an RA), it SHOULD send a Solicit message.


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

v2.23.0 | Report a Bug | By Email