Re: router behaviour with prefixes longer than /64

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 17 March 2014 20:51 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2813C1A045A for <ipv6@ietfa.amsl.com>; Mon, 17 Mar 2014 13:51:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 08wi1fxfV4ph for <ipv6@ietfa.amsl.com>; Mon, 17 Mar 2014 13:50:58 -0700 (PDT)
Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 73A851A0503 for <ipv6@ietf.org>; Mon, 17 Mar 2014 13:50:58 -0700 (PDT)
Received: by mail-we0-f178.google.com with SMTP id u56so5116492wes.9 for <ipv6@ietf.org>; Mon, 17 Mar 2014 13:50:50 -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=Ni1NlbvbdRNw01oARHMejMd7zh6Wqbtuzb72ft80UUk=; b=IulZo6bYNedquH6N9mlmE1C/fZ8lOQg4IS5CROMv2Uox3skfPLttq+5rmuL7+O3/zS OsGkdquTTensMdevinS84wSaEOqnDkZGEG+t/hOxDXEzS34EJ1kz29O95pt/wh/oiMht cQTLwJBuxXG/woyv8sjv1Q8tyeguMKykkHjb6opIqaHu5+qv3rJj25kCigIJc6Dz/JJT a3VhtbvhXFzx0gcB6lFaDmjU79BnNXnryWSy/m/oWKnTctMmt95zRBVQP1g5fAGYYX6S NgxSneu5yhWDnSxlPHkP+T5L8ElnYqoMvVmp8BmLz/VoXj+RF9Kb3AaPejk6Eg1cNRfn DdFQ==
X-Received: by 10.194.204.199 with SMTP id la7mr20342197wjc.4.1395089450044; Mon, 17 Mar 2014 13:50:50 -0700 (PDT)
Received: from [192.168.0.6] (cpc8-mort6-2-0-cust102.croy.cable.virginm.net. [82.43.108.103]) by mx.google.com with ESMTPSA id hy8sm41347769wjb.2.2014.03.17.13.50.48 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 17 Mar 2014 13:50:49 -0700 (PDT)
Message-ID: <5327602C.3010905@gmail.com>
Date: Tue, 18 Mar 2014 09:50:52 +1300
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: Peter Dordal <pld@cs.luc.edu>
Subject: Re: router behaviour with prefixes longer than /64
References: <9734C3A6-2678-4B50-98BD-21767420B9A4@gmail.com> <20140313.213538.41718510.sthaug@nethelp.no> <1BDB0240-28C8-41D7-B8EF-B7F26E9A036D@gmail.com> <021E64FECA7E5A4699562F4E66716481189E2017@XCH-PHX-503.sw.nos.boeing.com> <A4C13F60-1EA5-41D2-B6D4-51C10EAFD3A9@gmail.com> <021E64FECA7E5A4699562F4E66716481189E4240@XCH-PHX-503.sw.nos.boeing.com> <1394766011.25163.77.camel@tachyon.blake> <021E64FECA7E5A4699562F4E66716481189E44E5@XCH-PHX-503.sw.nos.boeing.com> <CAKD1Yr2VZ6WzAXg1VRtgtpxxX+JQomxv8w3VhGidq8jvZOK3bw@mail.gmail.com> <021E64FECA7E5A4699562F4E66716481189E4C92@XCH-PHX-503.sw.nos.boeing.com> <53274A52.4010201@umn.edu> <5327530F.7060003@cs.luc.edu>
In-Reply-To: <5327530F.7060003@cs.luc.edu>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/rWZW2cO4XVA9yj7nPkQcyMaFhYI
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Mar 2014 20:51:01 -0000

Peter,

On 18/03/2014 08:54, Peter Dordal wrote:
> On 03/17/2014 02:17 PM, David Farmer wrote:
>> On 3/17/14, 12:45 , Manfredi, Albert E wrote:
>>> From: Lorenzo Colitti [mailto:lorenzo@google.com]
>>>
>>>>> I didn't miss that. People seem to be reading this clause backwards.
>>>>>
>>>>> I'm saying that "those that start with binary value 000" are the vast
>>>>> majority of potential IPv6 global unicast addresses.
>>>
>>>> No, the way to read it is exactly the way it's written: for *all*
>>>> unicast addresses, except those that start with 0 or 1, IIDs are 64
>>>> bits long, period.
>>>
>>> Are you disagreeing that unicast addresses starting with 000 are the vast 
>>> majority of potential future unicast addresses?
>>
>> The only currently defined IPv6 addresses that start with the binary value 
>> 000, are special-purpose addresses, all other addresses that meet this 
>> definition are reserved, and not currently available for allocation, though 
>> they are reserved for future unicast allocation.
> 
> My understanding of the 0::/3 block has always been that it represents a fallback
> in case 64-bit prefixes don't work out for some reason. This address block is 
> "held in reserve".

No. It's partially used for special purpose addresses. The reserve is in the fact
that only 2000::/3 (1/8 of the total space) has been released to IANA for unicast
allocations.

   Brian

> That is, if we run out of /64 IPv6 address prefixes, we can always divide up the 
> 0::/3 block using, say, /96 prefixes.

> (And then at that point figure out how to manage with 32-bit interface IDs.)
> 
>> ...
>> There has never been any general-purpose unicast addresses that start with the 
>> binary value 000, only the current and historic special-purpose addresses.
>>
> But this /could/ change in the future, though that would be likely only if there 
> were a problem with the 64/64 division.
> Which is to say not very likely at all.
> 
> Peter Dordal
> Loyola Univ Chicago CS Dept
> 
> 
> ------------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------