IETF Logo Mail Archive

Re: [dhcwg] dhc wg last call on "DHCP Relay Agent AssignmentNotification Option"

Thomas Narten <narten@us.ibm.com> Wed, 10 May 2006 02:33 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FdeVr-00050z-Q3; Tue, 09 May 2006 22:33:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FdeVq-00050u-9D for dhcwg@ietf.org; Tue, 09 May 2006 22:33:18 -0400
Received: from e1.ny.us.ibm.com ([32.97.182.141]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FdeVp-0003Wn-24 for dhcwg@ietf.org; Tue, 09 May 2006 22:33:18 -0400
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e1.ny.us.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k4A2XE6O009752 for <dhcwg@ietf.org>; Tue, 9 May 2006 22:33:14 -0400
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay02.pok.ibm.com (8.12.10/NCO/VER6.8) with ESMTP id k4A2XCR6187800 for <dhcwg@ietf.org>; Tue, 9 May 2006 22:33:14 -0400
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.12.11/8.13.3) with ESMTP id k4A2XBqW031139 for <dhcwg@ietf.org>; Tue, 9 May 2006 22:33:11 -0400
Received: from cichlid.raleigh.ibm.com (sig-9-76-145-108.mts.ibm.com [9.76.145.108]) by d01av02.pok.ibm.com (8.12.11/8.12.11) with ESMTP id k4A2XB79031107; Tue, 9 May 2006 22:33:11 -0400
Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1]) by cichlid.raleigh.ibm.com (8.13.6/8.12.5) with ESMTP id k4A2WuKu017616; Tue, 9 May 2006 22:32:56 -0400
Message-Id: <200605100232.k4A2WuKu017616@cichlid.raleigh.ibm.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Subject: Re: [dhcwg] dhc wg last call on "DHCP Relay Agent AssignmentNotification Option"
In-Reply-To: Message from "Bernie Volz \(volz\)" <volz@cisco.com> of "Tue, 09 May 2006 22:09:25 EDT." <8E296595B6471A4689555D5D725EBB21019D0B6C@xmb-rtp-20a.amer.cisco.com>
Date: Tue, 09 May 2006 22:32:56 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: dhcwg@ietf.org, Stig Venaas <stig.venaas@uninett.no>, "Ralph Droms (rdroms)" <rdroms@cisco.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>
Errors-To: dhcwg-bounces@ietf.org

> It is 100% reliable in the sense that if the relay doesn't get the
> message, how would the client? Thus, the relay has at least as good
> information as the client (and in some cases, perhaps better since the
> message could always be lost between the relay and client).

Makes sense.

But, isn't one of the problems (if I recall from what is done in IPv4)
that relay agents can reboot and lose all their state? What happens
then? How does the relay recover? Is this extension going to be used
to help in that case too?

Thomas

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

v2.23.0 | Report a Bug | By Email