Re: [Casm] I-D Action: draft-li-casm-address-pool-management-arch-00.txt

Michael Richardson <> Wed, 22 March 2017 19:32 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 44EAC1294FB for <>; Wed, 22 Mar 2017 12:32:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id OGERG-RWNm6u for <>; Wed, 22 Mar 2017 12:32:14 -0700 (PDT)
Received: from ( [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5BDE7129C04 for <>; Wed, 22 Mar 2017 12:32:06 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 4E38C205A4 for <>; Wed, 22 Mar 2017 15:55:36 -0400 (EDT)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id D3248636BB for <>; Wed, 22 Mar 2017 15:32:04 -0400 (EDT)
From: Michael Richardson <>
In-Reply-To: <>
References: <> <>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Wed, 22 Mar 2017 15:32:04 -0400
Message-ID: <>
Archived-At: <>
Subject: Re: [Casm] I-D Action: draft-li-casm-address-pool-management-arch-00.txt
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Centralized Address Space Management <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 22 Mar 2017 19:32:16 -0000

Brian E Carpenter <> wrote:
    >> APMS A management system which has a centralized databse manage the
    >> overall address pools and allocate address pools to the device in the
    >> devices.

    > Again, although a central database is the traditional approach, we must
    > be open to a scalable approach and that means distribution. Certainly
    > there must be an *initial* pool that originates by human action in the
    > NOC. But that does not require a central database that records every
    > detail.

It would be good if whatever data format we come up to describe the prefixes
was also the format that ARIN/RIPE/etc. used/returned.
This would eliminate certain amounts of human-induced errors.

    > If an ISP has say a /29 and is delegating /48 to subscribers, it has to
    > manage up to 2**19 prefixes. That isn't an impossible size for a
    > central database, but it is large. (And this is a small ISP.)  The
    > problem becomes much easier if you distribute it among, say, 100 agents
    > spread around the network.

If you think about it, while in theory the ISP has to manage all that space,
actually, it just needs to have an entry for each customer.
Since it has to have an entry in a database for each customer anyway, a few
more bytes for a prefix isn't that big a deal in the whole scale of things.

[And, an ISP with 2**19 customers is doing quite well, so it can well afford
to manage that size of database :-)]

Unless pushed by some government mandated forced roll, I think that in v6,
ISPs will start to realize it's better to just allocate a prefix to a
customer, and when the customer is gone, never reuse that space until they
run out (LRU).

Michael Richardson <>ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-