Re: [Casm] [homenet] prefix assignment

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 29 March 2017 21:41 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: casm@ietfa.amsl.com
Delivered-To: casm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 529F9129465; Wed, 29 Mar 2017 14:41:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 dOb4eZtLl9LF; Wed, 29 Mar 2017 14:41:47 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D5CB12948C; Wed, 29 Mar 2017 14:41:46 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 6CA89203B0; Wed, 29 Mar 2017 18:05:41 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 92365636E0; Wed, 29 Mar 2017 17:41:45 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Juliusz Chroboczek <jch@irif.fr>
cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, Mark Townsley <townsley@cisco.com>, homenet@ietf.org, casm@ietf.org, anima@ietf.org
In-Reply-To: <87r31fhk0d.wl-jch@irif.fr>
References: <21984.1490644275@obiwan.sandelman.ca> <CANMVOuzYpcBdG2ZOhEXRnQU0Q=_i0i-09SPKzruJnznVoWW=OA@mail.gmail.com> <9240.1490649148@obiwan.sandelman.ca> <672bec4c-0e93-362c-21bf-99938cd0a066@gmail.com> <27800.1490654163@obiwan.sandelman.ca> <27680a33-708d-84b7-f378-3a47ee71840a@gmail.com> <2491.1490716597@obiwan.sandelman.ca> <5a41375c-2a4c-d5ca-e703-06d8e76f8728@gmail.com> <28218.1490799848@obiwan.sandelman.ca> <a34d8ff0-b2d1-b74c-2fd7-00e269b834ed@gmail.com> <14579.1490818588@obiwan.sandelman.ca> <53a40584-bc26-e7ec-e4c9-e76c86dcec03@gmail.com> <87r31fhk0d.wl-jch@irif.fr>
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:41:45 -0400
Message-ID: <1636.1490823705@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/KIT-XlfFh4kEcBzNey4GDM4XmBA>
Subject: Re: [Casm] [homenet] prefix assignment
X-BeenThere: casm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Coordinated Address Space Management <casm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/casm>, <mailto:casm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/casm/>
List-Post: <mailto:casm@ietf.org>
List-Help: <mailto:casm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/casm>, <mailto:casm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Mar 2017 21:41:49 -0000

Juliusz Chroboczek <jch@irif.fr> wrote:
    >> There's already a thing called an HNCP agent. Why couldn't
    >> it be enhanced to negotiate with an upstream ASA for resources?

    > Could you please clarify what you mean by "negotiate"?  Current HNCP
    > implementations are provided with a bunch of External Prefixes, which they
    > then carve into /64, one per prefix.  Are you envisioning a scenario where
    > the HNCP implementation actually performs active negotiation on its
    > external interfaces?

Yes, that's what Brian is suggesting.
The HNCP daemon would speak GRASP ASA on the "northbound" interface.
It wouldn't necessarily speak HNCP.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-