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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 09 June 2011 09:44 UTC

Return-Path: <alexandru.petrescu@gmail.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 2D80B11E8071 for <dhcwg@ietfa.amsl.com>; Thu, 9 Jun 2011 02:44:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 O8Jlb15SZvde for <dhcwg@ietfa.amsl.com>; Thu, 9 Jun 2011 02:44:36 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) by ietfa.amsl.com (Postfix) with ESMTP id AB508228003 for <dhcwg@ietf.org>; Thu, 9 Jun 2011 02:44:35 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.2) with ESMTP id p599iXM9026386 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 9 Jun 2011 11:44:33 +0200
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id p599iWK8028851; Thu, 9 Jun 2011 11:44:33 +0200 (envelope-from alexandru.petrescu@gmail.com)
Received: from [132.166.133.178] (is010173.intra.cea.fr [132.166.133.178]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.1) with ESMTP id p599iWrH018941; Thu, 9 Jun 2011 11:44:32 +0200
Message-ID: <4DF09600.8070209@gmail.com>
Date: Thu, 09 Jun 2011 11:44:32 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: dhcwg@ietf.org
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> <243EA4AA-9165-4BC5-BE81-50E219A5F35E@nominum.com> <E1CE3E6E6D4E1C438B0ADC9FFFA345EAD39BCA@SZXEML514-MBS.china.huawei.com>
In-Reply-To: <E1CE3E6E6D4E1C438B0ADC9FFFA345EAD39BCA@SZXEML514-MBS.china.huawei.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
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: Thu, 09 Jun 2011 09:44:39 -0000

Le 09/06/2011 04:29, Leaf yeh a écrit :
> Ted - We are not experiencing a shortage of DHCPv6 option codes,...

Yes, we use 66 decimal 0x42 for a new yet-to-be-documented option, we
think 66 may be the first available (IANA, isc sw) and max seems to be
255 even though 1 more byte can there be.

Alex

>
> Supposed you're talking about the space shortage of the DHCPv4
> option codes.
>
>
>
> -----Original Message----- From: dhcwg-bounces@ietf.org
> [mailto:dhcwg-bounces@ietf.org] On Behalf Of Ted Lemon Sent:
> Thursday, June 09, 2011 1:57 AM To: Bharat Joshi Cc: dhcwg@ietf.org
> Subject: Re: [dhcwg] I-D Action:
> draft-ietf-dhc-relay-id-suboption-08.txt
>
> 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.
>
>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>