Re: ITU-T Dubai Meeting

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 07 August 2012 08:20 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CCC121F8587 for <ietf@ietfa.amsl.com>; Tue, 7 Aug 2012 01:20:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.476
X-Spam-Level:
X-Spam-Status: No, score=-101.476 tagged_above=-999 required=5 tests=[AWL=0.215, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, 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 LohelqqloI3o for <ietf@ietfa.amsl.com>; Tue, 7 Aug 2012 01:20:11 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 012E821F866A for <ietf@ietf.org>; Tue, 7 Aug 2012 01:20:10 -0700 (PDT)
Received: by eekb45 with SMTP id b45so1011376eek.31 for <ietf@ietf.org>; Tue, 07 Aug 2012 01:20:10 -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=Bq5Y8h72GHCMAAUACDVXi4dcMWhAnyzBeyh9TC5rB0Y=; b=P7mARCUOKhXIGNZ8y/+UvcD9+iOyHGc3yyLi3j+/R83j192KCMH8mrvuu595YCWJ4y 8U0xJoVj6DvUi6RGJvYvd4oA5BrvPIuJkCvVZfgN0WZ2vAyMo5asGKPlpMOWs01FeUC6 3+CEGc4CVQhTdYZ3qcx3WjpVTwJpnkkNNe9sllHlzCr7htiCv1lo4JfdjVVNcucfFFtz JEZf530ZrTLoEFgVmhXiQwA0OkFZGYsqlUO6PCl79gtedvQm7yrJsDaEvwzbWR54dFfW CacXIil5C8j3360+CF0tGX/izdn4/O1eW9nHQi1m+XmL0ZcMIpQrTvrlFM/UqxQOQ8YG HyYg==
Received: by 10.14.214.196 with SMTP id c44mr16774472eep.7.1344327610151; Tue, 07 Aug 2012 01:20:10 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-145.as13285.net. [2.102.216.145]) by mx.google.com with ESMTPS id j4sm53930127eeo.11.2012.08.07.01.20.08 (version=SSLv3 cipher=OTHER); Tue, 07 Aug 2012 01:20:09 -0700 (PDT)
Message-ID: <5020CFB9.7090402@gmail.com>
Date: Tue, 07 Aug 2012 09:20:09 +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: mrex@sap.com
Subject: Re: ITU-T Dubai Meeting
References: <20120807074601.23F871A125@ld9781.wdf.sap.corp>
In-Reply-To: <20120807074601.23F871A125@ld9781.wdf.sap.corp>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 08:20:12 -0000

Martin,

As far as the mass market goes, multiple prefixes and renumbering are a fact of life.
See the MIF and HOMENET WGs for more.

As far as enterprise networks go, renumbering is rather undesirable but sometimes
inevitable, see 6RENUM.

Regards
   Brian

On 07/08/2012 08:46, Martin Rex wrote:
> Brian E Carpenter wrote:
> [ Charset UTF-8 unsupported, converting... ]
>> On 06/08/2012 23:02, Martin Rex wrote:
>>> Steven Bellovin wrote:
>>>> Randy Bush wrote:
>>>>> whatever the number of address bits, if it is fixed, we always run out.
>>>>> memory addressing has been a cliff many times.  ip addressing.  ...
>>>> Yup.  To quote Fred Brooks on memory address space: "Every successful
>>>> computer architecture eventually runs out of address space" -- and I heard
>>>> him say that in 1973.
>>> I'm wondering what resource shortage would have happened if IPv6
>>> had been massively adopted 10 years earlier, and whether we would have
>>> seen the internet backbone routers suffer severely from the size
>>> of the routing tables, if every single home customer (DSL subscriber)
>>> would have required a provider-independent IPv6 network prefix rather
>>> than a single, provider-dependent IPv4 IP Address.
>> That was never a likely scenario (and still isn't). PA prefixes are still
>> the norm for mass-market IP, regardless of version number.
> 
> 
> IPv6 PA prefixes result in that awkward renumbering.
> Avoiding the renumbering implies provider independent
> network prefix.
> 
> With IPv4, you would have typically keept your IPv4 network address
> (the old class A, B & C from early 199x) even when changing network
> providers.
> 
> 
> To me, IPv6 PA prefixes look like a pretty useless feature
> (from the customer perspective).  Either you want an provider-independent
> prefix to avoid the renumbering when changing providers,
> or you want some level of privacy protection and therefore
> a fully dynamic temporary DHCP-assigned IPv6 address
> (same network prefix for 10000+ customers of the ISP)
> and for use with NAT (again to avoid the renumbering).
> 
> IPv6 renumbering creates huge complexity without value (for the customer).
> 
> -Martin
>