IETF Logo Mail Archive

Re: [Casm] casm proposed charter v20170807

Benoit Claise <bclaise@cisco.com> Fri, 11 August 2017 12:55 UTC

Return-Path: <bclaise@cisco.com>
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 ECAEC132565 for <casm@ietfa.amsl.com>; Fri, 11 Aug 2017 05:55:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 b-tidhAa7y9o for <casm@ietfa.amsl.com>; Fri, 11 Aug 2017 05:55:35 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17F36132547 for <casm@ietf.org>; Fri, 11 Aug 2017 05:55:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11418; q=dns/txt; s=iport; t=1502456135; x=1503665735; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=xB6qfKyEqNN2UjF2eD1atoZFkt3WbYajGXklcMlOy3k=; b=MiqpKNsvKq85UT1D97v5ea+dKoppcbdgL3cnZNDa825c1hLLXWuKpv1K Y7d3YXS3vOTfIsbtue6rbCpgThvfKdtjEoNjeSY5fdyVT6jHkyTdMitue sPo8o1viq9on/13qua5/20qC6behg/QmynQTqnWxxRbzZ4uBIuuYxX8md 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DlAgCIqI1Z/xbLJq1cGQEBAQEBAQEBAQEBBwEBAQEBhD6BFI8DkGYikGKFNQ6CBCEBCoUbAoU/FgECAQEBAQEBAWsohRgBAQEBAgEBAWwXBAsRAQMBASgHJx8DBggGAQwGAgEBiiMIEK1iJ4s7AQEBAQEBAQEBAQEBAQEBAQEBAQEBGAWDKINOgWMrC4JxhD2GKgEEmASIIpQ6i0OHEY0piGomATBZMTIhCBwVSYccPjaKMgEBAQ
X-IronPort-AV: E=Sophos;i="5.41,357,1498521600"; d="scan'208,217";a="696435421"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Aug 2017 12:55:30 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v7BCtTjn022631; Fri, 11 Aug 2017 12:55:30 GMT
To: xiechf <xiechf.bri@chinatelecom.cn>, Marc Blanchet <marc.blanchet@viagenie.ca>, casm@ietf.org
References: <C9B5F12337F6F841B35C404CF0554ACB8AD0FB7A@dggeml509-mbx.china.huawei.com> <5B50136F-27A7-4EDA-A6F0-AEB8002ABC8A@chinatelecom.cn>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <b52ca0d8-d76b-9429-0028-19f705902d8a@cisco.com>
Date: Fri, 11 Aug 2017 14:55:29 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <5B50136F-27A7-4EDA-A6F0-AEB8002ABC8A@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="------------00C2ACF73BF86E2AA7568BC9"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/zC5MffGS-9gSPkMhkv3JHUz40YE>
Subject: Re: [Casm] casm proposed charter v20170807
X-BeenThere: casm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Coordinated 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: Fri, 11 Aug 2017 12:55:38 -0000

Dear all,

While it's good to discuss charter text, let's not forget that 
discussing CASM open issues on the mailing list and developing drafts is 
important. Even more important. Feel free to self organize: no need to 
wait for a WG for that.

Regards, Benoit
>
> Hi, Marc,
>
> I think the charter text you proposed is fine.  I also made some small 
> modifications which is in red as below.
>
> Thank you!
>
> Chongfeng
>>
> Coordinated Address Space Management (CASM) Proposed Charter, v20170807
>
> Organizations use IP Address Space Management (IPAM) tools to manage 
> their IP address space, often with proprietary database and interfaces.
> This work is to evolve IPAM into standardized interfaces for 
> coordinated management of IP addresses, including legacy IP neworks, 
> SDN/NFV networks and other forms of virtualization. Use cases include 
> dynamic allocation and release of IP addresses and prefixes based on 
> usage and queries to RIR to receive the allocated prefixes to the 
> requestor. The interfaces will be specified as Yang models. The scope 
> of the system is within a single autonomous system.
>
> Future work, not part of the current charter, could include 
> intent-based northbound interfaces and additional interactions with RIR.
>
> Milestones
> - Problem Statement and Architecture
> - Yang model for IP prefix management
> - Yang model for RIR Internet Number Resource requests
>
>
>
>>
>> -----Original Message-----
>> From: CASM [mailto:casm-bounces@ietf.org] On Behalf Of Marc Blanchet
>> Sent: Tuesday, August 08, 2017 1:45 AM
>> To: casm <casm@ietf.org <mailto:casm@ietf.org>>
>> Subject: [Casm] casm proposed charter v20170807
>>
>> Hello,
>>  following our informal meeting during last IETF, I took the token to 
>> start writing a charter for CASM. I know it is not complete, but 
>> would like to get comments, proposals, suggestions, reviews at this 
>> point.
>>
>> Regards, Marc.
>>
>> ==========
>>
>> Coordinated Address Space Management (CASM) Proposed Charter, v20170807
>>
>> Organizations use IP Address Space Management (IPAM) tools to manage 
>> their IP address space, often with proprietary database and interfaces.
>> This work is 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 
>> and queries to RIR to receive the allocated prefixes to the 
>> requestor.  The interfaces will be specified as Yang models. The 
>> scope of the system is within a single autonomous system.
>> Future work, not part of the current charter, could include 
>> intent-based northbound interfaces and additional interactions with RIR.
>>
>> Milestones
>> - Problem Statement and Architecture
>> - Yang model for IP prefix management
>> - Yang model for RIR Internet Number Resource requests
>>
>> _______________________________________________
>> CASM mailing list
>> CASM@ietf.org <mailto:CASM@ietf.org>
>> https://www.ietf.org/mailman/listinfo/casm
>
>
>
> _______________________________________________
> CASM mailing list
> CASM@ietf.org
> https://www.ietf.org/mailman/listinfo/casm

v2.23.0 | Report a Bug | By Email