Re: [dhcwg] /128 address allocation and "localized IPv6 address space exhaustion", was RE: Brokenness of specs w.r.t. client behavior with M&O bits

"H. Peter Anvin" <hpa@zytor.com> Sun, 02 November 2008 16:09 UTC

Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipngwg-archive@lists.ietf.org
Delivered-To: ietfarch-ipngwg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1157D3A681A; Sun, 2 Nov 2008 08:09:14 -0800 (PST)
X-Original-To: IPV6@core3.amsl.com
Delivered-To: IPV6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 404523A68D7 for <IPV6@core3.amsl.com>; Sat, 1 Nov 2008 17:06:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level:
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q44kxp+Zm4+b for <IPV6@core3.amsl.com>; Sat, 1 Nov 2008 17:06:52 -0700 (PDT)
Received: from terminus.zytor.com (terminus.zytor.com [198.137.202.10]) by core3.amsl.com (Postfix) with ESMTP id 6888C3A688D for <IPV6@core3.amsl.com>; Sat, 1 Nov 2008 17:06:52 -0700 (PDT)
Received: from [172.27.2.85] (c-98-210-181-100.hsd1.ca.comcast.net [98.210.181.100]) (authenticated bits=0) by terminus.zytor.com (8.14.2/8.14.1) with ESMTP id mA203ccI019253 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 1 Nov 2008 17:03:39 -0700
Message-ID: <490CEE60.1030708@zytor.com>
Date: Sat, 01 Nov 2008 17:03:44 -0700
From: "H. Peter Anvin" <hpa@zytor.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080723)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [dhcwg] /128 address allocation and "localized IPv6 address space exhaustion", was RE: Brokenness of specs w.r.t. client behavior with M&O bits
References: <7182010.12431219366974773.JavaMail.weblogic@epml09> <9A613C72-E818-410B-9769-8C34E8A78AE1@cisco.com> <200810131540.m9DFeRGR009155@rotala.raleigh.ibm.com> <BA6C47AC-1668-47CE-94D0-49C4F7A6775E@muada.com> <20081013163846.GA5577@isc.org> <FA7A47C2-0935-4BA3-A0EF-EC1773B181A0@muada.com> <20081014163236.GD5364@isc.org> <F3BF1907-5B33-4B6E-9ED8-B5AF275134BE@muada.com> <7465F7E3-931F-4924-AC84-2993AF447E68@nominum.com> <DC237AE116C10E4C9AD162D6C2EE62FE0134D3BC@vaebe102.NOE.Nokia.com> <a3c826bd0810232004v50879492j97d4be8132e0cd97@mail.gmail.com> <DC237AE116C10E4C9AD162D6C2EE62FE01383D2B@vaebe102.NOE.Nokia.com> <490799D1.7080307@gmail.com> <DC237AE116C10E4C9AD162D6C2EE62FE013B4AFD@vaebe102.NOE.Nokia.com> <490A6DFF.10103@gmail.com>
In-Reply-To: <490A6DFF.10103@gmail.com>
X-Virus-Scanned: ClamAV 0.93.3/8552/Fri Oct 31 18:14:36 2008 on terminus.zytor.com
X-Virus-Status: Clean
X-Mailman-Approved-At: Sun, 02 Nov 2008 08:09:13 -0800
Cc: ipv6@ietf.org, IPV6@core3.amsl.com, iljitsch@muada.com, Ted.Lemon@nominum.com, dhcwg@ietf.org, Markku.Ala-Vannesluoma@nokia.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

Brian E Carpenter wrote:
> 
>> I would not like to see IPv6 NAPT, but I see that as a real risk if
>> network is using DHCPv6 for allocating hosts just /128 addresses but at
>> the same time is not willing to delegate prefixes on demand. 
> 
> Agreed.

The sad part is that it's probably inevitable given the decision to have 
a fixed address length for IPv6.

	-hpa

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------