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

Benoit Claise <bclaise@cisco.com> Tue, 28 February 2017 21:16 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 9C405124281; Tue, 28 Feb 2017 13:16:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.512
X-Spam-Level:
X-Spam-Status: No, score=-14.512 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, T_KAM_HTML_FONT_INVALID=0.01, 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 Fn3FJQQ3sGPJ; Tue, 28 Feb 2017 13:16:10 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCAFE1296FD; Tue, 28 Feb 2017 13:16:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18644; q=dns/txt; s=iport; t=1488316570; x=1489526170; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=AionFtC2JlaYpOl6JFn5q7djUMnhSzpG63xH67+felg=; b=M24HrgYXm5E77HXr+YSAwq1KJO1sZFwLQrddAMtUiboTOfL/P2G3N2+c xCeRJOTO3CuGrZ67lG5Po3IU7h9DBzUhT1M/edTqyHfrHOjF2fKvvdBhS klh87g1ZCAMgRasYH2d7zxMTqlrnt4zKXqaUWUwb1xEQdtdISA/Dza/jy w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CPFAAu6LVY/xbLJq0aA0AZAQEBAQEBA?= =?us-ascii?q?QEBAQEHAQEBAQGCboFDAydfg1uKe5BxiAyHfVGGaB8BDIIwg0YCgnAVAQIBAQE?= =?us-ascii?q?BAQEBYiiEcAEBAQMBAQEhMRMHBgUFCwkCEQECAQIBJwMCAiEGHwMDAwgGAQwGA?= =?us-ascii?q?gEBiVsDDQgOknx9nViCJiuHEA2DXgEBAQEBAQEBAQEBAQEBAQEBAQEBARgFhky?= =?us-ascii?q?CBYJqglGBbR4YFoJQgl8FiRaGPYYehXg6hnSDJoNuhCSBe4UggzCGTYpKX4gJN?= =?us-ascii?q?SKBASEUCBcVPoZOPzUBiW8BAQE?=
X-IronPort-AV: E=Sophos;i="5.35,221,1484006400"; d="scan'208,217";a="652882206"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Feb 2017 21:16:02 +0000
Received: from [10.61.165.123] ([10.61.165.123]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v1SLG0oC026751; Tue, 28 Feb 2017 21:16:01 GMT
To: Xie Chongfeng <xiechf.bri@chinatelecom.cn>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "marc.blanchet@viagenie.ca" <marc.blanchet@viagenie.ca>, "CASM@ietf.org" <CASM@ietf.org>
References: <2111FF63-4AAA-4C50-8358-39CD55397D82@juniper.net> <B39211B7-A3CD-4C94-B5CF-470EB319244A@viagenie.ca> <2017021522094618095419@chinatelecom.cn> <1aed9ffa-5c0f-40ea-6afd-0af58930961a@gmail.com> <2017022809122853035318@chinatelecom.cn>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <216b9239-592a-a22c-aa43-889a2872300e@cisco.com>
Date: Tue, 28 Feb 2017 21:47:37 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <2017022809122853035318@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="------------47CBCF36F8EBC9B1591C5061"
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/6ggGaq_D6ve_F0otgmnzxRTWSi0>
Cc: "lichen.bri@chinatelecom.cn" <lichen.bri@chinatelecom.cn>, draft-ietf-anima-prefix-management <draft-ietf-anima-prefix-management@ietf.org>, "'Liushucheng \(Will\)'" <liushucheng@huawei.com>, "wanghn.bri@chinatelecom.cn" <wanghn.bri@chinatelecom.cn>
Subject: Re: [Casm] =?utf-8?q?Which_interfaces_does_CASM_plan_on_standardizing?= =?utf-8?b?P++BoQ==?=
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, 28 Feb 2017 21:16:18 -0000

Hi Chongfeng,
> Hi,  Carpenter,
>
> It is nice to receive your comments. 
>
> CASM and ANIMA differ with each otherin the following aspects.
>
> Firstly, ANIMA is a self-managing in
> AUTONOMIC networking environment, the configurations to network elements
> are mainly done by the network elements themselves. while in CASM, in order 
>
> to make the task easier, we propose the use centralizedserver or platform to do 
>
> the configuration task, of course, the server may be distributed physically. 
>
>
>
> Secondly, they have different use case, more the 3
> years ago, I had a long talk with Dr. Jiang Sheng in Beijing, and propose
> that the IP RAN may be a suitable use case to ANIMA, although the name
> didn't exist yet.  the primary use case for CASM is the address pool
> configuration for broadband IP network, CT has implemented the whole system 
>
> based on the current CASM dratfs, and 3 vendors have joined the field test 
>
> last year. The field trial prove this approach can solve the issues we
> are concernd with.
>
> The detailed description of the interface is shown in,
> https://datatracker.ietf.org/doc/draft-sun-i2apm-address-pool-management-yang/
3 vendor implementations. Great. That's a lot of experience.
So the end goal is to standardize this 
draft-sun-i2apm-address-pool-management-yang draft?
You had some support for this in OPSAWG for a WG document, if I recall 
correctly...
Or maybe you learned from this development experience?

Regards, Benoit

>
>
> Thank you!
>
> Chongfeng
>
>
> ------------------------------------------------------------------------
> xiechf.bri@chinatelecom.cn
>
>     *发件人:* Brian E Carpenter <mailto:brian.e.carpenter@gmail.com>
>     *发送时间:* 2017-02-28 07:54
>     *收件人:* Xie Chongfeng <mailto:xiechf.bri@chinatelecom.cn>;
>     marc.blanchet@viagenie.ca <mailto:marc.blanchet@viagenie.ca>;
>     bclaise <mailto:bclaise@cisco.com>; CASM@ietf.org
>     <mailto:CASM@ietf.org>
>     *抄送:* lichen.bri@chinatelecom.cn
>     <mailto:lichen.bri@chinatelecom.cn>; 'Liushucheng (Will)'
>     <mailto:liushucheng@huawei.com>; wanghn.bri@chinatelecom.cn
>     <mailto:wanghn.bri@chinatelecom.cn>;
>     draft-ietf-anima-prefix-management
>     <mailto:draft-ietf-anima-prefix-management@ietf.org>
>     *主题:* Re: [Casm] Which interfaces does CASM plan on standardizing?
>     Hi Chongfeng,
>     > Network operation team needs configure manaually IP address pool
>     in each
>     > BRAS/vBRAS
>     Obviously that is a hopeless task. That's exactly why this is one
>     of the test cases for ANIMA. So can you please comment on the
>     level of detail needed in that interface? Is it similar to
>     https://tools.ietf.org/html/draft-ietf-anima-prefix-management-02#section-6.1
>     That is an example for an IPRAN operator.
>     Note, I'm not asking about technical details - just about the
>     level of abstraction.
>     Regards
>        Brian Carpenter
>     On 16/02/2017 03:09, Xie Chongfeng wrote:
>     >
>     > Hi,Benoit and all,
>     >
>     > This subject was originally raised by China Telecom, our use
>     case is clear and straightforward.  In CT's network, there are
>     tens of thousands of BRAS equipments,which are the major gateway
>     to the broadband users. When the vBRAS was introduced, the volume
>     will be even higher. Network operation team needs configure
>     manaually IP address pool in each
>     > BRAS/vBRAS, which are time-consuming and low -efficient. Can
>     DHCP solve this problem? The answer is NO, since DHCP deals with
>     address allocation for end users.
>     >
>     > In order to autimate the configuration process and improve the
>     IP adress usage, a centralized address pool managment approach may
>     be more reasonable. We discucssed with verdors and carriers, we
>     found that there have been some proprioritary inplementations,
>     they differ in the south-bound interface, so  we propose to
>     standardize the south-bound interface in the early stage, which
>     will benefit to all the players.
>     >
>     > Since the requirements are pressing to CT, we begun the filed
>     trial last year and 3 vendors have implementated the interface
>     defined in draft-sun-i2apm-address-pool-management-yang, luckily
>     they all passed the field test by our joint efforts.
>     >
>     > As mentioned in other drafts of CASM, the address management
>     capability will be  opened to other applications,such as SDN and
>     Cloud , the  north-bound interface will be standanized as well.
>     >
>     > Of course, in order to define the interface and its relatvie
>     workflow, a unified framwork or architecture will need to be
>     defined in advance.
>     >
>     > Thank you!
>     >
>     > Chongfeng Xie
>     >
>     >
>     >
>     >
>     >
>     >
>     > xiechf.bri@chinatelecom.cn
>     >
>     > From: Marc Blanchet
>     > Date: 2017-02-14 20:24
>     > To: Rakesh Kumar
>     > CC: Liushucheng; Xie Chongfeng
>     > Subject: Re: IPAM design from microsoft
>     > will look into it. were you able to get Bloomsberg or else to
>     support the work?
>     > Marc.
>     > On 14 Feb 2017, at 6:57, Rakesh Kumar wrote:
>     > HI,
>     >
>     > I found a very good document on the web from Microsoft about
>     IPAM. This is good document that explains some of the concept we
>     have listed in the drafts.
>     > I thought, you guys might want to take a look at this for your
>     reference.
>     >
>     > Thanks & Regards
>     > Rakesh
>     >
>     >
>     >
>     > _______________________________________________
>     > CASM mailing list
>     > CASM@ietf.org
>     > https://www.ietf.org/mailman/listinfo/casm
>     >
>