IETF Logo Mail Archive

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

Warren Kumari <warren@kumari.net> Wed, 12 December 2012 19:11 UTC

Return-Path: <warren@kumari.net>
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 A0BCE21E80F4 for <idr@ietfa.amsl.com>; Wed, 12 Dec 2012 11:11:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 DHMS13gGictx for <idr@ietfa.amsl.com>; Wed, 12 Dec 2012 11:11:21 -0800 (PST)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F04B21E808D for <idr@ietf.org>; Wed, 12 Dec 2012 11:11:21 -0800 (PST)
Received: from [192.168.1.38] (unknown [66.84.81.123]) by vimes.kumari.net (Postfix) with ESMTPSA id A3F061B405DE; Wed, 12 Dec 2012 14:11:20 -0500 (EST)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <CA+b+ERn4OM3BLbn90w74mrP_DsUb3-dUJc87LqtpJWhuFOLivg@mail.gmail.com>
Date: Wed, 12 Dec 2012 14:11:20 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <FA7751F7-820B-41E4-AB56-BAB9D44BB353@kumari.net>
References: <CA+b+ERnuWZ+r2O-eFhe3hU00uoU4UKnRcbhLNVXU7p5+DjoWbQ@mail.gmail.com> <C6C16AE3B7961044B04A1BCEC6E2F93603D12A0C@xmb-rcd-x14.cisco.com> <20121210225858.GC24937@puck.nether.net> <m2d2yh32cw.wl%randy@psg.com> <CA+b+ERnSVvewSpftXs3FhW12-S+sgnB1SwD4L+xqFW+hhbQayw@mail.gmail.com> <7120600D-71BD-4E61-8F06-25B7C2BAE6A8@riw.us> <20121211185917.GA21813@puck.nether.net> <CA+b+ERnzo2BLWjE1J_dMfYuExbG9WYJroPE4ZAWg++KK2_jy1g@mail.gmail.com> <CA+b+ERm=Agr7b6JXcXOwiP4wBjnEFmnVNt5fAJrn18R0hGtSzg@mail.gmail.com> <50C78C29.3070406@foobar.org> <50C8B8D9.4090903@umn.edu> <50C8C491.4040705@foobar.org> <CAH1iCiqfZRLv2pBEg3gKxT=ZXf7AXCPJ_+QibOpgeFfOuqFK7g@mail.gmail.com> <50C8CE86.10103@umn.edu> <50C8CF69.4070202@foobar.org> <CA+b+ER=tp+tdmNomjAXpaRBG8cYNo1SybAr1WoJ9frBUSGoOrg@mail.gmail.com> <CAL9jLaaenLrpG7Rw2N2+CpBXmazS+tufa_2UZAHJT-GOn580Fw@mail.gmail.com> <CA+b+ERn4OM3BLbn90w74mrP_DsUb3-dUJc87LqtpJWhuFOLivg@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
X-Mailer: Apple Mail (2.1499)
Cc: IETF IDR Working Group <idr@ietf.org>
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: Wed, 12 Dec 2012 19:11:22 -0000

On Dec 12, 2012, at 2:01 PM, Robert Raszuk <robert@raszuk.net> wrote:

> Chris,
> 
> Do you expect that folks will use the new space as soon as it is out
> of RFC editor ?

Who knows...

> Is there such huge demand for it among ISPs or
> DSL/FTTH/CABLE operators ;) ?

Who know...

> 
> And if so do you really assume those who will use it are so stupid
> that they would leak those ?

Oh Gods yes. Maybe not stupid, but accidents *will* happen.

But, if there is not a "reserved" range, folk are likely to just squat on some numbers and will be as (or more likely) to leak this… 

If this is a reserved range at least external folk can more easily see that this is a leak, and isn't as likely to end up as path poisoning a legitimate AS.

> I think 4 octet AS itself is not that
> widely deployed yet. Yes I saw your mail on few two octet private as
> leaked.
> 
> And if those are leaked do you think transits should just blindly
> remove those and replace those private ASes with their own AS ?

They could just drop them :-P (evil giggle, runs away…)

> Note
> last time I checked it is not easy to remove private-as from AS_PATH
> other then replacing it with your own when the UPDATE crossed few
> hops.
> 
> rgs,
> r.
> 
> On Wed, Dec 12, 2012 at 7:48 PM, Christopher Morrow
> <morrowc.lists@gmail.com> wrote:
>> On Wed, Dec 12, 2012 at 1:43 PM, Robert Raszuk <robert@raszuk.net> wrote:
>>> Are you putting this regex in today ?
>>> 
>>> Otherwise the sooner this goes through your vendors will be able to
>>> provide you one keyword match for the new private AS range in the
>>> policy language of your choice.
>>> 
>>> So I can't quite see what's the point of this regex debate now ....
>> 
>> to rephrase, I think Robert is asking: "Would you not just ask your
>> vendor to include a macro like: 'PrivateASNGroup' to match on in
>> routing policy language?"
>> 
>> seems reasonable... except that my SFO router may not get upgraded at
>> the same as my NYC router, nevermind fast-mover Nick over there who's
>> always happy to load nightly code on his elbonian routers... so do we
>> have to delay usage of this new shiny space until reasonably close to
>> all public bgp speakers upgrade? Or build a mechanism like AS4
>> required for as2 only realms stuck in the middle of the AS4 world?
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
> 

-- 
A. No
Q. Is it sensible to top-post?

v2.31.3 | Report a Bug | By Email | System Status