Re: draft-bourbaki-6man-classless-ipv6-00

Peter Hessler <phessler@theapt.org> Sun, 04 June 2017 13:16 UTC

Return-Path: <phessler@theapt.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03BAD129B2B for <ipv6@ietfa.amsl.com>; Sun, 4 Jun 2017 06:16:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.008
X-Spam-Level:
X-Spam-Status: No, score=0.008 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
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 PVhRk60_5oM2 for <ipv6@ietfa.amsl.com>; Sun, 4 Jun 2017 06:16:22 -0700 (PDT)
Received: from gir.theapt.org (gir.theapt.org [81.209.183.113]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A699129B22 for <ipv6@ietf.org>; Sun, 4 Jun 2017 06:16:22 -0700 (PDT)
Received: from gir.theapt.org (unknown [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/0 bits)) (Client did not present a certificate) (Authenticated sender: phessler) by gir.theapt.org (Postfix) with ESMTPSA id BB63778985 for <ipv6@ietf.org>; Sun, 4 Jun 2017 15:16:20 +0200 (CEST)
Date: Sun, 04 Jun 2017 15:16:19 +0200
From: Peter Hessler <phessler@theapt.org>
To: ipv6@ietf.org
Subject: Re: draft-bourbaki-6man-classless-ipv6-00
Message-ID: <20170604131619.GJ30896@gir.theapt.org>
References: <20170602141259.GD30896@gir.theapt.org> <CAKD1Yr0DtQYvCYLQexhXe_nhb5rjeyhnB4bCveqyO5Xbuwdg1A@mail.gmail.com> <20170602145655.msfjw35qhoev4sm2@Vurt.local> <CAKD1Yr3gqFgq3dxFaBEV++q5cgx1AHzFLGRJ50DYJjVE69C7iA@mail.gmail.com> <f2260ee557014429a1fef32de040547b@XCH15-06-11.nw.nos.boeing.com> <d62ce5e3ea0f486eb4c9d54609a86b24@XCH15-06-08.nw.nos.boeing.com> <04bdfdfe018145e6aedbaa62ed6cbfb0@XCH15-06-11.nw.nos.boeing.com> <78fe298cb5484d50a56cf6ed4ddafb54@XCH15-06-08.nw.nos.boeing.com> <6bba4c2b58964787860f2c7acf130959@XCH15-06-11.nw.nos.boeing.com> <f3ea6bf2d52b4179b1d9268dbcf67771@XCH15-06-08.nw.nos.boeing.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <f3ea6bf2d52b4179b1d9268dbcf67771@XCH15-06-08.nw.nos.boeing.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/aGjMypZUd6irQoVId_vFhnu3YO4>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 04 Jun 2017 13:16:23 -0000

On 2017 Jun 02 (Fri) at 20:14:11 +0000 (+0000), Templin, Fred L wrote:
:Another question that we would have to ask is what is the longest prefix that
:we should expect an ISP (or a core Internet router, for that matter) to carry
:in its routing tables? A /80? A /96?

OpenBGPD is intended for use on the default-free-zone, and has a default
configuration that allows /16 - /48 for IPv6 prefixes.  In looking at RIR
policies, and recommendations from vendors and operational documents, /48
looks to be the longest prefix length that you can consider reliably
routable beyond your own AS.

*Inside* an AS however, I see no reason to artificially limit the prefix
size.  Operators should aggregrate where it makes sense
(region/metro/building/cage/row/rack/etc), but that is good design
regardless of the size or even IP version.


-- 
First Law of Socio-Genetics:
	Celibacy is not hereditary.