[Casm] minutes of CASM meeting on March 22

"Pengtao (Tony)" <dr.pengtao@huawei.com> Thu, 23 March 2017 02:18 UTC

Return-Path: <dr.pengtao@huawei.com>
X-Original-To: casm@ietfa.amsl.com
Delivered-To: casm@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id C335D1294F3 for <casm@ietfa.amsl.com>; Wed, 22 Mar 2017 19:18:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id wXLgIoFfr4Wf for <casm@ietfa.amsl.com>; Wed, 22 Mar 2017 19:18:53 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7777B129426 for <casm@ietf.org>; Wed, 22 Mar 2017 19:18:52 -0700 (PDT)
Received: from (EHLO lhreml703-cah.china.huawei.com) ([]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DDG69924; Thu, 23 Mar 2017 02:18:49 +0000 (GMT)
Received: from SZXEMI415-HUB.china.huawei.com ( by lhreml703-cah.china.huawei.com ( with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 23 Mar 2017 02:18:48 +0000
Received: from SZXEMI508-MBS.china.huawei.com ([]) by SZXEMI415-HUB.china.huawei.com ([]) with mapi id 14.03.0235.001; Thu, 23 Mar 2017 10:18:45 +0800
From: "Pengtao (Tony)" <dr.pengtao@huawei.com>
To: "casm@ietf.org" <casm@ietf.org>
Thread-Topic: minutes of CASM meeting on March 22
Thread-Index: AdKje8q53j7mJvZQQq6PitSRL7Yqbg==
Date: Thu, 23 Mar 2017 02:18:45 +0000
Message-ID: <4B6E5970C6957B4E8EF9A3935B4070B363428C@SZXEMI508-MBS.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
x-originating-ip: []
Content-Type: multipart/mixed; boundary="_004_4B6E5970C6957B4E8EF9A3935B4070B363428CSZXEMI508MBSchina_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090206.58D3308A.00AB, ss=1, re=0.000, recu=0.000, reip=0.000, vtr=str, vl=0, cl=1, cld=1, fgs=0, ip=, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 9cbcd3e4db51471b376460b8ec40e5c8
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/v_EPN7C0kn5mIt0xlj7bAHCCLjM>
Subject: [Casm] minutes of CASM meeting on March 22
X-BeenThere: casm@ietf.org
X-Mailman-Version: 2.1.22
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, 23 Mar 2017 02:18:56 -0000

Hi all,

Please find the minutes of yesterday’s WebEx meeting below.


Tao PENG (Tony), Ph.D.
Senior Researcher
Huawei Technologies Co.,Ltd

Minutes CASM 2017/3/22
Host: Marc Blanchet
Agustin Formoso
Benoit Claise
Telecom Italia: Giuseppe Fioccola
ZDNS: Declan Ma
China Telecom:  Chen Li, Chongfeng Xie
China Unicom: Ying Cheng
Huawei: (David) Weiping XU, Will Liu, (Tony)

Marc: it is not yet clear about the scope and deliverables.

Li explained the draft “casm-pool-management-arch” - address management procedure and showed slides to explain the architecture.

Marc: Architecture in Figure 1 seems from Rakesh, which is broader. We need to get things converged.

Benoit: what you explained seems to be a subset.

Ma: you may also consider the RPKI system (Resource Public Key Infrastructure). After the prefixes are allocated, certificates need to be generated. This should connect with IPAM.

Benoit: what are the building blocks that you touch in the figure (slide 2)?

Xie: the south bound of ASMS system should be defined and standardized. A portal may be used for address configuration. A north bound interface could be defined.

Benoit: what is the flow among these entities (DHCP message/Yang?).

Xie: if we deploy centralized interface, there is only interaction between BNG and our management server. Currently, there is no management server; the configuration is done on BNG.

Benoit: I see disconnection between requirement and current implementation, which is a subset.

Xie: this architecture can cover several use cases. For example, it can be used on DHCP configuration, IPTV.

Benoit: do these people want to work on the full scope, or the scope is to only have BNG interaction?

Xie: address allocation in the cloud may be considered in the architecture. It is very important; some automatic mechanisms can be used.

Giuseppe: dynamic service creation could be an important use case. The application is crucial.

Liu: I was looking at the draft from Rakesh. Chen Li addressed most of the scenarios in Rakesh’s draft.

Benoit: how the use cases are covered by your draft? What is the current interaction flow from operator to network elements (BNG/DHCP…)? Do we have meeting agenda?

1, identify the details on south/north bound interfaces
2, show how the use cases are covered
3, consider the interaction flow of Address Space Management & Control
4, chairs decide the topics during BoF
5, start a thread to find a timeslot for a meeting on Sunday for better preparation