[Int-area] impacts to other specifications from draft-arkko-arp-iana-rules
Jari Arkko <jari.arkko@piuha.net> Mon, 01 December 2008 21:33 UTC
Return-Path: <int-area-bounces@ietf.org>
X-Original-To: int-area-archive@megatron.ietf.org
Delivered-To: ietfarch-int-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 460173A6A29; Mon, 1 Dec 2008 13:33:47 -0800 (PST)
X-Original-To: int-area@core3.amsl.com
Delivered-To: int-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D70C13A6A29 for <int-area@core3.amsl.com>; Mon, 1 Dec 2008 13:33:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.515
X-Spam-Level:
X-Spam-Status: No, score=-2.515 tagged_above=-999 required=5 tests=[AWL=0.084, BAYES_00=-2.599]
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 lMOY9QvywbVh for <int-area@core3.amsl.com>; Mon, 1 Dec 2008 13:33:45 -0800 (PST)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id B470A3A683D for <int-area@ietf.org>; Mon, 1 Dec 2008 13:33:44 -0800 (PST)
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id 992FF19876B; Mon, 1 Dec 2008 23:33:40 +0200 (EET)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id 3196C198639; Mon, 1 Dec 2008 23:33:40 +0200 (EET)
Message-ID: <49345820.6000207@piuha.net>
Date: Mon, 01 Dec 2008 23:33:20 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.18 (X11/20081125)
MIME-Version: 1.0
To: Internet Area <int-area@ietf.org>
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: Russ Housley <housley@vigilsec.com>
Subject: [Int-area] impacts to other specifications from draft-arkko-arp-iana-rules
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: int-area-bounces@ietf.org
Errors-To: int-area-bounces@ietf.org
Folks, As you recall, 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 _______________________________________________ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
- [Int-area] impacts to other specifications from d… Jari Arkko
- Re: [Int-area] impacts to other specifications fr… Dave Thaler
- Re: [Int-area] impacts to other specifications fr… Donald Eastlake
- Re: [Int-area] impacts to other specifications fr… Jari Arkko