Re: [Idr] new revision of private use ASN reservation draft

Randy Bush <randy@psg.com> Mon, 20 August 2012 14:22 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 978AE21F85C6 for <idr@ietfa.amsl.com>; Mon, 20 Aug 2012 07:22:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.547
X-Spam-Level:
X-Spam-Status: No, score=-2.547 tagged_above=-999 required=5 tests=[AWL=0.052, BAYES_00=-2.599]
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 YUYF1R5lQ7z5 for <idr@ietfa.amsl.com>; Mon, 20 Aug 2012 07:22:40 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 3821721F85B4 for <idr@ietf.org>; Mon, 20 Aug 2012 07:22:40 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80 (FreeBSD)) (envelope-from <randy@psg.com>) id 1T3SsG-000P0m-KA; Mon, 20 Aug 2012 14:22:36 +0000
Date: Mon, 20 Aug 2012 23:22:56 +0900
Message-ID: <m2ehn1r6bj.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Jon Mitchell <jrmitche@puck.nether.net>
In-Reply-To: <20120820141118.GA13367@puck.nether.net>
References: <20120806203338.GA14475@puck.nether.net> <502034DB.6000703@umn.edu> <20120820141118.GA13367@puck.nether.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Cc: idr@ietf.org
Subject: Re: [Idr] new revision of private use ASN reservation draft
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: Mon, 20 Aug 2012 14:22:40 -0000

>> "If private use ASNs are used between cooperating operators, special
>> attention should be given to ensuring uniqueness of the private use
>> ASNs between the operators. The use of the newer, numerically higher
>> range of private use ASNs is recommended for such cooperative use
>> between multiple operators, its significantly larger size allows the
>> coordination of large ranges for each cooperating operator,
>> simplifying "
> 
> Although in many cases, we know that these situations are a reality,
> I'm a bit concerned about the language here as it might encourage such
> use or mis-use of private ASN's that both Chris and Randy were
> concerned with, and boundary (public) ASN's or other approaches maybe
> better approaches to solve this problem depending on the specific use
> case.  Secondly, the above seems to imply that using the newer range
> is preferred, when in reality many other approaches as long as they
> were coordinated would work (one use older range, one use newer range,
> centralized database/registry, etc...).

let's be honest here.  what is being said is that this is really a new
public space with ad hoc assignment and recording.  we already have a
centralized database, we should use it.

randy