Re: [Casm] CASM BoF request just posted to BoF wiki

"Liushucheng (Will)" <> Fri, 10 February 2017 03:05 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BB221129538 for <>; Thu, 9 Feb 2017 19:05:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Status: No, score=-4.221 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] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Er_9UsIw8luf for <>; Thu, 9 Feb 2017 19:05:04 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7762E129525 for <>; Thu, 9 Feb 2017 19:05:03 -0800 (PST)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id DGD85883; Fri, 10 Feb 2017 03:05:01 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.301.0; Fri, 10 Feb 2017 03:05:00 +0000
Received: from ([]) by ([]) with mapi id 14.03.0235.001; Fri, 10 Feb 2017 11:04:56 +0800
From: "Liushucheng (Will)" <>
To: "" <>, "" <>
Thread-Topic: [Casm] CASM BoF request just posted to BoF wiki
Thread-Index: AdKCiHMMgNp6ZUuET/qq14mhMlioJgAIhcIAACe7GgA=
Date: Fri, 10 Feb 2017 03:04:55 +0000
Message-ID: <>
References: <> <09b401d282ed$9bced850$d36c88f0$>
In-Reply-To: <09b401d282ed$9bced850$d36c88f0$>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_C9B5F12337F6F841B35C404CF0554ACB898C19C5SZXEMA509MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020206.589D2DDD.01E9, ss=1, re=0.000, recu=0.000, reip=0.000, 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: 28c0e01c9ffe1a6a4ee251a2c281cf42
Archived-At: <>
Subject: Re: [Casm] CASM BoF request just posted to BoF wiki
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Centralized Address Space Management <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 10 Feb 2017 03:05:05 -0000

Hi Adrian and all,

Thanks for your comments. The proponents discussed and agreed with “coordinated”.

However, seems we missed the “Space” in title ?  Should be *“Coordinated Address Space Management”* instead of “Coordinated Address Management”. I  just fixed this on wiki.

Will (LIU Shucheng)

From: Adrian Farrel []
Sent: Friday, February 10, 2017 12:00 AM
To: Liushucheng (Will) <>om>;
Subject: RE: [Casm] CASM BoF request just posted to BoF wiki

Thanks for posting this ahead of time, Will. It's helpful to be able to read it and think about it.

Picking up on a point raised on the list and using Joel's suggestion...

Do you want to change "Centralized Address Management (CASM)" to "Coordinated Address Management (CASM)"? That does not preclude centralized solutions, but it also allows some degree of delegation as suggested by Brian.


From: CASM [] On Behalf Of Liushucheng (Will)
Sent: 09 February 2017 03:56
Subject: [Casm] CASM BoF request just posted to BoF wiki

Hi all,

I’m writing to notify you that the CASM BoF request was just posted in the bof wiki.
Many thanks for the efforts from Marc, Adrian, Rakesh and Chongfeng.

Please help to review it and let us know your thoughts. I’m copying it below.


Centralized Address Management (CASM)
·     Description: Organizations use IP Address Space Management (IPAM) tools to manage their IP address space, often with proprietary database and interfaces. This work intends to evolve IPAM into standardized interfaces for centralized management of IP addresses, specially in the context of SDN/NFV networks. Use cases include dynamic allocation and release of IP addresses and prefixes based on usage (reallocation in case of no more in use) and/or user intent (for specific services).
·     Agenda
o  Problem statement and use cases
o  Requirements and framework
o  Possible charter goals and milestones
o  Next steps
·     Status: WG Forming
·     Responsible AD: OPS (Benoit Claise, Joel Jaeggli)
·     BoF proponents: Chongfeng Xie(China Telecom), Rakesh Kumar (Juniper), Ying Cheng(China Unicom), Will Liu(Huawei)
·     BoF chairs: TBD
·     Number of people expected to attend: 100
·     Length of session (1, 1.5, 2, or 2.5 hours): 1.5 hours
·     Conflicts to avoid (whole Areas and/or WGs): intarea, opsawg, anima, supa, dhc, nfvrg
·     Mailing List: ​​<>
·     Draft charter: TBD
·     Relevant drafts:
o  ​<>
o  ​<>
o  ​<>
o  ​<>
o  ​<>

Will (LIU Shucheng)