IETF Logo Mail Archive

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

Ted Lemon <Ted.Lemon@nominum.com> Wed, 08 June 2011 17:57 UTC

Return-Path: <Ted.Lemon@nominum.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 AAA2B11E81BA for <dhcwg@ietfa.amsl.com>; Wed, 8 Jun 2011 10:57:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 x+b0xiQCIup7 for <dhcwg@ietfa.amsl.com>; Wed, 8 Jun 2011 10:57:25 -0700 (PDT)
Received: from exprod7og121.obsmtp.com (exprod7og121.obsmtp.com [64.18.2.20]) by ietfa.amsl.com (Postfix) with ESMTP id D72CC11E8095 for <dhcwg@ietf.org>; Wed, 8 Jun 2011 10:57:24 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob121.postini.com ([64.18.6.12]) with SMTP ID DSNKTe+4BLYAUE7uFqSitgrXbK7/UwtZuHjU@postini.com; Wed, 08 Jun 2011 10:57:24 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id D8EEAF8050 for <dhcwg@ietf.org>; Wed, 8 Jun 2011 10:57:23 -0700 (PDT)
Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "webmail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id CBB01190059; Wed, 8 Jun 2011 10:57:23 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from vpna-148.vpn.nominum.com (64.89.227.148) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 8 Jun 2011 10:57:23 -0700
MIME-Version: 1.0 (Apple Message framework v1237.1)
Content-Type: text/plain; charset="us-ascii"
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <31D55C4D55BEED48A4459EB64567589A115E3C9F1D@BLRKECMBX02.ad.infosys.com>
Date: Wed, 08 Jun 2011 13:57:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <243EA4AA-9165-4BC5-BE81-50E219A5F35E@nominum.com>
References: <20110604170424.3363.68771.idtracker@ietfa.amsl.com> <31D55C4D55BEED48A4459EB64567589A115E3C9F15@BLRKECMBX02.ad.infosys.com>, <BANLkTi=WiPMfR1cFmwSEehjzAWk97efBMQ@mail.gmail.com> <31D55C4D55BEED48A4459EB64567589A115E3C9F1B@BLRKECMBX02.ad.infosys.com>, <9B800A80-B90E-47DF-91B7-19DECBC32A5E@nominum.com> <31D55C4D55BEED48A4459EB64567589A115E3C9F1D@BLRKECMBX02.ad.infosys.com>
To: Bharat Joshi <bharat_joshi@infosys.com>
X-Mailer: Apple Mail (2.1237.1)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] 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: Wed, 08 Jun 2011 17:57:25 -0000

On Jun 6, 2011, at 9:13 AM, Bharat Joshi wrote:
> At present, we do not have any other use for this field. This 'type' was inspired from the previous revision of this document and we decided to keep it there thinking that more type of relay-ids may come in future.

I think the bottom line is that if you can't figure out what the type field does, you should take it out.   We are not experiencing a shortage of DHCPv6 option codes, so there's no reason to keep complexity in the spec to account for an unknown future circumstance that may or may not come to exist.

v2.23.0 | Report a Bug | By Email