BCP 153, RFC 5735 on Special Use IPv4 Addresses

RFC Editor <rfc-editor@rfc-editor.org> Tue, 19 January 2010 18:56 UTC

Return-Path: <rfc-ed@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 B998828C14A for <ietf-announce@core3.amsl.com>; Tue, 19 Jan 2010 10:56:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.422
X-Spam-Level:
X-Spam-Status: No, score=-2.422 tagged_above=-999 required=5 tests=[AWL=0.178, BAYES_00=-2.599, NO_RELAYS=-0.001]
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 v3zaD854L2V3 for <ietf-announce@core3.amsl.com>; Tue, 19 Jan 2010 10:56:54 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id C86A828C0F4 for <ietf-announce@ietf.org>; Tue, 19 Jan 2010 10:56:54 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 6000) id 90A49E0686; Tue, 19 Jan 2010 10:56:51 -0800 (PST)
Date: Tue, 19 Jan 2010 10:56:51 -0800
From: RFC Editor <rfc-editor@rfc-editor.org>
To: ietf-announce@ietf.org
Subject: BCP 153, RFC 5735 on Special Use IPv4 Addresses
Message-ID: <20100119185651.GP14300@rfc-editor.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.17 (2007-11-01)
Cc: RFC Editor <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: Tue, 19 Jan 2010 18:56:55 -0000

Resending.

----- Forwarded message from rfc-editor@rfc-editor.org -----

To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 153, RFC 5735 on Special Use IPv4 Addresses
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, iana@iana.org
Date: Thu, 14 Jan 2010 23:10:08 -0800 (PST)


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

        BCP 153        
        RFC 5735

        Title:      Special Use IPv4 Addresses 
        Author:     M. Cotton, L. Vegoda
        Status:     Best Current Practice
        Date:       January 2010
        Mailbox:    michelle.cotton@icann.org, 
                    leo.vegoda@icann.org
        Pages:      10
        Characters: 20369
        Obsoletes:  RFC3330
        See Also:   BCP0153

        I-D Tag:    draft-iana-rfc3330bis-11.txt

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

This document obsoletes RFC 3330.  It describes the global and other
specialized IPv4 address blocks that have been assigned by the
Internet Assigned Numbers Authority (IANA).  It does not address IPv4
address space assigned to operators and users through the Regional
Internet Registries, nor does it address IPv4 address space assigned
directly by IANA prior to the creation of the Regional Internet
Registries.  It also does not address allocations or assignments of
IPv6 addresses or autonomous system numbers.  This memo documents an 
Internet Best Current Practice.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. 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
Association Management Solutions, LLC


----- End forwarded message -----