Re: [Casm] Possible charter goals and milestones

"Liushucheng (Will)" <> Wed, 15 February 2017 02:42 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BA10E1294E3 for <>; Tue, 14 Feb 2017 18:42:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Status: No, score=-4.21 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, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id nvkt_CTavrRG for <>; Tue, 14 Feb 2017 18:42:02 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B57F612945F for <>; Tue, 14 Feb 2017 18:41:58 -0800 (PST)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id DGM66681; Wed, 15 Feb 2017 02:41:56 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 15 Feb 2017 02:41:54 +0000
Received: from ([]) by ([]) with mapi id 14.03.0235.001; Wed, 15 Feb 2017 10:41:47 +0800
From: "Liushucheng (Will)" <>
To: Benoit Claise <>, "" <>
Thread-Topic: [Casm] Possible charter goals and milestones
Thread-Index: AQHShukHT/ahGRtvKkWC8ytb2VweDaFpUmRw
Date: Wed, 15 Feb 2017 02:41:47 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_C9B5F12337F6F841B35C404CF0554ACB898C37DBSZXEMA509MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A0B0201.58A3BFF5.0011, 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: f47d4b8c24d019e01edf2a3fae4c4eb9
Archived-At: <>
Cc: 'Ying Cheng' <>, 'Xie Chongfeng' <>, 'Rakesh Kumar' <>, "" <>, Marc Blanchet <>, "" <>
Subject: Re: [Casm] Possible charter goals and milestones
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: Wed, 15 Feb 2017 02:42:05 -0000

Hi Benoit and all,

Thanks for your guidance. After offline discussions among all the proponents, we changed the BoF to non-WG forming in the wiki.

We also added the purpose of the BoF in the description:
The purpose of the BoF is to gather a common set of requirements from a larger set of operators and, if needed, possible protocol work milestones and scope.

I’m copying the updated version below for your convenience.


Coordinated Address Space 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 coordinated management of IP addresses, including SDN/NFV networks and other forms of virtualization. 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). The purpose of the BoF is to gather a common set of requirements from a larger set of operators and, if needed, possible protocol work milestones and scope.

  *   Agenda
     *   Problem statement and use cases
     *   Requirements and framework
     *   Possible charter goals and milestones
     *   Next steps
  *   Status: non-WG Forming
  *   Responsible AD: OPS (Benoit Claise, Joel Jaeggli, Warren Kumari)
  *   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:
     *   ​<>
     *   ​<>
     *   ​<>
     *   ​<>
     *   ​<>


Will (LIU Shucheng)

From: CASM [] On Behalf Of Benoit Claise
Sent: Wednesday, February 15, 2017 1:37 AM
Subject: [Casm] Possible charter goals and milestones

Dear all,

"Possible charter goals and milestones" is mentioned in the BoF Wiki, but I fail to see which deliverables you have in mind, next to the framework?
Is/are your deliverable(s) based on draft-sun-i2apm-address-pool-management-yang, so (a) YANG module(s) that would specify the interface and facilitate the automation?
The BoF WIKI mentions "WG forming", but without a clear view on those deliverables, that's difficult.

Tough question: If the solution is this YANG module, based on draft-sun-i2apm-address-pool-management-arch, should we jump directly to the solution? In other words, what is the BoF added value? Note: I thought that those two drafts received some (mild) support in OPSAWG already in IETF 94.

If one of your deliverables is about the DHCP protocol, then I hope we all agree that it should be done in the dhc WG.

Regards, Benoit