Re: [Casm] Which interfaces does CASM plan on standardizing?

Declan Ma <madi@zdns.cn> Thu, 02 March 2017 16:35 UTC

Return-Path: <madi@zdns.cn>
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 7D6C112956C for <casm@ietfa.amsl.com>; Thu, 2 Mar 2017 08:35:12 -0800 (PST)
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, SPF_PASS=-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 aMt3CAjNY6Wx for <casm@ietfa.amsl.com>; Thu, 2 Mar 2017 08:35:08 -0800 (PST)
Received: from gw1.turbomail.org (gw1.turbomail.org [159.8.83.126]) (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 E6B0512946A for <CASM@ietf.org>; Thu, 2 Mar 2017 08:35:07 -0800 (PST)
X-TM-DID: 9d5f31037ad57d532448ff9210a47a1f
Content-Type: text/plain; charset=gb2312
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Declan Ma <madi@zdns.cn>
In-Reply-To: <F8C2270D-231F-4B87-921C-4A6C8AF415EA@viagenie.ca>
Date: Fri, 3 Mar 2017 00:30:34 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <8CA8B4F9-8A9C-433B-8B78-EE51CC955EF8@zdns.cn>
References: <F8C2270D-231F-4B87-921C-4A6C8AF415EA@viagenie.ca>
To: Marc Blanchet <marc.blanchet@viagenie.ca>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/SVp1g3N5-EsdGmimtOS-qcHBcA4>
Cc: "CASM@ietf.org" <CASM@ietf.org>
Subject: Re: [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: Thu, 02 Mar 2017 16:35:12 -0000

Marc,

I would like to provide a sort of need that should be met in the IPAM solution provided by my company, as a quick followup of today’s tele-meeting.

ZDNS provides IPAM solutions to many large-scale enterprises other ISP, such as State Grid in China, PetroChina.

In addition to the interactions with Logs, Address Pool Management and BSS, IPAM offered by ZDNS are expected by our customers to interface with their Firewalls, Traffic Engineering System, even their OA System and so on.

All those interfaced systems, typically are provided by third parties who are happy to see IPAM solutions provide standardized interfaces unanimously. 


Declan(Di) Ma

ZDNS

http://en.zdns.cn


> 在 2017年3月2日,22:56,Marc Blanchet <marc.blanchet@viagenie.ca> 写道:
> 
> 
> _______________________________________________
> CASM mailing list
> CASM@ietf.org
> https://www.ietf.org/mailman/listinfo/casm