Re: Wasting address space (was: Re: Last Call: 'Considerations on the IPv6 Host density Metric' to Informational RFC (draft-huston-hd-metric))

Tim Chown <tjc@ecs.soton.ac.uk> Tue, 06 June 2006 14:37 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fncgu-0001aF-QY; Tue, 06 Jun 2006 10:37:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fncgs-0001a1-T9 for ietf@ietf.org; Tue, 06 Jun 2006 10:37:54 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fnbdf-0008Ro-WA for ietf@ietf.org; Tue, 06 Jun 2006 09:30:32 -0400
Received: from owl.ecs.soton.ac.uk ([152.78.68.129]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FnbQq-0003MJ-E9 for ietf@ietf.org; Tue, 06 Jun 2006 09:17:17 -0400
Received: from goose.ecs.soton.ac.uk (goose.ecs.soton.ac.uk [152.78.68.131]) by owl.ecs.soton.ac.uk (8.13.1/8.13.1) with ESMTP id k56DHCpq010583 for <ietf@ietf.org>; Tue, 6 Jun 2006 14:17:12 +0100
Received: from login.ecs.soton.ac.uk (login.ecs.soton.ac.uk [152.78.68.162]) by goose.ecs.soton.ac.uk (8.13.1/8.13.1) with ESMTP id k56DH3AY022468 for <ietf@ietf.org>; Tue, 6 Jun 2006 14:17:05 +0100
Received: (from tjc@localhost) by login.ecs.soton.ac.uk (8.12.11.20060308/8.11.6) id k56DGxND007556 for ietf@ietf.org; Tue, 6 Jun 2006 14:16:59 +0100
Date: Tue, 06 Jun 2006 14:16:59 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Message-ID: <20060606131659.GF31719@login.ecs.soton.ac.uk>
Mail-Followup-To: ietf@ietf.org
References: <1149305596.24519.142.camel@tachyon> <FCD8E720-5865-4C50-B839-BD52E6F62F13@muada.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <FCD8E720-5865-4C50-B839-BD52E6F62F13@muada.com>
User-Agent: Mutt/1.4i
X-ECS-MailScanner: Found to be clean, Found to be clean
X-Spam-Status: No
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Subject: Re: Wasting address space (was: Re: Last Call: 'Considerations on the IPv6 Host density Metric' to Informational RFC (draft-huston-hd-metric))
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

On Mon, Jun 05, 2006 at 08:12:28PM +0200, Iljitsch van Beijnum wrote:
> 
> Having to choose between /60 and /48 would be much better than having  
> to choose between /64 and bigger in general, as it removes the "will  
> I ever need a second subnet" consideration, the average allocation  
> size goes down and moving to a /48 after having grown out of a /60  
> isn't too painful.

There's a certain appeal to this, to have to renumber before your
network grows too big.  Interesting suggestion.
 
> It's also really helpful if all ISPs use the same subnet sizes. For  
> instance, I can set up my routes as DHCPv6 prefix delegation clients,  
> so they can be reconfigured with new address prefixes automatically  
> when changing ISPs, but I still need to put the subnet bits (and  
> therefore the subnet size) in the configuration by hand, so having to  
> change that defeats the purpose of the exercise.

Which was the point of /48 pervasively?

-- 
Tim/::1



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf