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

"Xie Chongfeng" <xiechf.bri@chinatelecom.cn> Wed, 15 February 2017 14:10 UTC

Return-Path: <xiechf.bri@chinatelecom.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 9FD1B12961B for <casm@ietfa.amsl.com>; Wed, 15 Feb 2017 06:10:38 -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, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-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 CJnJezIRJ7k8 for <casm@ietfa.amsl.com>; Wed, 15 Feb 2017 06:10:35 -0800 (PST)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.222]) by ietfa.amsl.com (Postfix) with ESMTP id 74303129607 for <casm@ietf.org>; Wed, 15 Feb 2017 06:10:25 -0800 (PST)
HMM_SOURCE_IP: 172.18.0.92:55386.123341668
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-114.250.172.214 (unknown [172.18.0.92]) by chinatelecom.cn (HERMES) with ESMTP id 69371280029; Wed, 15 Feb 2017 22:09:50 +0800 (CST)
Received: from ip<114.250.172.214> ([172.18.0.92]) by App0021(MEDUSA 0.0.0.0) with ESMTP id 02fe818b-1a98-443d-8ac6-b9ac608ede45 for marc.blanchet@viagenie.ca; Wed Feb 15 22:10:20 2017
0/X-Total-Score: 0:
X-FILTER-SCORE: to=<8e8293844f838d828f8489869561978a8288868f8a864f8482>, score=<14871678206yijklmqT55555655y55i5psW4ADGykgggggpggsggWg>
X-Real-From: xiechf.bri@chinatelecom.cn
X-Receive-IP: 172.18.0.92
X-MEDUSA-Status: 0
Date: Wed, 15 Feb 2017 22:09:51 +0800
From: "Xie Chongfeng" <xiechf.bri@chinatelecom.cn>
To: "marc.blanchet@viagenie.ca" <marc.blanchet@viagenie.ca>, bclaise <bclaise@cisco.com>, "CASM@ietf.org" <CASM@ietf.org>
References: <2111FF63-4AAA-4C50-8358-39CD55397D82@juniper.net>, <B39211B7-A3CD-4C94-B5CF-470EB319244A@viagenie.ca>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 7, 166[cn]
Mime-Version: 1.0
Message-ID: <2017021522094618095419@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart555242301083_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/Bd8WsKGPd48F6vWhzqBNi9w7zWA>
Cc: "lichen.bri@chinatelecom.cn" <lichen.bri@chinatelecom.cn>, "'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: Wed, 15 Feb 2017 14:10:38 -0000

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