Re: [Casm] I-D Action: draft-kumar-casm-requirements-and-framework-00.txt

joel jaeggli <joelja@bogus.com> Wed, 08 February 2017 05:02 UTC

Return-Path: <joelja@bogus.com>
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 31072129956 for <casm@ietfa.amsl.com>; Tue, 7 Feb 2017 21:02:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 hxAE3gqYy52B for <casm@ietfa.amsl.com>; Tue, 7 Feb 2017 21:02:09 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CEA0129954 for <casm@ietf.org>; Tue, 7 Feb 2017 21:02:09 -0800 (PST)
Received: from mb-3.local (c-73-202-177-209.hsd1.ca.comcast.net [73.202.177.209]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id v18527PB066829 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Wed, 8 Feb 2017 05:02:08 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host c-73-202-177-209.hsd1.ca.comcast.net [73.202.177.209] claimed to be mb-3.local
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, casm@ietf.org
References: <148579530142.29779.15228003608361236038.idtracker@ietfa.amsl.com> <45ac9aef-907b-5a9d-7d07-fc8c54c3806d@gmail.com>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <74fb7dd8-a3c0-f4e6-7fb7-16017e86d6bc@bogus.com>
Date: Tue, 07 Feb 2017 21:02:02 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <45ac9aef-907b-5a9d-7d07-fc8c54c3806d@gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="jC1r1LDnxc71e8TJ2VUu5RxeQQHl3hn7u"
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/DEa98FlfBj5djz7FgZ0TKTm5cWI>
Subject: Re: [Casm] I-D Action: draft-kumar-casm-requirements-and-framework-00.txt
X-BeenThere: casm@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Centralized 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, 08 Feb 2017 05:02:11 -0000

On 2/7/17 7:40 PM, Brian E Carpenter wrote:
> Hi,
> 
>> This document describes evolution of IPAM into a
>> standardized interfaces for centralized management of IP addresses.
> 
>> CASM:   Centralized Address Space Management
> 
> Please delete 'centralized'. It isn't necessary (as mentioned in my
> previous message) and it has the effect of limiting the range of
> solutions that can be considered. I will consider the document as
> if this word does not appear...

Coordinated if you like.

> And in fact I like the draft. I simply observe that this part of the model:
> 
>         +---+------------+-------+-------+---------------+------+
>         |    Address Space Management (IPAM) System             |
>         |      +-----------+ +----------+ +--------+            |
>         |      | Pool      | |Address   | |Database|            |
>         |      | Management| |Management| |        |            |
>         |      +-----------+ +----------+ +--------+            |
>         |                                                       |
>         +-------------------------+-----------------------------+
> 
> *does not need to be centralized* except for two points: providing
> the initial pool to the distributed system, and providing policy
> intent to the distributed system.
> 
> And there's a draft describing a distributed solution, for a subset
> of the problem space:
> https://tools.ietf.org/html/draft-ietf-anima-prefix-management-02
> I understand that it's too soon for this list to discuss solutions,
> but I really do want the distributed approach to be on the table, since
> this is one of the early use cases for the Anima WG.
> 
> Regards
>    Brian Carpenter
> 
> _______________________________________________
> CASM mailing list
> CASM@ietf.org
> https://www.ietf.org/mailman/listinfo/casm
>