Re: [dhcwg] dhcpv6-24: confirm vs. renew vs. rebind

Alexandru Petrescu<petrescu@crm.mot.com> Wed, 15 May 2002 14:03 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 KAA05314 for <dhcwg-archive@odin.ietf.org>; Wed, 15 May 2002 10:03:06 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id KAA22767 for dhcwg-archive@odin.ietf.org; Wed, 15 May 2002 10:03:20 -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 KAA22464; Wed, 15 May 2002 10:01:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA29718 for <dhcwg@optimus.ietf.org>; Wed, 15 May 2002 05:09:28 -0400 (EDT)
Received: from motgate3.mot.com (motgate3.mot.com [144.189.100.103]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22444 for <dhcwg@ietf.org>; Wed, 15 May 2002 05:09:13 -0400 (EDT)
Received: [from pobox3.mot.com (pobox3.mot.com [10.64.251.242]) by motgate3.mot.com (motgate3 2.1) with ESMTP id BAA28674 for <dhcwg@ietf.org>; Wed, 15 May 2002 01:57:24 -0700 (MST)]
Received: [from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id BAA23789 for <dhcwg@ietf.org>; Wed, 15 May 2002 01:56:23 -0700 (MST)]
Received: from thorgal.crm.mot.com (thorgal.crm.mot.com [140.101.173.1]) by az33exr02.mot.com (8.11.6/8.11.6) with ESMTP id g4F99lF07287; Wed, 15 May 2002 04:09:48 -0500
Received: from test9.crm.mot.com.crm.mot.com (test9.crm.mot.com [140.101.173.239]) by thorgal.crm.mot.com (Postfix) with ESMTP id 3F7C82EC86; Wed, 15 May 2002 11:09:16 +0200 (CEST)
To: Thomas Narten <narten@us.ibm.com>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] dhcpv6-24: confirm vs. renew vs. rebind
References: <200205081513.g48FD7W19372@rotala.raleigh.ibm.com>
From: Alexandru Petrescu <petrescu@crm.mot.com>
Date: Tue, 14 May 2002 22:48:35 +0200
In-Reply-To: <200205081513.g48FD7W19372@rotala.raleigh.ibm.com>
Message-ID: <m3elgecv6k.fsf@test9.crm.mot.com>
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Lines: 21
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

Thomas Narten <narten@us.ibm.com> writes:
> For the confirm, I gather that the only answer is "yes" or "no". If
> so, it would also be good to say that and point out that this message
> is used to decide whether a rebind/renew/request needs to be
> done. (note: In a separate note, I have questions about the overall
> utility of confirm.)

Hi, I'm not intending at all to fight over whether this particular
message is useful or not, especially since I was not involved in its
inclusion here.

Just wanted to mention a possible use that is to couple it with RIP
update messages within a small domain (what is small) to manage
mobility with host-based routes.  Within such a domain, access routers
are co-located with DHCP relays and the most central router is
co-located with the DHCP server.  The advantage of using confirm to
trigger the update is that the addition of the new route is triggered
from both ends of a path (from server and from relay), completing the
route supposedly faster.

Alex



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