Re: [Idr] WGLC on draft-ietf-idr-as-private-reservation-00

Tony Li <tony.li@tony.li> Sat, 01 December 2012 01:03 UTC

Return-Path: <tony.li@tony.li>
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 DAA6F21F89A7 for <idr@ietfa.amsl.com>; Fri, 30 Nov 2012 17:03:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level:
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 aEZYkIVAOibo for <idr@ietfa.amsl.com>; Fri, 30 Nov 2012 17:03:01 -0800 (PST)
Received: from qmta13.emeryville.ca.mail.comcast.net (qmta13.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:243]) by ietfa.amsl.com (Postfix) with ESMTP id 6A41121F884F for <idr@ietf.org>; Fri, 30 Nov 2012 17:03:01 -0800 (PST)
Received: from omta22.emeryville.ca.mail.comcast.net ([76.96.30.89]) by qmta13.emeryville.ca.mail.comcast.net with comcast id VuVQ1k0081vN32cAD131Kc; Sat, 01 Dec 2012 01:03:01 +0000
Received: from [10.155.35.198] ([128.107.239.234]) by omta22.emeryville.ca.mail.comcast.net with comcast id W10l1k002547xYo8i10nkk; Sat, 01 Dec 2012 01:00:59 +0000
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Tony Li <tony.li@tony.li>
In-Reply-To: <m2pq2uzl2i.wl%randy@psg.com>
Date: Fri, 30 Nov 2012 17:00:44 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <FCB6E858-F190-46AF-8BA5-F4C92F590505@tony.li>
References: <B6B72499-E9D0-4281-84EB-6CA53694866E@juniper.net> <D704E7E3-3A95-4696-9757-9E17605E670C@tony.li> <378E396E-3F4B-4ACC-83D1-C4931524FECD@puck.nether.net> <CA+b+ERneavhy1gzKRSnCfN+YjYcU0+3WgBg6f68gq=tpx8yV5g@mail.gmail.com> <1AC79BDA-C088-47B4-888D-4B0428FB7C4F@puck.nether.net> <B549F708-0D5E-4B22-AC91-B6CE61B258FE@tony.li> <CAL9jLaZdX_jem0JdSGHzuhc3GDZXMDR0kvMKq5xr3D-EWYbNVQ@mail.gmail.com> <CA+b+ER=rL6WAMuu5cJUQk94ObUrhKKgmiNuxRhMGJbavCg6S3A@mail.gmail.com> <CAL9jLaa27PZwa+fj_okSHTjjnxQeR8q67Nb5V0aYKOBbqcHtjQ@mail.gmail.com> <CA+b+ERnBAOU5sbtjnPcfzmw2ieu7UPEXWbGCpsY=5hcfSUToFg@mail.gmail.com> <CAL9jLab4WZa-QA2pwhD7cuCk8iNca3xSUeJkQDxJyy4dS37WSg@mail.gmail.com> <9DCD1872-F11D-4B08-9B0B-834C05D7D0FF@tony.li> <m2pq2uzl2i.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1499)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1354323781; bh=ZEgR8S8hQQnwPZiOVXa15X5fL9s5baMyTbMCUhdQZiw=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=AI2iW3sY4jGb43SwBDXxCrYlRm9kuHWk7RBvdfvsVLXMk7/8iKyq2YxqcDD+hGprJ 5SiESHuksH/hqhgyD3VsrI+kIIUv3qUWwLG6n7L86Bou3GILYeBBnJLeI803s4h4h0 NujwayAVUKNTLc5r2RRdgDA5KF2uvS2whasVXsdQ0jsPuLZ8zIM8AWw7cslekqG+dh MWtqDxpq7t5QdbFqwuBwGOZxwBq+aj2OAtJdXzyCz6NHw9vOJRvTHgVM8fGuTp04X1 iUF8CjFLudNMhp8wDowpgA2xCOlVaRvT/FlQT4+AxITAL7QT17Mo4XFMT33r4+ZHcI 2dZQs3CvIw3ww==
Cc: idr wg <idr@ietf.org>, Robert Raszuk <robert@raszuk.net>
Subject: Re: [Idr] WGLC on draft-ietf-idr-as-private-reservation-00
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: Sat, 01 Dec 2012 01:03:02 -0000

On Nov 30, 2012, at 4:13 PM, Randy Bush <randy@psg.com> wrote:

>> There is ample demand for doing this
> 
> in the current world, there is demand for all sorts of things.
> 
> but is there actual need?  i.e. the current widely deployed practice of
> re-using an AS for many customers and applying the 'ignore as loop' hack
> seems to be working well.  what we do not have is that hack formalized.
> i think wes and shane are working on that, but i could be wrong.
> 
>> There is ample demand for doing this, it's simply not represented by
>> the SP community.
> 
> you will note a large number of SPs speaking against this proposal
> 
> randy


Well, let's put it this way: the data center community has, for better or worse, decided that BGP is their protocol of choice.  Frankly, I find it mildly nauseating, but it's very clear that they are going to use BGP regardless of what you and I say.  Yes, there are more than one of them going this way, they are large and well-funded.  It's going to happen.

Now, again, we can block off a range of numbers, or data center folks are going to end up squatting on public ASNs.  And if that happens, we will end up being asked to implement ASN NAT, at which point we can no longer ensure global uniqueness.

<Yakov>
Can we please be practical?
</Yakov>

Tony