Re: [v6ops] Two prefixes [draft-ietf-v6ops-icp-guidance WGLC]

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 08 August 2012 15:48 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B41711E80FE for <v6ops@ietfa.amsl.com>; Wed, 8 Aug 2012 08:48:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.73
X-Spam-Level:
X-Spam-Status: No, score=-100.73 tagged_above=-999 required=5 tests=[AWL=-0.554, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_32=0.6, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pfO9hwCaAJ8F for <v6ops@ietfa.amsl.com>; Wed, 8 Aug 2012 08:48:12 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0E8BE11E80FB for <v6ops@ietf.org>; Wed, 8 Aug 2012 08:48:11 -0700 (PDT)
Received: by eaai11 with SMTP id i11so290908eaa.31 for <v6ops@ietf.org>; Wed, 08 Aug 2012 08:48:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=qX6T+jJpggD0Gtb/ust/QXtZyePvCbwGqmS1aSi5uQE=; b=l2acK6Tyajug+nyz4CpzwUx6t1nCAc5uHRz4kuXbZQAZ+sb02eV8k2w/Z5gzVDmJyU yvfuka7d93A9SRRnSZvRmLT5eesi7uJvi3xhl96JmwfM7ObXMTx3HhLRO1uhnGr0Ovju isrEmd3hXpLyP2gle5Bsr2k92pE7G3HKDbahqDEnAl3utc5JOHI01Vg1jhDrZp4TQZ1o PJyehJYq3Vyd49KjZv7rbbaaX2hMfH33x3oYR4be81fgKn4WTJqm19hfqUEH4melNDTv 4qViTpQo1tfxe+n5t6ZBrg/FJpVuu0dePQeyNcG9RHTrAJd0qGjNUKxFEEPUWXKZvJGB n7Qw==
Received: by 10.14.0.198 with SMTP id 46mr2142754eeb.30.1344440891248; Wed, 08 Aug 2012 08:48:11 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-169.as13285.net. [2.102.217.169]) by mx.google.com with ESMTPS id q3sm62467103eeo.4.2012.08.08.08.48.08 (version=SSLv3 cipher=OTHER); Wed, 08 Aug 2012 08:48:09 -0700 (PDT)
Message-ID: <50228A3D.901@gmail.com>
Date: Wed, 08 Aug 2012 16:48:13 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Arturo Servin <arturo.servin@gmail.com>
References: <5F52A5BB-36F7-4CF9-9639-960C65ADFD4E@cisco.com> <CAD6AjGRMQ8o5fVHeWaOanKYomqJ0jArXS-zXm4qQdqacPS0QbA@mail.gmail.com> <5020DEC0.1090601@gmail.com> <1344332397.93146.YahooMailNeo@web32504.mail.mud.yahoo.com> <CAD6AjGSAE3=rcSo2=96qfiY_41Kq8r5cSgC0N1-fbF+msMF0bg@mail.gmail.com> <50211B63.3020203@gmail.com> <CAKD1Yr1_bADT7cwX9QccRickCYHxqiaDu89Qz7fhbsyZZS6r-Q@mail.gmail.com> <502257A7.7080208@gmail.com> <4E118319-8D7F-40FC-B966-C7F44963A2F2@lacnic.net> <502282E7.3050502@gmail.com> <49BE778F-5C3C-4BA6-8E2C-AC068EA68943@gmail.com>
In-Reply-To: <49BE778F-5C3C-4BA6-8E2C-AC068EA68943@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: Ron Bonica <ron@bonica.org>, "v6ops@ietf.org" <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>
Subject: Re: [v6ops] Two prefixes [draft-ietf-v6ops-icp-guidance WGLC]
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 08 Aug 2012 15:48:13 -0000

Arturo,

On 08/08/2012 16:28, Arturo Servin wrote:
> 	No, I didn't say that.
> 
> 	1) if you are small, multi-homed you should use BGP+PI.
> 
> 
> 	2) if you are small and uni-home use PA.
> 
> 		
> 	If 1 does not scale (I would question that), it is a problem that we should solve elsewhere.

Yes, of course, and that was the main focus of the Routing Research Group for
a couple of years (see RFC 6115). It's pretty clear that it doesn't scale to
millions of sites with currently deployable technology. That being so,
IMHO v6ops has to be cautious about encouraging widespread usage. (This
applies generally, not just to ICPs, of course.)

   Brian

> 	There are other solutions for 1, but I would not recommend them as a best practice, just like workarounds to use PA and avoid BGP.
> 
> 	1 and 2 are orthogonal to the fact that the ICP is as well an enterprise or not.
> 
> Regards,
> as
> 
> On 8 Aug 2012, at 12:16, Brian E Carpenter wrote:
> 
>> On 08/08/2012 15:59, Arturo Servin wrote:
>>> Brian,
>>>
>>> 	But we are not talking about enterprises, we are talking about ICPs, which IMHO are two different problems and advices.
>> To be clear, I intended to talk about either pure specialised ICPs, or an enterprise that
>> wishes to behave as an ICP for its own content.
>>
>>> 	For Enterprises, yes PA and PI are debatable (as discussed in many places, many times) and more dependent on the size and type of enterprise, for ICPs I think we are more or less in consensus that PI is more much common (and IMO the recommendation).
>>>
>>> 	Perhaps, the corner case are "small ICPs" which if they are uni-homed, then PA is fine, if they are multi-homed then BGP+PI should be the recommendation no matter if they are small or large.
>> But that's the case that doesn't scale to millions. Are you suggesting that
>> we have to tell them "you can't serve your own content reliably, because
>> you're too small"?
>>
>>    Brian
>>
>>> Regards,
>>> as
>>>
>>> On 8 Aug 2012, at 09:12, Brian E Carpenter wrote:
>>>
>>>> My concern here, as I've already hinted, is publishing advice that is
>>>> valid for the N thousand enterprises that can reasonably expect to get
>>>> a PI prefix but nothing for the N million others that may wish to serve
>>>> up content *and* be multihomed.
>>>
> 
>