Re: [Idr] new ID on expansion of private use ASN range

"UTTARO, JAMES" <ju1738@att.com> Tue, 03 July 2012 01:45 UTC

Return-Path: <ju1738@att.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2F7721F85C0 for <idr@ietfa.amsl.com>; Mon, 2 Jul 2012 18:45:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.051
X-Spam-Level:
X-Spam-Status: No, score=-106.051 tagged_above=-999 required=5 tests=[AWL=-0.052, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, 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 wTJGr1Igz3Uy for <idr@ietfa.amsl.com>; Mon, 2 Jul 2012 18:45:04 -0700 (PDT)
Received: from nbfkord-smmo06.seg.att.com (nbfkord-smmo06.seg.att.com [209.65.160.94]) by ietfa.amsl.com (Postfix) with ESMTP id C3A8621F85B6 for <idr@ietf.org>; Mon, 2 Jul 2012 18:45:03 -0700 (PDT)
Received: from unknown [144.160.128.153] (EHLO flpi408.enaf.ffdc.sbc.com) by nbfkord-smmo06.seg.att.com(mxl_mta-6.11.0-10) over TLS secured channel with ESMTP id 5ae42ff4.0.423095.00-408.1155414.nbfkord-smmo06.seg.att.com (envelope-from <ju1738@att.com>); Tue, 03 Jul 2012 01:45:10 +0000 (UTC)
X-MXL-Hash: 4ff24ea66bb08a9e-ad6882353c42d822ecb0899fef41124745de0f20
Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id q631j9dn022992; Mon, 2 Jul 2012 18:45:09 -0700
Received: from fflint04.pst.cso.att.com (fflint04.pst.cso.att.com [150.234.39.64]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id q631j0Me022891 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 2 Jul 2012 18:45:01 -0700
Received: from MISOUT7MSGHUB9E.ITServices.sbc.com (misout7msghub9e.itservices.sbc.com [144.151.223.61]) by fflint04.pst.cso.att.com (RSA Interceptor); Mon, 2 Jul 2012 18:44:42 -0700
Received: from MISOUT7MSGUSR9I.ITServices.sbc.com ([144.151.223.56]) by MISOUT7MSGHUB9E.ITServices.sbc.com ([144.151.223.61]) with mapi id 14.02.0298.004; Mon, 2 Jul 2012 21:44:42 -0400
From: "UTTARO, JAMES" <ju1738@att.com>
To: 'Jon Mitchell' <jrmitche@puck.nether.net>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] new ID on expansion of private use ASN range
Thread-Index: AQHNWHKljC8TDxs8cE6jyZJb6lmEx5cWx/CA
Date: Tue, 03 Jul 2012 01:44:42 +0000
Message-ID: <B17A6910EEDD1F45980687268941550FB31543@MISOUT7MSGUSR9I.ITServices.sbc.com>
References: <20120702164834.GB13713@puck.nether.net>
In-Reply-To: <20120702164834.GB13713@puck.nether.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.70.21.94]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <ju1738@att.com>
X-SOURCE-IP: [144.160.128.153]
X-AnalysisOut: [v=1.0 c=1 a=bvJ_HHhP4N4A:10 a=RWSgesl4Y2gA:10 a=ofMgfj31e3]
X-AnalysisOut: [cA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=xwOvzTHDVLE4u4]
X-AnalysisOut: [nGvK72ag==:17 a=48vgC7mUAAAA:8 a=6H-FyMtOVf_CPohR60AA:9 a=]
X-AnalysisOut: [CjuIK1q_8ugA:10 a=lZB815dzVvQA:10 a=H7Wc3F33PO4uAkdZ:21 a=]
X-AnalysisOut: [D2ZdFx-yW8Rorb4f:21]
Subject: Re: [Idr] new ID on expansion of private use ASN range
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jul 2012 01:45:04 -0000

Jon,

	Seems reasonable.. I do not fully get the context.. You describe the fact that the increase in the number of AS across both l3VPN and Internet use cases are expanding rapidly.. No Doubt... So I see the creation of the new spaces and ranges.. My concerns are in re the Operations Considerations Section

a) You are creating a set of rules for the internet routing context.

"  If private use ASNs are used and prefixes are originated from these
   private use ASNs which are destined to the Internet, private use ASNs
   must be removed from the AS_PATH before being advertised to the
   global Internet.
"
How does this effect folks who use AS_PATH and/or AS_CONTENT in routing policy decisions? Better question is there an issue if all of the Private ASNs are stripped?

b) You specify no rules in re the L3VPN routing context(s). 

c) Not sure how this would work? If someone screws up what is the collateral damage?

"  Prior to making use of the second, numerically
   higher, range of these ASNs network operators should be confident any
   implementation specific features or filters that recognize private
   use ASNs have been updated to recognize both ranges correctly so that
   no unintended announcement of private use ASNs to the Internet
"

Thanks,
	Jim Uttaro


-----Original Message-----
From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On Behalf Of Jon Mitchell
Sent: Monday, July 02, 2012 12:49 PM
To: idr@ietf.org
Subject: [Idr] new ID on expansion of private use ASN range


IDR WG folks -

I hope you can take some time from the normal debate(s) to consider and
review a fresh draft on expanding the ASN space reserved for Private
Use.  All comments regarding content, clarity or structure welcome.

Cheers,

Jon

--

A new version of I-D, draft-mitchell-idr-as-private-reservation-00.txt
has been successfully submitted by Jon Mitchell and posted to the IETF
repository.

Filename:        draft-mitchell-idr-as-private-reservation
Revision:        00
Title:           Autonomous System (AS) Reservation for Private Use
Creation date:   2012-06-20
WG ID:           Individual Submission
Number of pages: 4
URL:
http://www.ietf.org/internet-drafts/draft-mitchell-idr-as-private-reservation-00.txt
Status:
http://datatracker.ietf.org/doc/draft-mitchell-idr-as-private-reservation
Htmlized:
http://tools.ietf.org/html/draft-mitchell-idr-as-private-reservation-00


Abstract:
   This document describes the reservation of Autonomous System numbers
   (ASNs) that may be used within networks but should not be advertised
   to the Internet, known as private use ASNs.  This document enlarges
   the total space available for private use ASNs by documenting the
   reservation of a second larger range and updates RFC 1930.

                                                                                  


The IETF Secretariat

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr