Re: [Casm] New Version Notification for draft-kumar-requirements-and-framework-00.txt

Benoit Claise <bclaise@cisco.com> Tue, 14 February 2017 15:50 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 624401293DC for <casm@ietfa.amsl.com>; Tue, 14 Feb 2017 07:50:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.512
X-Spam-Level:
X-Spam-Status: No, score=-14.512 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, 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 s04_jNMnzZXa for <casm@ietfa.amsl.com>; Tue, 14 Feb 2017 07:50:16 -0800 (PST)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2C32126CD8 for <CASM@ietf.org>; Tue, 14 Feb 2017 07:50:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=22284; q=dns/txt; s=iport; t=1487087416; x=1488297016; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=+u49UpEN3U5JZGH/5qQPMzHQpCQGpCZsGUWOiaPzDV0=; b=SNesdQwnOJHow0/DxPiW1Jnia5KJFVyHhTPvXMfJaEhMAn1TW/cvfain yZQgVUs9DAkcc3ETNdKOQ3Aek80TJ0TKQjeNJQI2c8GFBAR8lNV3O5Jl9 FwDc0VuKnVM0nU4wzvzFRJboUlOkAtP+kAsJRHtDSdjlEjFtN1cUaOdbO 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DPBAAdJqNY/xbLJq1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgm+BRAMnX4NZinqRHox/ikMfAQyFdgKCPxQBAgEBAQEBAQFiKIR?= =?us-ascii?q?pAQEBAwEBASFLBAUCDAQJAhEDAQEBAScDAgInHwkIBgEMBgIBAYlfCA6RPp1Og?= =?us-ascii?q?iUrizEBAQEBAQEBAQEBAQEBAQEBAQEBAQEdhkyCBYJqhFwYFoJQgl8FiQQIhje?= =?us-ascii?q?BRopphm+LJYF7U4REgy2GRogsgmSIBTYhVSsgFAgVFRglhHuBST81AYofAQEB?=
X-IronPort-AV: E=Sophos;i="5.35,161,1484006400"; d="scan'208,217";a="650659130"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Feb 2017 15:50:11 +0000
Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v1EFoAoY021044; Tue, 14 Feb 2017 15:50:11 GMT
To: Xie Chongfeng <xiechf.bri@chinatelecom.cn>, Rakesh Kumar <rkkumar@juniper.net>, "'Liushucheng (Will)'" <liushucheng@huawei.com>, "marc.blanchet@viagenie.ca" <marc.blanchet@viagenie.ca>
References: <C6E4C89A-AE5C-42F6-A533-1D14B2BEBA92@juniper.net> <0C1DF88F-E1D2-4A3A-B452-E964500EF93D@viagenie.ca> <C9B5F12337F6F841B35C404CF0554ACB898BBCC6@SZXEMA509-MBS.china.huawei.com> <2114F564-747D-4BDA-9909-20CA69C9A23C@juniper.net> <2017020510350947064621@chinatelecom.cn>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <462548f7-ddcf-1a0a-8ea8-c17c02cbeba5@cisco.com>
Date: Tue, 14 Feb 2017 16:50:09 +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: <2017020510350947064621@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="------------146327A30BA0CFD956785560"
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/3iDnpo4Qow2NCTpMRSaRmowpnvs>
Cc: "ian.farrer" <ian.farrer@telekom.de>, "normen.kowalewski" <normen.kowalewski@telekom.de>, "CASM@ietf.org" <CASM@ietf.org>
Subject: Re: [Casm] New Version Notification for draft-kumar-requirements-and-framework-00.txt
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: Tue, 14 Feb 2017 15:50:19 -0000

Chongfeng,

For my understanding...
So the plan is to stop working on these three drafts in OPSAWG?

    draft-xi-ps-centralized-address-management
    <http://tools.ietf.org/html/draft-xi-ps-centralized-address-management>
    expired
    draft-sun-i2apm-address-pool-management-arch
    <http://tools.ietf.org/html/draft-sun-i2apm-address-pool-management-arch>
    expired
    draft-sun-i2apm-address-pool-management-yang
    <http://tools.ietf.org/html/draft-sun-i2apm-address-pool-management-yang>
    expired

