Re: [Casm] prefix assignment

Michael Richardson <> Wed, 29 March 2017 21:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 76FE91293EE; Wed, 29 Mar 2017 14:38:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id pKoT4lbMrvUk; Wed, 29 Mar 2017 14:38:56 -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 B8BB71250B8; Wed, 29 Mar 2017 14:38:56 -0700 (PDT)
Received: from ( [IPv6:2607:f0b0:f:2::247]) by (Postfix) with ESMTP id 8C9D6203B0; Wed, 29 Mar 2017 18:02:51 -0400 (EDT)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id B6D69636E0; Wed, 29 Mar 2017 17:38:55 -0400 (EDT)
From: Michael Richardson <>
To: Brian E Carpenter <>
cc:,, Mark Townsley <>,
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, 29 Mar 2017 17:38:55 -0400
Message-ID: <>
Archived-At: <>
Subject: Re: [Casm] prefix assignment
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Coordinated Address Space Management <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 29 Mar 2017 21:38:58 -0000

Brian E Carpenter <> wrote:
    >> I just don't see the point of the ASA here.

    > There's already a thing called an HNCP agent. Why couldn't
    > it be enhanced to negotiate with an upstream ASA for resources?

Because it's already done. It's called DHCPv6.
It already has extensive running code :-)
It's not even that complex.

I would love to request address space via ASA from the DHCPv6 server.
That would all happen within the ISP's ACP though.

Right now (on DSL lines), the address space mostly comes via radius.
Which is to say that the problem has been centralized by MBS builders into
being someone else's problem. Advertising the address space is often done by
OSPFv3, but there are additional things that would be easier for the DHCPv6
server to do, such as the DNS delegations that homenet is working on

I think that CASM could very nicely define/extend the prefix ASA to deal with
DNS reverse names, and as the RIRs (George) said, better link the delegated
prefix to clear ownership records.

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