Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP

The IESG <iesg-secretary@ietf.org> Mon, 30 January 2012 23:03 UTC

Return-Path: <iesg-secretary@ietf.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 DE17311E80D7 for <ietf-announce@ietfa.amsl.com>; Mon, 30 Jan 2012 15:03:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.543
X-Spam-Level:
X-Spam-Status: No, score=-102.543 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Kedk9wP6-h7 for <ietf-announce@ietfa.amsl.com>; Mon, 30 Jan 2012 15:03:32 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6340821F875B for <ietf-announce@ietf.org>; Mon, 30 Jan 2012 15:03:32 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20120130230332.4239.59749.idtracker@ietfa.amsl.com>
Date: Mon, 30 Jan 2012 15:03:32 -0800
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
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: Mon, 30 Jan 2012 23:03:33 -0000

The IESG has received a request from an individual submitter to consider the following document:
- 'IANA Reserved IPv4 Prefix for Shared CGN Space'
 <draft-weil-shared-transition-space-request-14.txt> as a BCP

On its December 15, 2011 telechat, the IESG reviewed version 10 of this 
document and requested various changes. These changes are reflected in 
the draft version 14 and the IESG now solicits community input on the 
changed text only. Please send substantive comments to the ietf@ietf.org 
mailing lists by 2012-02-16. Exceptionally, comments may be sent to 
iesg@ietf.org instead. In either case, please retain the beginning of 
the Subject line to allow automated sorting.

Abstract

  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 Network Address Translation (CGN) devices.  It is anticipated
  that Service Providers will use this Shared Address Space to number
  the interfaces that connect CGN devices to Customer Premise Equipment
  (CPE).

  Shared Address Space is distinct from RFC1918 private address space
  because it is intended for use on Service Provider networks.
  However, it may be used as RFC 1918 private address space in certain
  circumstances.  Details are provided in the text of this document.

  As this document proposes the allocation of an additional special-use
  IPv4 address block, it updates RFC 5735.

The following text captures the most salient change between version 10 and 14 of this document:

  Shared Address Space is IPv4 address space designated for Service
     Provider use with the purpose of facilitating CGN deployment.  Also,
     Shared Address Space can be used as additional [RFC1918] space when
     at least one of the following conditions is true:

     o  Shared Address Space is not also used on the Service Provider side
        of the CPE.

     o  CPE routers behave correctly when using the same address block on
        both the internal and external interfaces.


The file can be obtained via
http://datatracker.ietf.org/doc/draft-weil-shared-transition-space-request/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-weil-shared-transition-space-request/


No IPR declarations have been submitted directly on this I-D.