Re: [dhcwg] WGLC: draft-ietf-dhc-relay-id-suboption-09.txt

Bharat Joshi <bharat_joshi@infosys.com> Thu, 02 February 2012 08:57 UTC

Return-Path: <bharat_joshi@infosys.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A9C221F87A3 for <dhcwg@ietfa.amsl.com>; Thu, 2 Feb 2012 00:57:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.099
X-Spam-Level:
X-Spam-Status: No, score=-7.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ccwSqsgzTSWF for <dhcwg@ietfa.amsl.com>; Thu, 2 Feb 2012 00:57:44 -0800 (PST)
Received: from KECGATE08.infosys.com (kecgate08.infosysconsulting.com [122.98.10.33]) by ietfa.amsl.com (Postfix) with ESMTP id 2BCD221F87A0 for <dhcwg@ietf.org>; Thu, 2 Feb 2012 00:57:43 -0800 (PST)
X-TM-IMSS-Message-ID: <1a584f360004a94e@infosys.com>
Received: from blrkechub01.ad.infosys.com ([10.66.236.41]) by infosys.com ([122.98.10.33]) with ESMTP (TREND IMSS SMTP Service 7.1) id 1a584f360004a94e ; Thu, 2 Feb 2012 14:27:51 +0530
Received: from blrkechub12.ad.infosys.com (10.66.236.47) by blrkechub01.ad.infosys.com (10.66.236.41) with Microsoft SMTP Server (TLS) id 8.2.176.0; Thu, 2 Feb 2012 14:27:41 +0530
Received: from BLRKECMBX02.ad.infosys.com ([10.66.236.25]) by blrkechub12.ad.infosys.com ([10.66.236.47]) with mapi; Thu, 2 Feb 2012 14:27:40 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: Shankari Vaidyalingam <shankari.v2k6@gmail.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Date: Thu, 02 Feb 2012 14:24:37 +0530
Thread-Topic: [dhcwg] WGLC: draft-ietf-dhc-relay-id-suboption-09.txt
Thread-Index: Aczgogji3IFa1+nqS1KRRCijC1JHWAA5kGRW
Message-ID: <31D55C4D55BEED48A4459EB64567589A118C41DA25@BLRKECMBX02.ad.infosys.com>
References: <CAGeyXNcUbko5ZL0AzK0KbkuuOp3dm0kLyqfuYat8drGNFyT7mQ@mail.gmail.com>
In-Reply-To: <CAGeyXNcUbko5ZL0AzK0KbkuuOp3dm0kLyqfuYat8drGNFyT7mQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] WGLC: draft-ietf-dhc-relay-id-suboption-09.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2012 08:57:45 -0000

Hi Shankari,

       Thanks a lot for reviewing the draft and your comments. Please see my response in line.

Regards,
Bharat

> Please find below some queries on the relay-id draft:
> (1) When the relay-id is not configured by the user then can you please let me know what would be the behavior in the event of relay-agent crash?

If the relay agent is not configured by the administrator then relay agent will not be able to use bulk-lease query in the case of crash. It may still use lease query by remote-id to retrieve address bindings.

> (2) Can you let me know how the relay-id is maintained unique across the relay agents connected to a particular server.

A network administrator will have to ensure the uniqueness of the relay-id across the network.

> (3) When the relay-agent recovers from crash and sends a "bulk-lease-query" with the relay-id to restore the previous configuration/mappings, what would be the approx amount of recovery time allowed for full functionality of relay agent to resume.
>

It might depend on the number of active leases that were allocated through this relay agent when it went down.
**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message. Further, you are not 
to copy, disclose, or distribute this e-mail or its contents to any other person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys has taken 
every reasonable precaution to minimize this risk, but is not liable for any damage 
you may sustain as a result of any virus in this e-mail. You should carry out your 
own virus checks before opening the e-mail or attachment. Infosys reserves the 
right to monitor and review the content of all messages sent to or from this e-mail 
address. Messages sent to or from this e-mail address may be stored on the 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***