Re: [dhcwg] Review of draft-ietf-dhc-option-guidelines

David Hankins <dhankins@google.com> Sun, 02 October 2011 05:05 UTC

Return-Path: <dhankins@google.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 1F4E021F8E3B for <dhcwg@ietfa.amsl.com>; Sat, 1 Oct 2011 22:05:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.976
X-Spam-Level:
X-Spam-Status: No, score=-105.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 y6OGj2UP9X4S for <dhcwg@ietfa.amsl.com>; Sat, 1 Oct 2011 22:05:47 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7D69D21F8E38 for <dhcwg@ietf.org>; Sat, 1 Oct 2011 22:05:47 -0700 (PDT)
Received: from hpaq12.eem.corp.google.com (hpaq12.eem.corp.google.com [172.25.149.12]) by smtp-out.google.com with ESMTP id p9258jgi000539 for <dhcwg@ietf.org>; Sat, 1 Oct 2011 22:08:45 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1317532125; bh=wtCJwmqoCTTD6Us1WJpERPqhV9s=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=pnDwVbNtmhuoff7VJz7RxjqoBCkh1MRpQECYLnk0TUMB4SDtPvuUrmC/gVOoRX6A0 yeLL7t5Dh1h1h6kFypiqQ==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:date: message-id:subject:from:to:cc:content-type:x-system-of-record; b=utNofFCFYbFT7lk8URp+MOJHiAbSXl5WUTBUnCq8/6UYXXP4VBTVOQFVKiiFzSSGH 8Su73sIQ64r8blwA/YLmg==
Received: from gyg8 (gyg8.prod.google.com [10.243.50.136]) by hpaq12.eem.corp.google.com with ESMTP id p9258hGU019418 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <dhcwg@ietf.org>; Sat, 1 Oct 2011 22:08:43 -0700
Received: by gyg8 with SMTP id 8so3059462gyg.20 for <dhcwg@ietf.org>; Sat, 01 Oct 2011 22:08:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Lf1W2WVrSeSkYO/kv9WlDhuBzix409qqwnwGbQYRtyQ=; b=wFIw22Iu/c3SCH4M0lcdNKyESP7JyYUMbhARHtzh+nC5qCnIakUB64J7WUmj+JbrYN 5zuv5ib9+h7VrYw1fW5w==
Received: by 10.101.171.5 with SMTP id y5mr339255ano.3.1317532122886; Sat, 01 Oct 2011 22:08:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.101.171.5 with SMTP id y5mr339251ano.3.1317532122654; Sat, 01 Oct 2011 22:08:42 -0700 (PDT)
Received: by 10.100.14.5 with HTTP; Sat, 1 Oct 2011 22:08:42 -0700 (PDT)
In-Reply-To: <CACLSHdQd5tE_Hmfz=RnpznTdRr4qwvk+YmaJeMtVQgCpxgeaHg@mail.gmail.com>
References: <5D36713D8A4E7348A7E10DF7437A4B920122B5BD@SZXEML506-MBS.china.huawei.com> <CACLSHdQd5tE_Hmfz=RnpznTdRr4qwvk+YmaJeMtVQgCpxgeaHg@mail.gmail.com>
Date: Sat, 01 Oct 2011 22:08:42 -0700
Message-ID: <CACLSHdRcT5cPZ1yQ=VXJd5WTT-FBQtH+e_BzGQxwHvPvT42UJA@mail.gmail.com>
From: David Hankins <dhankins@google.com>
To: Jiangsheng <jiangsheng@huawei.com>
Content-Type: multipart/alternative; boundary="001636c927fc26a72404ae49da17"
X-System-Of-Record: true
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Review of draft-ietf-dhc-option-guidelines
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: Sun, 02 Oct 2011 05:05:48 -0000

On Sat, Oct 1, 2011 at 9:45 PM, David Hankins <dhankins@google.com> wrote:

> 13. This draft says nothing about option orders, which is also important.
>> The principle should be not give any specific order when design a new DHCP
>> option. The option should be allowed to appear any place in the DHCP
>> message. The only exception is security option(s). They need to perform
>> algorithm over all other options. They may be allowed to located at the end.
>>
>
> It gets very hard to write concise language here, since the DHCPv6 style of
> options is for options to contain options whose codes are taken from the
> same option spaces.  "Anywhere in the packet" is nice and simple, but very
> wrong in DHCPv6.
>

I tell a lie, the "Clients Request their Options" section gives advice not
to rely on any ordering unless in the most dire of circumstance.

The discussion does go along with ORO/PRL, since there can be an expectation
that the ORO/PRL order leads to packet ordering.

-- 
David W. Hankins
SRE - Systems Engineer
Google, Inc.