Re: [dhcwg] DHCP impacts from draft-arkko-arp-iana-rules
"Bernie Volz (volz)" <volz@cisco.com> Mon, 01 December 2008 23:03 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 BFD7528C0F9; Mon, 1 Dec 2008 15:03:04 -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 1CBD428C127 for <dhcwg@core3.amsl.com>; Mon, 1 Dec 2008 15:03:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 yLHSKbwfN5YN for <dhcwg@core3.amsl.com>; Mon, 1 Dec 2008 15:03:02 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id CEB7328C0EA for <dhcwg@ietf.org>; Mon, 1 Dec 2008 15:03:01 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,698,1220227200"; d="scan'208";a="29620822"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 01 Dec 2008 23:02:57 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id mB1N2vnr018766; Mon, 1 Dec 2008 18:02:57 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id mB1N2tCO004480; Mon, 1 Dec 2008 23:02:57 GMT
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 1 Dec 2008 18:02:55 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 01 Dec 2008 18:02:53 -0500
Message-ID: <8E296595B6471A4689555D5D725EBB2109C80E14@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <4934570E.1010305@piuha.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dhcwg] DHCP impacts from draft-arkko-arp-iana-rules
Thread-Index: AclT/viCAdMoK9gmTzSVDz9vV316dQACaXqg
References: <4934570E.1010305@piuha.net>
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Jari Arkko <jari.arkko@piuha.net>, Dhcwg <dhcwg@ietf.org>
X-OriginalArrivalTime: 01 Dec 2008 23:02:55.0785 (UTC) FILETIME=[F2450190:01C95408]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3037; t=1228172577; x=1229036577; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=volz@cisco.com; z=From:=20=22Bernie=20Volz=20(volz)=22=20<volz@cisco.com> |Subject:=20RE=3A=20[dhcwg]=20DHCP=20impacts=20from=20draft -arkko-arp-iana-rules |Sender:=20 |To:=20=22Jari=20Arkko=22=20<jari.arkko@piuha.net>,=20=22Dh cwg=22=20<dhcwg@ietf.org>; bh=cs5KEXrr2/twSPdvksvxY13oxCgypKGki58Y4kDbrFo=; b=VhbARpDwvLZ3MIkDn1jh1NywXRWJF5CjuIa5hGRm7pDRVsFg79F6COYnW7 Zol1pN/T5cpdwfAGqXUeq97dObiOVU7+94TdlURWkspQpqu82nYIaaCjtE/y BZrRVAQm0I;
Authentication-Results: rtp-dkim-1; header.From=volz@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
Cc: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, Russ Housley <housley@vigilsec.com>
Subject: Re: [dhcwg] DHCP impacts from draft-arkko-arp-iana-rules
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
Hum ... Didn't realize this was such a problem. There's no issue that I can see with DHCPv4 - you've addressed the 1-octet issue for future assignments because of the limit on the htype field. For DHCPv6, there is no issue as it has a 2-octet field. Thus, draft looks OK to me. - Bernie -----Original Message----- From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of Jari Arkko Sent: Monday, December 01, 2008 4:29 PM To: Dhcwg Cc: Carlos Pignataro (cpignata); Russ Housley Subject: [dhcwg] DHCP impacts from draft-arkko-arp-iana-rules Folks, I recently wrote a draft about the IANA rules regarding ARP, as no such rules were defined before. During last call, it became apparent that there are a few other protocols that use the same numbers. For instance, specialized forms of ARP for certain link layers or DHCPv4/6. Having realized this, we did a more thorough search of the RFC series to attempt to find all such uses. The new version of my draft lists all these uses and updates the RFCs in question. I would like to ask for your review to make sure (a) that the ARP rule change is OK from the perspective of your protocol and (b) we have found all uses of the ARP numbers. Here's what the draft says: "The change is also applicable to extensions of ARP that use the same message format, such as [RFC0903], [RFC1931], and [RFC2390]. The change also affects other protocols that employ values from the ARP name spaces. For instance, the ARP hardware address type (ar$hrd) number space is also used in the "htype" (hardware address type) fields in Bootstrap Protocol (BOOTP) [RFC0951] and Dynamic Host Configuration Protocol (DHCP) [RFC2131], as well as in the "hardware type" field in the DHCP Unique Identifiers in DHCPv6 [RFC3315]. These protocols are therefore affected by the update in the IANA rules. Other affected specifications include the specialized address resolution mechanisms in HYPERchannel [RFC1044], DHCP options [RFC2132], [RFC4361], ATM (Asynchronous Transfer Mode) ARP [RFC2225], HARP (High-Performance Parallel Interface ARP) [RFC2834], [RFC2835], Dual MAC FDDI (Fiber Distributed Data Interface) ARP [RFC1329], MAPOS (Multiple Access Protocol over Synchronous Optical Network/Synchronous Digital Hierarchy) ARP [RFC2176], FC (Fibre Channel) ARP [RFC4338], and DNS Resource Records [RFC4701]." (We have only listed a protocol as affected when uses ARP values directly, e.g., in its own protocol message formats. Use of ARP as-is is of course not an issue. I have also not listed the many IP over Foo specifications that talk about how to use ARP in Foo, describing what hardware type values to use, etc.) Here's the URL for the draft: http://tools.ietf.org/html/draft-arkko-arp-iana-rules-04 Jari _______________________________________________ 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
- [dhcwg] DHCP impacts from draft-arkko-arp-iana-ru… Jari Arkko
- Re: [dhcwg] DHCP impacts from draft-arkko-arp-ian… Bernie Volz (volz)
- Re: [dhcwg] DHCP impacts from draft-arkko-arp-ian… Ralph Droms
- Re: [dhcwg] DHCP impacts from draft-arkko-arp-ian… Jari Arkko