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

Christopher Morrow <morrowc.lists@gmail.com> Fri, 30 November 2012 04:37 UTC

Return-Path: <christopher.morrow@gmail.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 0573321E8039 for <idr@ietfa.amsl.com>; Thu, 29 Nov 2012 20:37:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-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 zlemS+bn41W8 for <idr@ietfa.amsl.com>; Thu, 29 Nov 2012 20:37:56 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0C32121E8037 for <idr@ietf.org>; Thu, 29 Nov 2012 20:37:55 -0800 (PST)
Received: by mail-ee0-f44.google.com with SMTP id b47so32985eek.31 for <idr@ietf.org>; Thu, 29 Nov 2012 20:37:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=NLW8tD2f9c5iR6Y1jTRUOEOtVD4xkRnGVcST74VB8m4=; b=vsNtPxnrNtMSGo4sE2WfAZeRzS1x+5QL37n1OpQ3yoWN8kZyAW3R5Zm6pBEVp+b3vU owH7Z7epSj7aGM3igfuQ356NCWhvvwdRMgMNSLXPKddQSnNBALp15eobmHfV9Lm8L0Gk 8Ve0XlDRTN0tHpNAOowvfjBnqsgvYJFhtm4TAuOO8R/8ceVIv1OBthV+CDbw5FiATD5R 4fmABsv5nO6dmmhpx2FO/NccTTgTUnLNrThbrLMmKks5dQReHC9+xwZeN5u4w9asIyvT 16LFPyFIEyZ977DF+A8XEt5MpuhJjqt16/728bsWCP72WnEXrATrzufDzRhL+ed81F/C pq7A==
MIME-Version: 1.0
Received: by 10.14.194.4 with SMTP id l4mr40984267een.42.1354250274629; Thu, 29 Nov 2012 20:37:54 -0800 (PST)
Sender: christopher.morrow@gmail.com
Received: by 10.223.96.5 with HTTP; Thu, 29 Nov 2012 20:37:54 -0800 (PST)
In-Reply-To: <20121129191043.GA9189@puck.nether.net>
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> <20121129191043.GA9189@puck.nether.net>
Date: Thu, 29 Nov 2012 23:37:54 -0500
X-Google-Sender-Auth: LeNKRG1USaUZiKkPZ46q-oxkrQc
Message-ID: <CAL9jLabFv44WBDbygWTmhL9_H4_eQhmAn_DXjGzLAknhU8SUxQ@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Jon Mitchell <jrmitche@puck.nether.net>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: idr wg <idr@ietf.org>, Tony Li <tony.li@tony.li>, 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: Fri, 30 Nov 2012 04:37:57 -0000

On Thu, Nov 29, 2012 at 2:10 PM, Jon Mitchell <jrmitche@puck.nether.net> wrote:
>
> As I've stated before, mis-configuration or improper use of private use
> ASNs doesn't seem to be highly correlated to the size of the range.  If

agreed.

> this were an issue, I guess, we would expect that a network would be
> leaking close to 1K ASNs today that then would expand to many thousands
> or millions after the draft is approved?
>
> Any network can filter private ASNs as well as various other types of
> ASNs on ingress that they do not want to not accept/propogate.  This
> draft will have no impact on whether people tend to do that correctly or
> not in my opinion.  Folks who have no use for more than a thousand

save the one-time (maybe) change to as-path filters, sure. (not that
that's really an issue)

> internal use ASNs today are not likely to use this new range.
>
> Jon
>
> On Thu, Nov 29, 2012 at 01:19:30PM -0500, Christopher Morrow wrote:
>> On Thu, Nov 29, 2012 at 1:01 PM, Tony Li <tony.li@tony.li> wrote:
>> >
>> > On Nov 29, 2012, at 9:50 AM, Jared Mauch <jared@puck.nether.net> wrote:
>> >
>> >>> Internet folks will say "Do not trash our environment"
>> >>
>> >> As an operator, I feel this is a fair thing for me to say. :)
>> >
>> >
>> > Indeed it is.
>> >
>> > However, I think it's also fair to point out that allocating a chunk from a large namespace and effectively taking out of the big I environment doesn't do much to trash it.
>> >
>>
>> because private asns don't leak?
>> route-views>sho ip bgp regex _64..._
>> <snip>
>>    Network          Next Hop            Metric LocPrf Weight Path
>> *  27.123.19.0/24   195.66.232.239                         0 5459 38082 64549 ?
>> *  41.76.104.0/21   196.7.106.245            0             0 2905 11845 64525 i
>> *  41.90.0.0/16     114.31.199.1             0             0 4826 8966
>> 33771 65535 64555 64555 33771 i
>> *                   194.85.40.15                           0 3267 2603
>> 8966 33771 65535 64555 64555 33771 i
>> *  41.209.32.0/19   164.128.32.11                          0 3303 174
>> 9129 9129 9129 9129 {4558,15808,64520} i
>> *  131.124.1.0/24   69.31.111.244            0             0 4436 4323 64778 i
>> *  131.124.2.0/24   69.31.111.244            0             0 4436 4323 64778 i
>> *  131.124.3.0/24   69.31.111.244            0             0 4436 4323 64778 i
>> *  131.124.4.0/24   69.31.111.244            0             0 4436 4323 64778 i
>> *  131.124.5.0/24   69.31.111.244            0             0 4436 4323 64778 i
>>
>> (hi twtc! filter-customer-much?)
>> _______________________________________________
>> Idr mailing list
>> Idr@ietf.org
>> https://www.ietf.org/mailman/listinfo/idr