Re: [Casm] prefix assignment

Brian E Carpenter <> Wed, 29 March 2017 23:12 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A01EB1296BF; Wed, 29 Mar 2017 16:12:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id j4-15ZYqhCar; Wed, 29 Mar 2017 16:12:46 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4001:c0b::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 56D7012969C; Wed, 29 Mar 2017 16:12:42 -0700 (PDT)
Received: by with SMTP id 190so11437448itm.3; Wed, 29 Mar 2017 16:12:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=8CGAL/RuUywWYk2fEbxCeGAyc+X0KJBT/AlqCrec1Mc=; b=QI+SpNfF8UzkJiBoPsDp1NzqBvVyhawTPqHJj0z27tRy0dg/r4vsgChIfMGY4HNk0B IVu91fMRHZBZGtsu4gT33u0dFJUs2dN0dvh4gQxPkFGbKR1zoQ+h8RwFcFSaZFeXYnlF O65EY3pGfA7fEkvJQ1HD6dAb5LsSz9xjR8rlWz+XTkhIh65tutJQLfRl6iUd8L9NbvST uRql75OBB4fIdF1xFWyLHkFXcCOYLmuayfu4+YGNOnafok5TTZjRcs5QmS8k4qMQLzqN LfXzHZZ1HjjzFOkVwPb0JtM1Ovr1HDiJY3ZfQIO9cBYYB+nR1o9ZWb/WdmW7LEEpyZHA ZHFg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=8CGAL/RuUywWYk2fEbxCeGAyc+X0KJBT/AlqCrec1Mc=; b=Dk/9QCBK7xZqSmiZOA/HC+B7j8O2WfHJBqXDAlmSvRafqaY68dnX1LRps6jbyXgkiZ WiS9xvPAEEui/eWsYqzdlzorXqRNGpDjOUDBlq+H3nucvoyhB+F0944Tnzq4l0Rjgt9Y gVAhSC2vzp7dw1xk3xAU0s7lw1iZOB4GQItA9HvsmixHVQMqym6uLD8vgA5Owek5Fj75 PcA9agXsJX8S38gjiKZVsXWNTmJ2qFPjIZEemo9qZWeXH1FGuOVcg0ix6DBowAxw5K1E y+ial8w6CwiQa+XqbVJ2TaoRNhxPFgOoLK79eSjwBzjNvZMKzMLtUQLgfScMDpTD7SOl jwzQ==
X-Gm-Message-State: AFeK/H22XYpG5UA0lhKOKrFLpG7b4h7fHbp1j97RasDf8fPhstD6qMdecbWZvz/tMj4qTg==
X-Received: by with SMTP id x9mr1160426itb.102.1490829161628; Wed, 29 Mar 2017 16:12:41 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:128:28cc:dc4c:9703:6781? ( [2001:67c:370:128:28cc:dc4c:9703:6781]) by with ESMTPSA id b25sm433380iod.32.2017. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Mar 2017 16:12:41 -0700 (PDT)
To: Michael Richardson <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <>
Cc:,, Mark Townsley <>,
From: Brian E Carpenter <>
Organization: University of Auckland
Message-ID: <>
Date: Thu, 30 Mar 2017 12:12:41 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
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 23:12:49 -0000

On 30/03/2017 10:38, Michael Richardson wrote:
> 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.

All true. But it isn't designed for negotiation as far as I know,
just a request/response.
> I would love to request address space via ASA from the DHCPv6 server.
> That would all happen within the ISP's ACP though.

Agreed, that is a little higher up the food chain. Maybe that is as close
to the user as an ASA will get. I don't really care; I just wanted to
explore the way we might fit our various tools together.

> 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
> finishing.

Yes, indeed, and then we could discuss how the radius server gets new
address space when it runs out.
> 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.

Yes, by defining a full set of relevant objectives.