[Idr] On FIB sizing...

Tony Li <tony.li@tony.li> Sun, 16 December 2012 02:27 UTC

Return-Path: <tony.li@tony.li>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA1C121F8549 for <idr@ietfa.amsl.com>; Sat, 15 Dec 2012 18:27:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level:
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dR7FY85hoYcr for <idr@ietfa.amsl.com>; Sat, 15 Dec 2012 18:27:52 -0800 (PST)
Received: from qmta13.emeryville.ca.mail.comcast.net (qmta13.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:243]) by ietfa.amsl.com (Postfix) with ESMTP id 0ED5E21F8543 for <idr@ietf.org>; Sat, 15 Dec 2012 18:27:51 -0800 (PST)
Received: from omta12.emeryville.ca.mail.comcast.net ([76.96.30.44]) by qmta13.emeryville.ca.mail.comcast.net with comcast id c2Dd1k0020x6nqcAD2Tr7r; Sun, 16 Dec 2012 02:27:51 +0000
Received: from sjc-vpn7-675.cisco.com ([128.107.239.233]) by omta12.emeryville.ca.mail.comcast.net with comcast id c2RZ1k00Z52qHCY8Y2Rf2m; Sun, 16 Dec 2012 02:25:49 +0000
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Tony Li <tony.li@tony.li>
In-Reply-To: <CAPWAtb+Lo6hRu6Hg9dQNf2VUJ9q_85H+bKiRZE1WEaRnLN4BVQ@mail.gmail.com>
Date: Sat, 15 Dec 2012 18:25:32 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <AEA6A7A2-9934-4B0F-BCD0-19CC4C1B371B@tony.li>
References: <CA+b+ERnSVvewSpftXs3FhW12-S+sgnB1SwD4L+xqFW+hhbQayw@mail.gmail.com> <7120600D-71BD-4E61-8F06-25B7C2BAE6A8@riw.us> <20121211185917.GA21813@puck.nether.net> <CA+b+ERnzo2BLWjE1J_dMfYuExbG9WYJroPE4ZAWg++KK2_jy1g@mail.gmail.com> <CA+b+ERm=Agr7b6JXcXOwiP4wBjnEFmnVNt5fAJrn18R0hGtSzg@mail.gmail.com> <50C78C29.3070406@foobar.org> <50C8B8D9.4090903@umn.edu> <50C9039E.1050104@foobar.org> <20121213144147.GB4524@puck.nether.net> <50CB52E0.7080602@foobar.org> <20121214174012.GA18502@puck.nether.net> <50CBB294.1000300@umn.edu> <B5907AE4-F639-4CC7-B522-B9AD92E61A51@kumari.net> <50CCFD49.1060307@foobar.org> <1355614542.6115.19.camel@galileo.millnert.se> <CAPWAtb+Lo6hRu6Hg9dQNf2VUJ9q_85H+bKiRZE1WEaRnLN4BVQ@mail.gmail.com>
To: Jeff Wheeler <jsw@inconcepts.biz>
X-Mailer: Apple Mail (2.1499)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1355624871; bh=pJOiFQEubAx1ZUn15VXdJGMDN79Ut3+AwBhcBzFNLeQ=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=AEasOYZJSqeo7GvQ+wwJwO22QOFtgfBqY1LUWFZyNJgyDKqjWXBEriFEsFmNA0wva Y/vYBTB4FsF8nyUQcfdC4PMeIL1NypLK0heYqPJvTsmdqZQxrt43jcVxKHZy2rcN9c YZ63e40g/jv7zKZXchD2lQRDa7t70hFclwKK8R4nh3XGP1nOGhMjDmJQgZxMW+zKMu 05plI+sJrBWk+CbbqeXMvkxkJewmQSj6T+k4gnTF5t4wfZRnlnoBJzgyXJE8BOSHmx TrqzTb3gYIVW8rrXxYjPEIjmhX6rxP/MZD4iWJtTjIxLl2iWRqAJmyBnPIgcXbRya4 tnU1qeJrhL35A==
Cc: IETF IDR Working Group <idr@ietf.org>
Subject: [Idr] On FIB sizing...
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2012 02:27:53 -0000

On Dec 15, 2012, at 4:26 PM, Jeff Wheeler <jsw@inconcepts.biz> wrote:

> I thought 2^128 for IPv6 was stupid.  It was an expensive choice,
> given the challenges which still exist in dealing with 128 bit
> arithmetic in many environments, FIB consumption, legibility of
> addresses, and so on.  


As an aside, FIB sizing only varies loosely with the maximum number of bits in the address because the FIB can be constructed to hold only prefixes.  Thus, what's more important is the average and distribution of prefix lengths.

Thus, (for a core router) the choice of /128 is largely irrelevant when remote prefixes are all /64 and shorter.  For a datacenter switch that has to store possibly many /128's, this is more of an issue, but is offset because there is no ARP cache to deal with.

Tony