Re: [dhcwg] FW: I-D Action: draft-ietf-dhc-relay-id-suboption-08.txt

Bharat Joshi <bharat_joshi@infosys.com> Mon, 06 June 2011 09:38 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 7168611E80D7 for <dhcwg@ietfa.amsl.com>; Mon, 6 Jun 2011 02:38:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WRgfLBG9Y2hf for <dhcwg@ietfa.amsl.com>; Mon, 6 Jun 2011 02:38:19 -0700 (PDT)
Received: from kecgate02.infosys.com (kecgate02.infosys.com [122.98.14.32]) by ietfa.amsl.com (Postfix) with ESMTP id 21A0A11E80D2 for <dhcwg@ietf.org>; Mon, 6 Jun 2011 02:38:18 -0700 (PDT)
X-TM-IMSS-Message-ID: <0b23e7f4001f8ce7@infosys.com>
Received: from blrkechub04.ad.infosys.com ([10.66.236.44]) by infosys.com ([122.98.14.32]) with ESMTP (TREND IMSS SMTP Service 7.1) id 0b23e7f4001f8ce7 ; Mon, 6 Jun 2011 15:01:30 +0530
Received: from BLRKECMBX02.ad.infosys.com ([10.66.236.22]) by blrkechub04.ad.infosys.com ([10.66.236.44]) with mapi; Mon, 6 Jun 2011 15:08:09 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: Pavan Kurapati <pavan.kurapati@gmail.com>
Date: Mon, 06 Jun 2011 15:06:16 +0530
Thread-Topic: [dhcwg] FW: I-D Action: draft-ietf-dhc-relay-id-suboption-08.txt
Thread-Index: AcwjkYF5cESoO/qCT46gIJzndwEUPQAm600V
Message-ID: <31D55C4D55BEED48A4459EB64567589A115E3C9F1B@BLRKECMBX02.ad.infosys.com>
References: <20110604170424.3363.68771.idtracker@ietfa.amsl.com> <31D55C4D55BEED48A4459EB64567589A115E3C9F15@BLRKECMBX02.ad.infosys.com>, <BANLkTi=WiPMfR1cFmwSEehjzAWk97efBMQ@mail.gmail.com>
In-Reply-To: <BANLkTi=WiPMfR1cFmwSEehjzAWk97efBMQ@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
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] FW: I-D Action: draft-ietf-dhc-relay-id-suboption-08.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: Mon, 06 Jun 2011 09:38:20 -0000

Pavan,

       Thanks a lot for the quick review.

       Will rephrase the sentence.

       Yes. 'type' field has been kept there to keep any future extensibility possible.

Regards,
Bharat
________________________________________
From: Pavan Kurapati [pavan.kurapati@gmail.com]
Sent: Sunday, June 05, 2011 8:31 PM
To: Bharat Joshi
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] FW: I-D Action: draft-ietf-dhc-relay-id-suboption-08.txt

Bharat,

Draft looks good. Just one minor editorial comment and one clarification needed below.

> "DHCP typically identifies clients based on information in their DHCP messages"

You might want to replace the first "DHCP" with DHCP server. If you do not want to restrict to server here you may say network entity

I assume the inclusion of "type" field now is for any future consideration of including other types like DUID? Else it seems redundant, now that we have only 1 type in the sub-option.

Thanks,
Pavan


On Sun, Jun 5, 2011 at 2:33 PM, Bharat Joshi <bharat_joshi@infosys.com<mailto:bharat_joshi@infosys.com>> wrote:
Hi All,

     This draft was under IESG review and a new revision was required as it had three DISCUSS points. Mark was not getting enough time to push this work. We needed this draft for Bulk Lease Query work and so we decided to help.

      Apart from the three DISCUSS position, there was a comment from Ted. Ted had suggested that the usage of DUID as relay-id as defined in this draft is not correct. DUID is typically tied down to the device and the use cases in this draft required same relay-id to be used if a relay-agent is replaced.

       In this revision, we have addressed all the DISCUSS positions. We have also removed both the relay-id type ASCII and DUID. We have introduced a new relay-id type OPAQUE. This new relay-id type can be administratively configured and is a series of octets.

       Now, as the above changes are more than minor changes, I think that it will first have to go through working-group. So I request people to review this draft ( only 5 pages ) and post their comments.

Regards,
Bharat
________________________________________
From: dhcwg-bounces@ietf.org<mailto:dhcwg-bounces@ietf.org> [dhcwg-bounces@ietf.org<mailto:dhcwg-bounces@ietf.org>] On Behalf Of internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> [internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>]
Sent: Saturday, June 04, 2011 10:34 PM
To: i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>
Cc: dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Subject: [dhcwg] I-D Action: draft-ietf-dhc-relay-id-suboption-08.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

       Title           : The DHCPv4 Relay Agent Identifier Suboption
       Author(s)       : Bharat Joshi
                         Mark Stapp
       Filename        : draft-ietf-dhc-relay-id-suboption-08.txt
       Pages           : 8
       Date            : 2011-06-04

  This draft defines a new Relay Agent Identifier suboption for the
  Dynamic Host Configuration Protocol&#39;s (DHCP) Relay Agent Information
  option.  The suboption carries a value that uniquely identifies the
  relay agent device within the administrative domain.  The value is
  typically administratively-configured in the relay agent.  The
  suboption allows a DHCP relay agent to include the identifier in the
  DHCP messages it sends.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-relay-id-suboption-08.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-dhc-relay-id-suboption-08.txt
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org<mailto:dhcwg@ietf.org>
https://www.ietf.org/mailman/listinfo/dhcwg

**************** 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***
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org<mailto:dhcwg@ietf.org>
https://www.ietf.org/mailman/listinfo/dhcwg