Re: [v6ops] [GROW] Deaggregation by large organizations

joel jaeggli <joelja@bogus.com> Thu, 16 October 2014 15:38 UTC

Return-Path: <joelja@bogus.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E4E21A1BCC; Thu, 16 Oct 2014 08:38:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.769
X-Spam-Level:
X-Spam-Status: No, score=0.769 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RDNS_DYNAMIC=0.982] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zt4URGXSivKK; Thu, 16 Oct 2014 08:38:27 -0700 (PDT)
Received: from minorthreat.org (ec2-54-68-221-247.us-west-2.compute.amazonaws.com [54.68.221.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A27691A1BAE; Thu, 16 Oct 2014 08:38:27 -0700 (PDT)
Received: from mb-aye.local (c-67-188-0-113.hsd1.ca.comcast.net [67.188.0.113]) (authenticated bits=0) by minorthreat.org (8.14.9/8.14.9) with ESMTP id s9GFc34F015472 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 16 Oct 2014 15:38:03 GMT (envelope-from joelja@bogus.com)
Message-ID: <543FE66F.9020309@bogus.com>
Date: Thu, 16 Oct 2014 08:38:23 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:33.0) Gecko/20100101 Thunderbird/33.0
MIME-Version: 1.0
To: Gert Doering <gert@space.net>, Christopher Morrow <christopher.morrow@gmail.com>
References: <F5C06CAF-0AD2-4225-8EE7-FC72CE9913F0@muada.com> <CAL9jLaZLWG5cKPPhTtLtvn9OQOYwYjdgHCUXsWi3pZJjK+nAbQ@mail.gmail.com> <903173CE-64D6-4FE5-98DB-B408C9586A02@muada.com> <CAL9jLaZiUfb2Pz--nWMq_=DhSz0m4uwDcyPs19PVuq=t6vpyxA@mail.gmail.com> <20141016143743.GC31092@Space.Net> <CAL9jLaYvN3vthmcKNmBj-q+puWkuEdWf=2cfWBCTUXV9j=g_Wg@mail.gmail.com> <20141016145931.GE31092@Space.Net>
In-Reply-To: <20141016145931.GE31092@Space.Net>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="KaTt10DIjXVilQLhKdal5UVH2Cxo0bRu7"
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/p9YSH5vAMBnNW_HVRBt-0_uTxJo
Cc: IPv6 Operations <v6ops@ietf.org>, "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Subject: Re: [v6ops] [GROW] Deaggregation by large organizations
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Oct 2014 15:38:29 -0000

On 10/16/14 7:59 AM, Gert Doering wrote:
> Hi,
> 
> On Thu, Oct 16, 2014 at 10:45:23AM -0400, Christopher Morrow wrote:
>>> A strong message to that extent would be good :-) - coupled with
>>> some recommendations how the conflicting goals ("I want all ISPs in
>>> my neighbourhood to use optimal routing" vs. "someone in Asia might
>>> not be interested in all in 5k routes for german municipality")
>>> could be solved.
>>
>> ok, perhaps iljitsch can drop some text into a document so we can get
>> a good read going and decide whether or not GROW wants to spend cycles
>> on it?
> 
> That would be nice (as I see the problem but have no cycles to write
> something useful).
> 
>> The problem exists in v4 and v6 and likely will persist in whatever
>> comes next. It's directly related to routing operations work on the
>> global intertubes, so it SEEMS like GROW is the 'right place' to
>> discuss this... we can't go anywhere without text and a draft though.
> 
> It seems to be made worse by the fact that "this" can be done more
> easily with IPv6, as you just can't get enough v4 space to subdivide
> it into 5000 globally visible prefixes today - and those entities that
> discover the "must have reliability!  must have independence!" mantra
> *now* will hit the v6 space...  (given that I see this argument in this
> dimension more often from governmental structures who have been hiding
> behind single-IPv4-NAT so far).

The number of autonomous systems present in the internet is a good proxy
for the number of organizations that find this necessary. It is not a
proxy for the number of prefixes each of those ASes choose to advertise
though somewhat less than half of those ASNs advertise one prefix only.

http://www.cidr-report.org/cgi-bin/plot?file=%2fvar%2fdata%2fbgp%2fas2.0%2fbgp-as-count%2etxt&start=0&end=1413472455&width=0%2e9&height=0%2e3&with=step&ylabel=AS+Count


>>> I get that question fairly often from "largish networks", and so far,
>>> I always have to answer "there is no routing police, so it's hard to
>>> say what is allowed on the Internet and what not" - which is a humorous
>>> way to say "there is no consensus here what consists 'good' and
>>> 'responsible'"...
>>
>> I sort of don't want there to be 'routing police' though :( In a way
>> this whole debate sounds like something a 'cisco training class' (or
>> other example) would have covered, or should cover. I suppose it's
>> fairly experiential at this point though.
> 
> I *do* want a routing police, in the sense that "the operator community"
> agrees on what is considered "good" and "bad" behaviour, so end users
> can ask someone (me, Iljitsch, ...) what to do in their network planning,
> and we can tell them
> 
>   - if you do *this*, it's "guaranteed" to work
>   - if you do *that*, you can be sure that you will be filtered
> 
> while today, I have to tell them
> 
>   - well, today it is likely to work, but it might stop working tomorrow,
>     and there is no document that you could show around to those that
>     break your connectivity to show them that "you are doing the right thing"
> 
> ISPs develop their own guidelines on prefix-length filtering, some with
> better understanding on what they want to achieve, others by using 10 year
> old example documents for never-updated filters...
> 
> So, yes, guidance, please :-)
> 
> Gert Doering
>         -- NetMaster
> 
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>