Re: [Casm] New Version Notification for draft-li-opsawg-address-pool-management-arch-01

Georgios Karagiannis <> Mon, 16 July 2018 17:47 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9B462130E21; Mon, 16 Jul 2018 10:47:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id x54trjDSGGP2; Mon, 16 Jul 2018 10:47:47 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 51216130E0C; Mon, 16 Jul 2018 10:47:47 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTP id 59083CFA5A2A7; Mon, 16 Jul 2018 18:47:43 +0100 (IST)
Received: from ([]) by ([]) with mapi id 14.03.0399.000; Mon, 16 Jul 2018 18:47:44 +0100
From: Georgios Karagiannis <>
To: "" <>, xiechf.bri <>
CC: "" <>, "" <>
Thread-Topic: [Casm] New Version Notification for draft-li-opsawg-address-pool-management-arch-01
Thread-Index: AQHUEnJkhOmhD7mWgUODb8ZKwg3TVKSSMuIQ
Date: Mon, 16 Jul 2018 17:47:44 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_C5034E44CD620A44971BAAEB372655DC3B018F6Alhreml505mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [Casm] New Version Notification for draft-li-opsawg-address-pool-management-arch-01
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Coordinated Address Space Management <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 16 Jul 2018 17:47:51 -0000

Hi Chen Li,

From what I understand, by using CASM you would like to enhance the operation of IPAM (IP Address Space Management) tools by defining standardized interfaces for a centralized management of IP addresses.

Are you planning to work in IETF on specifying both the interfaces that are mentioned in the draft?

・         CASM App-facing Interface

・         CASM device-facing Interface
If that will be the case are you then planning to use NETCONF/YANG data models?

Are you also willing to prioritize any of these two interfaces?

It might be possible that CASM could work use in addition to the address management attributes also on other attributes, e.g., billing. Are you also willing to consider other attributes  than address management attributes in this work?

Best regards,

From: CASM [] On Behalf Of
Sent: Tuesday, July 03, 2018 4:05 AM
To: casm <>
Cc: lichen.bri <>cn>; Tianran Zhou <>om>; jclarke <>om>; 孙雪媛 <>om>; xiechf.bri <>
Subject: [Casm] New Version Notification for draft-li-opsawg-address-pool-management-arch-01

Hi all,

We have updated the new version of I-D, draft-li-opsawg-address-pool-management-arch-01.txt, the revision was made based on the comments raised in London meeting,
Telecom Italia also provided a new use case afterwards, which was also included in this new draft.

Here is the  link of the draft .  wish for your comments, Thanks.

Best Regards,

Chen Li

Chen  Li
Network Evolution and Planning Center
Network Technology & Planning Department
China Telecom Corporation Limited Beijing Research Institute<>
Tel: +86-10-50902891
Mobile: +86-18910853955