RE: [dhcwg] dhc wg last call on "DHCP Relay AgentAssignmentNotification Option"

"Bernie Volz \(volz\)" <volz@cisco.com> Wed, 10 May 2006 02:40 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FdecQ-0002MT-Pc; Tue, 09 May 2006 22:40:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FdecP-0002Ku-Sj for dhcwg@ietf.org; Tue, 09 May 2006 22:40:05 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FdecN-0003vG-Jy for dhcwg@ietf.org; Tue, 09 May 2006 22:40:05 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 09 May 2006 19:40:03 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.05,107,1146466800"; d="scan'208"; a="27702318:sNHT22494360"
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k4A2e3TL000241; Tue, 9 May 2006 22:40:03 -0400 (EDT)
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 9 May 2006 22:40:02 -0400
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] dhc wg last call on "DHCP Relay AgentAssignmentNotification Option"
Date: Tue, 09 May 2006 22:40:01 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB21019D0B7F@xmb-rtp-20a.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dhcwg] dhc wg last call on "DHCP Relay AgentAssignmentNotification Option"
Thread-Index: AcZz2jZAOPbWpR/1TU2nGHP0gKb/OQAAJDtg
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Thomas Narten <narten@us.ibm.com>
X-OriginalArrivalTime: 10 May 2006 02:40:02.0970 (UTC) FILETIME=[0A03EFA0:01C673DB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
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

That's what the DHCPv6 Lease Query we're working on drafting will solve
- the relay will be able to query the server for the client information
if it reboots.

- Bernie 

> -----Original Message-----
> From: Thomas Narten [mailto:narten@us.ibm.com] 
> Sent: Tuesday, May 09, 2006 10:33 PM
> To: Bernie Volz (volz)
> Cc: dhcwg@ietf.org; Stig Venaas; Ralph Droms (rdroms)
> Subject: Re: [dhcwg] dhc wg last call on "DHCP Relay 
> AgentAssignmentNotification Option" 
> 
> > 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
> 

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