Regards, Benoit
> Yes, I agree to  combine all ideas into one set of drafts to push 
> forward this work.
>
> BUT  I didn't find any major difference between CASM and the old 
> drafts, major use cases of centralized address management has been 
> considered in the old PS draft 
> (https://datatracker.ietf.org/doc/draft-xie-ps-centralized-address-management/), 
> including the DNS and NAT. CT put forward the use case of address 
> management in metro network,  Ian and norman of DT raised the case of 
> address management for OpenStack, OSS,etc.
>
> So, I think it is necessary to clarify the relationship of these 
> drafts. Thank you!
>
> Chongfeng
>
> ------------------------------------------------------------------------
> xiechf.bri@chinatelecom.cn
>
>     *From:* Rakesh Kumar <mailto:rkkumar@juniper.net>
>     *Date:* 2017-02-03 14:37
>     *To:* Liushucheng (Will) <mailto:liushucheng@huawei.com>; Marc
>     Blanchet <mailto:marc.blanchet@viagenie.ca>; Xie Chongfeng
>     <mailto:xiechf.bri@chinatelecom.cn>
>     *CC:* CASM@ietf.org <mailto:CASM@ietf.org>
>     *Subject:* Re: [Casm] New Version Notification for
>     draft-kumar-requirements-and-framework-00.txt
>     Hi Will,
>     The draft we wrote was based on the slide set we had presented
>     earlier, that details a comprehensive approach to address
>     management including with other address services such as DNS and
>     NAT. We have also introduced the concept of interfaces based on
>     user requirements.
>     I think, it would be good idea to combine all ideas into one set
>     of drafts.
>     I think, CASM would also be useful for mining data for security
>     related analytics.
>     Thanks
>     Rakesh
>     On 2/2/17, 10:26 PM, "CASM on behalf of Liushucheng (Will)"
>     <casm-bounces@ietf.org on behalf of liushucheng@huawei.com> wrote:
>         Hi Rakesh,
>         Many thanks for your efforts!
>         No worries. Let's review and update in next version. And maybe
>     another online meeting in next week.
>         Btw, there are also some old work on this area as we discussed:
>     https://datatracker.ietf.org/doc/draft-xie-ps-centralized-address-management/
>     https://datatracker.ietf.org/doc/draft-sun-i2apm-address-pool-management-arch/
>     https://datatracker.ietf.org/doc/draft-sun-i2apm-address-pool-management-yang/
>         Would you please let the audience know about the differences
>     between new ones and old ones?
>         Regards,
>         Will (LIU Shucheng)
>         -----Original Message-----
>         From: CASM [mailto:casm-bounces@ietf.org] On Behalf Of Marc
>     Blanchet
>         Sent: Monday, January 30, 2017 9:02 PM
>         To: Rakesh Kumar <rkkumar@juniper.net>
>         Cc: CASM@ietf.org
>         Subject: Re: [Casm] New Version Notification for
>     draft-kumar-requirements-and-framework-00.txt
>         On 30 Jan 2017, at 1:43, Rakesh Kumar wrote:
>         > It looks like we messed up on the name. My mistake.
>         >
>         > It should have been
>         > “draft-kumar-casm-requirements-and-framework-00” instead of
>         > “draft-kumar-requirements-and-framework-00”.
>         > Is there a way to correct it?
>         yeah. no big deal. we shall fix it for the new rev.
>         Marc.
>         >
>         > Thanks
>         > Rakesh
>         >
>         > On 1/29/17, 8:03 PM, "CASM on behalf of Rakesh Kumar"
>         > <casm-bounces@ietf.org on behalf of rkkumar@juniper.net> wrote:
>         >
>         >
>         >
>         >     On 1/29/17, 7:53 PM, "internet-drafts@ietf.org"
>         > <internet-drafts@ietf.org> wrote:
>         >
>         >
>         >         A new version of I-D,
>         > draft-kumar-requirements-and-framework-00.txt
>         >         has been successfully submitted by Marc Blanchet and
>     posted to
>         > the
>         >         IETF repository.
>         >
>         >         Name: draft-kumar-requirements-and-framework
>         >         Revision: 00
>         >         Title: Centralized Address Space Management(CASM)
>         > Requirements and Framework
>         >         Document date: 2017-01-29
>         >         Group: Individual Submission
>         >         Pages: 8
>         >         URL:
>         >
>     https://www.ietf.org/internet-drafts/draft-kumar-requirements-and-framework-00.txt
>         >         Status:
>         >
>     https://datatracker.ietf.org/doc/draft-kumar-requirements-and-framework/
>         >         Htmlized:
>         >
>     https://tools.ietf.org/html/draft-kumar-requirements-and-framework-00
>         >
>         >
>         >         Abstract:
>         >            The organizations use IP Address Space Management
>     (IPAM)
>         > tools to
>         >            manage their IP address space, often with
>     proprietary
>         > database and
>         >            interfaces.  This document describes evolution of
>     IPAM into
>         > a
>         >            standardized interfaces for centralized
>     management of IP
>         > addresses.
>         >
>         >
>         >
>         >
>         >         Please note that it may take a couple of minutes
>     from the time
>         > of submission
>         >         until the htmlized version and diff are available at
>         > tools.ietf.org.
>         >
>         >         The IETF Secretariat
>         >
>         >
>         >
>         > _______________________________________________
>         >     CASM mailing list
>         >     CASM@ietf.org
>         >     https://www.ietf.org/mailman/listinfo/casm
>         >
>         >
>         > _______________________________________________
>         > CASM mailing list
>         > CASM@ietf.org
>         > https://www.ietf.org/mailman/listinfo/casm
>         _______________________________________________
>         CASM mailing list
>         CASM@ietf.org
>         https://www.ietf.org/mailman/listinfo/casm
>         _______________________________________________
>         CASM mailing list
>         CASM@ietf.org
>         https://www.ietf.org/mailman/listinfo/casm
>