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

Randy Bush <randy@psg.com> Wed, 04 July 2012 00:12 UTC

Return-Path: <randy@psg.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 1D73311E80B7 for <idr@ietfa.amsl.com>; Tue, 3 Jul 2012 17:12:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level:
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599]
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 BILbBNBDOj68 for <idr@ietfa.amsl.com>; Tue, 3 Jul 2012 17:12:15 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id A7E2511E80A5 for <idr@ietf.org>; Tue, 3 Jul 2012 17:12:15 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SmDCe-0000x6-G4; Wed, 04 Jul 2012 00:12:21 +0000
Date: Wed, 04 Jul 2012 09:12:04 +0900
Message-ID: <m2wr2k2xm3.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: David Farmer <farmer@umn.edu>
In-Reply-To: <4FF350D3.2030205@umn.edu>
References: <20120702164834.GB13713@puck.nether.net> <m2zk7hxli9.wl%randy@psg.com> <20120703141629.GC22598@puck.nether.net> <CAL9jLaa0Q6Zwrce8cxYY_VtDOsnjdQF6gG+bEC3T4LZbJYuZ7w@mail.gmail.com> <4FF350D3.2030205@umn.edu>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="US-ASCII"
Cc: idr@ietf.org
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: Wed, 04 Jul 2012 00:12:17 -0000

> So Chris, why does clothing store with 1.5k endsites want those ASNs 
> publicly registered.  I tend toward why not, but they frequently seem to 
> not want them publicly registered.  They clam it has something to do 
> with security.  I don't buy it, but on the other had it is their
> network.

it's the public's resource

> A lot of enterprise networks are starting to use BGP internally, but 
> they seems to only want to deal with eBGP and no iBGP peerings or only 
> very limited iBGP.  So they give every router or pair of site routers 
> its own Private ASN.  I seen some with fairly elaborate routing policy, 
> that would qualify as unique routing policy.  But many don't they just 
> used Private ASN to avoid iBGP, without any unique routing policy.

i see lots of silly things.  i am not inclined to change to world to
accommodate them.

> But using an ASN so you don't have to deal with iBGP isn't justified by 
> the unique routing policy criteria of RFC 1930.

or by good design practice

randy