Re: [Casm] Possible charter goals and milestones

Benoit Claise <bclaise@cisco.com> Wed, 15 February 2017 13:25 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 86358129A23 for <casm@ietfa.amsl.com>; Wed, 15 Feb 2017 05:25:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=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 t1GGSrvLUHjY for <casm@ietfa.amsl.com>; Wed, 15 Feb 2017 05:25:05 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09FE01299F9 for <CASM@ietf.org>; Wed, 15 Feb 2017 05:25:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=32143; q=dns/txt; s=iport; t=1487165105; x=1488374705; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=uVfXozH6+DET3c++tYzkf4p9K9YxexhcS5OW2J+Dhvc=; b=lH8/goL29CStM5bPXecfadpFHEMieyf5cU93B/K5WetT6CsvQTYRasYn MhRpi0wssGF1fJoI/eYx+MXB8SgMaBMvulvRck2rYVZFyAQKWDDLzZxJd UpkdVZtkRn4af+9qZb46/NIGC4GcwaCUbKDrmdX0ytm2094Hz6m7GQeiW 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CrAQBFVqRY/xbLJq1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgm+BRAMnX4NZighykR6VNoIJAx8BDIV2AoJLGAECAQEBAQEBAWI?= =?us-ascii?q?ohHABAQEEAQEhCicaCxAJAhEEAQEhAQYDAgInHwkIBgEMBgIBAReJUA6SDZ1Og?= =?us-ascii?q?iUrizcBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYZNggWCaoUKglCCXwWVVYYihm+?= =?us-ascii?q?LJYo/hkeLEYgGHzhVKyAUCBUVPYZEPzUBigYBAQE?=
X-IronPort-AV: E=Sophos;i="5.35,166,1484006400"; d="scan'208,217";a="652502483"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Feb 2017 13:25:02 +0000
Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v1FDP2SD014437; Wed, 15 Feb 2017 13:25:02 GMT
To: "Liushucheng (Will)" <liushucheng@huawei.com>, "CASM@ietf.org" <CASM@ietf.org>
References: <e3e3a854-f452-c176-1757-f0fcb94a5b2a@cisco.com> <C9B5F12337F6F841B35C404CF0554ACB898C37DB@SZXEMA509-MBS.china.huawei.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <6150aca4-83ee-60cf-4b79-b657b8971040@cisco.com>
Date: Wed, 15 Feb 2017 14:25:01 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <C9B5F12337F6F841B35C404CF0554ACB898C37DB@SZXEMA509-MBS.china.huawei.com>
Content-Type: multipart/alternative; boundary="------------E920F4D4682A5D67114FE280"
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/P8NPZ8LfiD1hMjsxrVKB8PE3Dxk>
Cc: 'Ying Cheng' <chengying10@chinaunicom.cn>, 'Xie Chongfeng' <xiechf.bri@chinatelecom.cn>, 'Rakesh Kumar' <rkkumar@juniper.net>, "joelja@bogus.com" <joelja@bogus.com>, Marc Blanchet <marc.blanchet@viagenie.ca>, "warren@kumari.net" <warren@kumari.net>
Subject: Re: [Casm] Possible charter goals and milestones
X-BeenThere: casm@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 15 Feb 2017 13:25:08 -0000

Hi Liushucheng,
>
> 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. 
> https://trac.tools.ietf.org/bof/trac/
>
> 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.
>
Protocol work?  Which protocol?  Can you expand on what is needed?
I thought the work was about interfaces.
>
> I’m copying the updated version below for your convenience.
>
I believe this is better.

Regards, Benoit
>
> --start—
>
> *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
>       o Problem statement and use cases
>       o Requirements and framework
>       o Possible charter goals and milestones
>       o 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: ​​https://www.ietf.org/mailman/listinfo/casm
>   * Draft charter: TBD
>   * Relevant drafts:
>       o ​https://datatracker.ietf.org/doc/draft-kumar-casm-problem-and-use-cases
>       o ​https://datatracker.ietf.org/doc/draft-xie-ps-centralized-address-management
>       o ​https://datatracker.ietf.org/doc/draft-kumar-casm-requirements-and-framework
>       o ​https://datatracker.ietf.org/doc/draft-sun-i2apm-address-pool-management-arch
>       o ​https://datatracker.ietf.org/doc/draft-sun-i2apm-address-pool-management-yang
>
> --end--
>
> Regards,
>
> Will (LIU Shucheng)
>
> *From:*CASM [mailto:casm-bounces@ietf.org] *On Behalf Of *Benoit Claise
> *Sent:* Wednesday, February 15, 2017 1:37 AM
> *To:* CASM@ietf.org
> *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
>
>
>
> _______________________________________________
> CASM mailing list
> CASM@ietf.org
> https://www.ietf.org/mailman/listinfo/casm