[Casm] Which interfaces does CASM plan on standardizing?

Benoit Claise <bclaise@cisco.com> Tue, 14 February 2017 17:30 UTC

Return-Path: <bclaise@cisco.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 9DEE51296D2 for <casm@ietfa.amsl.com>; Tue, 14 Feb 2017 09:30:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 HwKhrsipiV6d for <casm@ietfa.amsl.com>; Tue, 14 Feb 2017 09:29:50 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3669612941A for <CASM@ietf.org>; Tue, 14 Feb 2017 09:29:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7212; q=dns/txt; s=iport; t=1487093390; x=1488302990; h=to:from:subject:message-id:date:mime-version; bh=Ng/Gg8JghIa/naiA/BsYBZjq6RWxzibWG30oRAN1YNM=; b=MGfLYDBtwOcCRbfDjzEF5bvJSE7Ef9GfmFwbl1t1HUXSAc0Ngjmc6Y9x ynXGeHCwiCRjpDFIRCyGt0uraSe74ECFYHA2h3zEJam1lO3obyHrE1j/Y Wf6y2gtV4ilYo9sFbxa/f9sxcy+7SHUTe2/1SmcTYbMIGa+p1D+REIC1D c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BTCAC/PaNY/xbLJq1eHAEBBAEBCgEBh?= =?us-ascii?q?DMDJ1+DWYp6oSiDHYQbKoIdAYMQgwwUAQIBAQEBAQEBYh0LhRMxgQICXw0IAQG?= =?us-ascii?q?JZw6fKZABgiUrizQBAQEBBgEBAQEfBYZMggWHIQEBBYMcgl8FiQySZoFPkEWKP?= =?us-ascii?q?4ZGixCIBTYhVSsgFAgVFYcBPzUBh3KCLQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.35,162,1484006400"; d="scan'208,217";a="649639762"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Feb 2017 17:29:46 +0000
Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v1EHTjUW014523 for <CASM@ietf.org>; Tue, 14 Feb 2017 17:29:46 GMT
To: "CASM@ietf.org" <CASM@ietf.org>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <82fe1b7a-995b-9fdf-ec28-424ca1cef884@cisco.com>
Date: Tue, 14 Feb 2017 18:29:44 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------C6DF6F4587AAA47B1AB750EE"
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/IuL5Kn9H6EWLvBFwzvrFsni18Mc>
Subject: [Casm] Which interfaces does CASM plan on standardizing?
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: Tue, 14 Feb 2017 17:30:01 -0000

Dear all,

Joel, Warren, and I have been discussing CASM.

Reading the two drafts, and we're wondering...

        draft-kumar-casm-problem-and-use-cases-00: This document describes evolution of IPAM into a
        standardized_interfaces _for centralized management of IP addresses.

        draft-kumar-casm-requirements-and-framework-00: There is a pressing need to define a new address management system
        which can meet these diverse set of requirements.  Such a system must
        be built with well defined_interfaces _so users can easily migrate
        from one vendor to another without rewriting their network management
        systems.

We see static address, public IP address pool, multicast IP address 
pool, pool initializing or resizing, etc.
We see DHCP server, DNS server, NAT service. And I guess there are 
controllers up there somewhere.
So which interfaces does CASM plan on standardizing?

         +----------------+ +------+ +----+ +-----+ +-----------------------+
         |Interface for   | |SDN/  | |OSS/| |ADMIN| |Interface for logs,    |
         |managing address| |Legacy| |BSS | |     | |DHCP, DNS, NAT, Address|
         |space and pools | |      | |    | |     | |allocation records     |
         +--------+-------+ +--+---+ +-+--+ +--+--+ +----------+------------+
                  |            |       |       |               ^
                  |            |       |       |               |
                  |            |       |       |               |
                  |            |       |       |               |
                  v            v       v       v               |
         +---+------------+-------+-------+---------------+------+
         |    Address Space Management (IPAM) System             |
         |      +-----------+ +----------+ +--------+            |
         |      | Pool      | |Address   | |Database|            |
         |      | Management| |Management| |        |            |
         |      +-----------+ +----------+ +--------+            |
         |                                                       |
         +-------------------------+-----------------------------+
                     |
         +-----------v------------+
         |Address Helper Plug|ins |
         +----+--+------+-----+---+
           |  |         |     |--------------------+
           |  +----+    |                          |
           |       |     ------------+             |
           v       +----|            |             |
         +--------+    +-----+  +----------+   +--------+
         | DNS    |    |NAT  |  |  Address |   | DHCP   |
         | Servers|    |     |  |  Mapping |   | Servers|
         |        |    |     |  |  Systems |   |        |
         +--------+    +-----+  +----------+   +--------+

All of them in this figure? A subset of those interfaces?
This group should be clear what it plans on working on.
And which IPAM vendors are involved in CASM, for a definition of IPAM 
related to this figure?

Note: similar comments as last time btw. See 
https://www.ietf.org/mail-archive/web/opsawg/current/msg04613.html

Regards, Benoit