RFC 6319 on Issues Associated with Designating Additional Private IPv4 Address Space

rfc-editor@rfc-editor.org Tue, 19 July 2011 23:48 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B76721F84DC for <ietf-announce@ietfa.amsl.com>; Tue, 19 Jul 2011 16:48:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.447
X-Spam-Level:
X-Spam-Status: No, score=-102.447 tagged_above=-999 required=5 tests=[AWL=0.153, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0epRJlA-h+o1 for <ietf-announce@ietfa.amsl.com>; Tue, 19 Jul 2011 16:48:00 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id 6FE0421F84D8 for <ietf-announce@ietf.org>; Tue, 19 Jul 2011 16:48:00 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 65EA198C518; Tue, 19 Jul 2011 16:48:00 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6319 on Issues Associated with Designating Additional Private IPv4 Address Space
From: rfc-editor@rfc-editor.org
Message-Id: <20110719234800.65EA198C518@rfc-editor.org>
Date: Tue, 19 Jul 2011 16:48:00 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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 Jul 2011 23:48:01 -0000

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

        
        RFC 6319

        Title:      Issues Associated with Designating Additional 
                    Private IPv4 Address Space 
        Author:     M. Azinger, L. Vegoda
        Status:     Informational
        Stream:     IETF
        Date:       July 2011
        Mailbox:    marla.azinger@ftr.com, 
                    leo.vegoda@icann.org
        Pages:      12
        Characters: 26939
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-azinger-additional-private-ipv4-space-issues-05.txt

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

When a private network or internetwork grows very large, it is
sometimes not possible to address all interfaces using private IPv4
address space because there are not enough addresses.  This document
describes the problems faced by those networks, the available
options, and the issues involved in assigning a new block of private
IPv4 address space.

While this informational document does not make a recommendation for
action, it documents the issues surrounding the various options that
have been considered.  This document is not an Internet Standards Track 
specification; it is published for informational purposes.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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