Re: [dhcwg] WGLC - draft-ietf-dhc-option-guidelines-12 - Respond by July 15

"Bernie Volz (volz)" <volz@cisco.com> Fri, 12 July 2013 14:13 UTC

Return-Path: <volz@cisco.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 4B9CE21E805E for <dhcwg@ietfa.amsl.com>; Fri, 12 Jul 2013 07:13:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 FziqzP47LI5G for <dhcwg@ietfa.amsl.com>; Fri, 12 Jul 2013 07:13:46 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 6520B21F9A48 for <dhcwg@ietf.org>; Fri, 12 Jul 2013 07:13:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2806; q=dns/txt; s=iport; t=1373638426; x=1374848026; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=PHjd/SMrzyMvOi+lkfGCQJ8gmrZWQnHqnwgOFUT1RfM=; b=kKSOFIAk4W5Ljvpn1JK3y09pW/yl8y3l7Ln0Ew2h9W1HGwzjnMLloOZd PJxBz+cjs5tbQkPlrGNA4sBEbcSL8j2jgBX5fOKrpv40uvDM2x+1CPGdi Yx3VRDrdTnR/pvjIUp5A5IwZdFY2tbBQEjmIvWvQo8L6StA0jGvlNLGsF s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhQFAH8O4FGtJXG9/2dsb2JhbABagwY0T8FRgQkWdIIjAQEBAwEBAQEaHTQLBQcGAQgOAwQBAQsUCS4LFAkJAQQOBQiIAQYMtyaPMDENgwVsA5kFkCSDEoIo
X-IronPort-AV: E=Sophos;i="4.89,653,1367971200"; d="scan'208";a="234058267"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-5.cisco.com with ESMTP; 12 Jul 2013 14:13:46 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r6CEDj03014717 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 12 Jul 2013 14:13:45 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.56]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.02.0318.004; Fri, 12 Jul 2013 09:13:45 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Thread-Topic: [dhcwg] WGLC - draft-ietf-dhc-option-guidelines-12 - Respond by July 15
Thread-Index: Ac5/CeXs+iBdFB2RQ1KzXVvxbBOdyQ==
Date: Fri, 12 Jul 2013 14:13:43 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E185E06E8@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.86.255.139]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC - draft-ietf-dhc-option-guidelines-12 - Respond by July 15
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: Fri, 12 Jul 2013 14:13:51 -0000

Fragment type is one of the 'basic' option formats in section 5. You can put these together to build new options that still meet the requirements (though in some cases that requires additional length fields). Perhaps this is one area that needs a bit more clarity? (I think I would have said one can build structured options using the basic option formats in section 5 as the data elements, perhaps with additional (2-octet) length fields where appropriate.)

Yes, RFC 2131 (and perhaps 2132) should be in the Informative References as "DHCPv4" is mentioned several times. First of these (at least) should be linked to the reference (looks to be in section 9).

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of Ralph Droms
Sent: Thursday, July 11, 2013 3:56 PM
To: Bernie Volz (volz)
Cc: dhcwg@ietf.org WG
Subject: Re: [dhcwg] WGLC - draft-ietf-dhc-option-guidelines-12 - Respond by July 15

Looks about ready to publish.  Some comments:

Title of section 10: "Additional States Considered Harmful"  I suggest s/States/State/.  At first, I thought this referred to client states as in DHCPv4.  The text in section 10 clearly refers to state added to the various kinds of state the server maintains to manage clients.

In section 13, what is a "fragment type"?  The word fragment appears (once) previously in section 5, but I don't have a clue what a "fragment type" might be.

Add citations to RFC 2131 and RFC 2132 for the references to DHCPv4?

- Ralph

On Jul 1, 2013, at 5:44 PM 7/1/13, Bernie Volz (volz) <volz@cisco.com> wrote:

> The draft-ietf-dhc-option-guidelines-12, http://tools.ietf.org/html/draft-ietf-dhc-option-guidelines-12, addresses the comments from the previous (-11) last call. While originally I expected to have a short (1 week) last call for the updated document, I think it best to have the standard 2 weeks given the time of year (and the Independence Day holiday in the US).
>  
> Please review the draft and indicate whether or not you feel this version is ready to be published. Your response matters to the process, so please do respond.
>  
> Do note: While I encourage full reviews, the main focus is to assure we have consensus on the recent changes from the -11. The -11 WGLC support will be taken into consideration.
>  
> As Tomek is an author, I will evaluate consensus after July 15, 2013.
>  
> -          Bernie
>  
> _______________________________________________
> 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