Re: [v6ops] [Fwd: I-D Action: draft-ietf-v6ops-icp-guidance-03.txt]

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 31 August 2012 14:53 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 5F18A21F8628 for <v6ops@ietfa.amsl.com>; Fri, 31 Aug 2012 07:53:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.528
X-Spam-Level:
X-Spam-Status: No, score=-101.528 tagged_above=-999 required=5 tests=[AWL=0.163, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 AerxxD61TpIe for <v6ops@ietfa.amsl.com>; Fri, 31 Aug 2012 07:53:25 -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 9F6B721F8621 for <v6ops@ietf.org>; Fri, 31 Aug 2012 07:53:24 -0700 (PDT)
Received: by eaai11 with SMTP id i11so940018eaa.31 for <v6ops@ietf.org>; Fri, 31 Aug 2012 07:53:23 -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=aBlLBs17LoaOy/3l4jL6uLzLYShYAEjYkyF22L23ats=; b=Ye5GztnZMyR4lw0sCqTp+7fl2yW62JTZVjpFMhQG7dYFXUYMM2QMEPGLv1s7YJjhnW HRutQuE6LwB6L1S+UVlbzhQo/MYUwNd6V5SK8l8N/tI/WLg0KpsT3/4zwQWrHsUkXV9K tNvT/XmazjfdbU89PQgnZaFh6XufRUqJCJg/ueSSWNTXGWlNV5J/HywttG0XCfZ95wcB rQ9/yIA2BH07EQKixxS/TgSIfXRpoFHwSIq6Qmm/WbwTzZ0Ljt0oP5Fs9/zWuwhG0WJ4 2cqVx+eL3MNNr+ya9gPmanHGmVvZwYzw+Z2akavYRY4912yjBYkl37GlQuiEKeUzQ7ov lHeg==
Received: by 10.14.203.69 with SMTP id e45mr11525391eeo.23.1346424803836; Fri, 31 Aug 2012 07:53:23 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-147.as13285.net. [2.102.216.147]) by mx.google.com with ESMTPS id v3sm14104871eep.10.2012.08.31.07.53.22 (version=SSLv3 cipher=OTHER); Fri, 31 Aug 2012 07:53:22 -0700 (PDT)
Message-ID: <5040CFEC.9010307@gmail.com>
Date: Fri, 31 Aug 2012 15:53:32 +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: Nick Hilliard <nick@inex.ie>
References: <5040646F.6000103@gmail.com> <50407CAB.4060903@redpill-linpro.com> <504094DD.9060708@gmail.com> <50409C2A.2060805@redpill-linpro.com> <5040B3FB.7060502@inex.ie>
In-Reply-To: <5040B3FB.7060502@inex.ie>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] [Fwd: I-D Action: draft-ietf-v6ops-icp-guidance-03.txt]
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: Fri, 31 Aug 2012 14:53:26 -0000

Nick,

On 31/08/2012 13:54, Nick Hilliard wrote:
> On 31/08/2012 12:12, Tore Anderson wrote:
>> The document continues in the same vein: «only large content providers
>> can justify the bother and expense of obtaining a PI prefix». Can't say
>> I agree.
> 
> +1.
> 
> PI is easy to get and there are plenty of smaller organisations who depend
> on it for their business requirements (at least for ipv4).  

It's a solution, not a requirement. It may well be the *only* solution in
IPv4, but this is about IPv6 which needs to be much more scaleable than
IPv4 to make any sense.

> There are no
> substantial issues with routing PIv6 address space, because the minimum
> assignment size is /48, which corresponds with the RIRs' recommendations on
> minimum prefix filter length.

That is, however, just a pragmatic choice and with the *current* size of the
IPv6 RIB, simply not an issue. The point is that we (the IETF) need to set
things rolling in a way that will scale to an IPv6 RIB many times bigger
than the current IPv4 RIB. Recommending PI unconditionally is, in my
opinion, highly irresponsible in that context.

As document editors we will of course do what the WG chairs determine
is the WG consensus. As an individual contributor, I will continue to press
for recognition of the PA approach.

    Brian

> 
> Nick
> 
>