RFC 5494 on IANA Allocation Guidelines for the Address Resolution Protocol (ARP)

rfc-editor@rfc-editor.org Mon, 06 April 2009 23:53 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C3E0C28C13A for <ietf-announce@core3.amsl.com>; Mon, 6 Apr 2009 16:53:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.931
X-Spam-Level:
X-Spam-Status: No, score=-16.931 tagged_above=-999 required=5 tests=[AWL=0.068, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
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 k11MF4mUm1yC for <ietf-announce@core3.amsl.com>; Mon, 6 Apr 2009 16:53:41 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 196EF28C107 for <ietf-announce@ietf.org>; Mon, 6 Apr 2009 16:53:41 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 0B0A5276763; Mon, 6 Apr 2009 16:53:44 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5494 on IANA Allocation Guidelines for the Address Resolution Protocol (ARP)
From: rfc-editor@rfc-editor.org
Message-Id: <20090406235344.0B0A5276763@bosco.isi.edu>
Date: Mon, 06 Apr 2009 16:53:44 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2009 23:53:41 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5494

        Title:      IANA Allocation Guidelines for the 
                    Address Resolution Protocol (ARP) 
        Author:     J. Arkko, C. Pignataro
        Status:     Standards Track
        Date:       April 2009
        Mailbox:    jari.arkko@piuha.net, 
                    cpignata@cisco.com
        Pages:      7
        Characters: 11894
        Updates:    RFC826, RFC951, RFC1044, RFC1329, RFC2131, RFC2132, 
                    RFC2176, RFC2225, RFC2834, RFC2835, RFC3315, RFC4338,  
                    RFC4361, RFC4701

        I-D Tag:    draft-arkko-arp-iana-rules-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5494.txt

This document specifies the IANA guidelines for allocating new values
in the Address Resolution Protocol (ARP).  This document also
reserves some numbers for experimentation purposes.  The changes also
affect other protocols that employ values from the ARP name spaces.  
[STANDARDS TRACK]

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute