Re: [dhcwg] PKIX WG new I-D draft: DHCP section review

Ralph Droms <rdroms@cisco.com> Sat, 06 December 2008 11:35 UTC

Return-Path: <dhcwg-bounces@ietf.org>
X-Original-To: dhcwg-archive@megatron.ietf.org
Delivered-To: ietfarch-dhcwg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BD9DB3A684F; Sat, 6 Dec 2008 03:35:57 -0800 (PST)
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 34B463A6841 for <dhcwg@core3.amsl.com>; Sat, 6 Dec 2008 03:35:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.972
X-Spam-Level:
X-Spam-Status: No, score=-5.972 tagged_above=-999 required=5 tests=[AWL=0.627, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id siFZ+-9JvxG5 for <dhcwg@core3.amsl.com>; Sat, 6 Dec 2008 03:35:55 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 2E3B03A684F for <dhcwg@ietf.org>; Sat, 6 Dec 2008 03:35:55 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,724,1220227200"; d="scan'208";a="30234319"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 06 Dec 2008 11:35:49 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id mB6BZn9j001462; Sat, 6 Dec 2008 06:35:49 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id mB6BZno2029196; Sat, 6 Dec 2008 11:35:49 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 6 Dec 2008 06:35:49 -0500
Received: from bxb-rdroms-8712.cisco.com ([10.98.10.83]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 6 Dec 2008 06:35:48 -0500
Message-Id: <A29FB4BE-EDEC-4BD8-B2A4-DE340BAB6A84@cisco.com>
From: Ralph Droms <rdroms@cisco.com>
To: Massimiliano Pala <Massimiliano.Pala@Dartmouth.edu>
In-Reply-To: <F32C8732-944D-4DB4-9E39-FF4430973C1A@nominum.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sat, 06 Dec 2008 06:35:42 -0500
References: <4935915E.1060708@Dartmouth.edu> <F32C8732-944D-4DB4-9E39-FF4430973C1A@nominum.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 06 Dec 2008 11:35:48.0751 (UTC) FILETIME=[C91B99F0:01C95796]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1214; t=1228563349; x=1229427349; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rdroms@cisco.com; z=From:=20Ralph=20Droms=20<rdroms@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20PKIX=20WG=20new=20I-D=20draft =3A=20DHCP=20section=20review |Sender:=20 |To:=20Massimiliano=20Pala=20<Massimiliano.Pala@Dartmouth.e du>; bh=JlDM6WzSx5NUX2An2rrmKWiVVq1aw0VhyD8QyEe35YI=; b=PxXSt49oblz+/zNaZTiwvnTBMnlokar71/AxGJRSZvNOqIvX/OWfCZH2Yv 3KiD1tcggpi04xxLsY2XawIdAFnUJ9D6LK3LcIKDpD4CeKjMyRKBh/ppFDZS 2NVlOXbi9R;
Authentication-Results: rtp-dkim-2; header.From=rdroms@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
Cc: DHC-WG <dhcwg@ietf.org>, Damien Neil <Damien.Neil@nominum.com>
Subject: Re: [dhcwg] PKIX WG new I-D draft: DHCP section review
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org

I agree with Damien's review.  Take a look at RFC 4280 for an example  
of how to write parallel definitions for an option in DHCPv4 and DHCPv6.

-  Ralph

On Dec 2, 2008, at Dec 2, 2008,3:11 PM, Damien Neil wrote:

> On Dec 2, 2008, at 11:49 AM, Massimiliano Pala wrote:
>>    http://www.ietf.org/internet-drafts/draft-ietf-pkix-prqp-01.txt
>>
>> I would need the expertise from your WG to validate the DHCP part  
>> of the I-D.
>
> At first glance, two issues jump out at me:
>
> Section B.1.1 does not indicate whether the option is for DHCPv4 or  
> DHCPv6.  The option code and length fields are 16 bits wide, which  
> implies DHCPv6, but the examples in subsequent sections imply  
> DHCPv4.  DHCPv4 options encode the option code and length as a  
> single octet each.  (Section B.1.1 also references RFC 3315,  
> implying DHCPv6.)
>
> Section B.1.1 specifies that the option contains a list of DNS  
> names, but the ISC DHCP examples in section B.1.2 are for an option  
> containing a list of IPv4 addresses.
>
>               - Damien
> _______________________________________________
> 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