BCP 153, RFC 6598 on IANA-Reserved IPv4 Prefix for Shared Address Space

rfc-editor@rfc-editor.org Fri, 20 April 2012 23:20 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 7F12721F8419 for <ietf-announce@ietfa.amsl.com>; Fri, 20 Apr 2012 16:20:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.56
X-Spam-Status: No, score=-104.56 tagged_above=-999 required=5 tests=[AWL=1.117, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 75bQHeHkfMBb for <ietf-announce@ietfa.amsl.com>; Fri, 20 Apr 2012 16:20:43 -0700 (PDT)
Received: from rfc-editor.org (rfcpa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 7872E21F8466 for <ietf-announce@ietf.org>; Fri, 20 Apr 2012 16:20:42 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id DEB32B1E017; Fri, 20 Apr 2012 16:19:32 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 153, RFC 6598 on IANA-Reserved IPv4 Prefix for Shared Address Space
From: rfc-editor@rfc-editor.org
Message-Id: <20120420231932.DEB32B1E017@rfc-editor.org>
Date: Fri, 20 Apr 2012 16:19:32 -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: Fri, 20 Apr 2012 23:20:44 -0000

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

        BCP 153        
        RFC 6598

        Title:      IANA-Reserved IPv4 Prefix for Shared 
                    Address Space 
        Author:     J. Weil, V. Kuarsingh,
                    C. Donley, C. Liljenstolpe,
                    M. Azinger
        Status:     Best Current Practice
        Stream:     IETF
        Date:       April 2012
        Mailbox:    jason.weil@twcable.com, 
        Pages:      11
        Characters: 22055
        Updates:    RFC5735
        See Also:   BCP00153

        I-D Tag:    draft-weil-shared-transition-space-request-15.txt

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

This document requests the allocation of an IPv4 /10 address block to
be used as Shared Address Space to accommodate the needs of Carrier-
Grade NAT (CGN) devices.  It is anticipated that Service Providers
will use this Shared Address Space to number the interfaces that
connect CGN devices to Customer Premises Equipment (CPE).

Shared Address Space is distinct from RFC 1918 private address space
because it is intended for use on Service Provider networks.
However, it may be used in a manner similar to RFC 1918 private
address space on routing equipment that is able to do address
translation across router interfaces when the addresses are identical
on two different interfaces.  Details are provided in the text of
this document.

This document details the allocation of an additional special-use
IPv4 address block and updates RFC 5735.  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

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