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

"Liushucheng (Will)" <liushucheng@huawei.com> Fri, 03 February 2017 06:52 UTC

Return-Path: <liushucheng@huawei.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 E15831293DC; Thu, 2 Feb 2017 22:52:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.419
X-Spam-Level:
X-Spam-Status: No, score=-7.419 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 2Ml4Y6zRwtb8; Thu, 2 Feb 2017 22:52:35 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DD0C128E18; Thu, 2 Feb 2017 22:52:34 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml705-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DFS28000; Fri, 03 Feb 2017 06:52:31 +0000 (GMT)
Received: from SZXEMA414-HUB.china.huawei.com (10.82.72.73) by lhreml705-cah.china.huawei.com (10.201.5.168) with Microsoft SMTP Server (TLS) id 14.3.301.0; Fri, 3 Feb 2017 06:52:30 +0000
Received: from SZXEMA509-MBS.china.huawei.com ([169.254.2.147]) by SZXEMA414-HUB.china.huawei.com ([10.82.72.73]) with mapi id 14.03.0235.001; Fri, 3 Feb 2017 14:52:24 +0800
From: "Liushucheng (Will)" <liushucheng@huawei.com>
To: Rakesh Kumar <rkkumar@juniper.net>, Marc Blanchet <marc.blanchet@viagenie.ca>, Xie Chongfeng <xiechf.bri@chinatelecom.cn>, "draft-xie-ps-centralized-address-management@ietf.org" <draft-xie-ps-centralized-address-management@ietf.org>
Thread-Topic: [Casm] New Version Notification for draft-kumar-requirements-and-framework-00.txt
Thread-Index: AQHSevkfeV7Pux9hTUaQV0Cdp4RpsKFW1Itw//9/XoCAAIbrgA==
Date: Fri, 03 Feb 2017 06:52:24 +0000
Message-ID: <C9B5F12337F6F841B35C404CF0554ACB898BBD2A@SZXEMA509-MBS.china.huawei.com>
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>
In-Reply-To: <2114F564-747D-4BDA-9909-20CA69C9A23C@juniper.net>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.70.79.82]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.589428B0.00AF, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.2.147, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: a3d61cf00703c48b3484ba03bf382c0b
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/lZvRRYVL5QRt4p67iCC_c2-S9I0>
Cc: "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: Fri, 03 Feb 2017 06:52:38 -0000

Thanks for your prompt response. I have a better understanding now. 

Just took a glance and below please find the abstracts of two PS drafts, one requirement form the old one:

----draft-xie-ps-centralized-address-management-01----
Abstract

   The increase in number, diversity and complexity of devices and 
   services in modern networks bring new challenges for the management 
   of network resources, such as IP addresses, network prefixes, bandwidth, 
   and services that utilize such resources. This draft contains a problem 
   statement for IP address management and defines requirements with 
   practical use cases provided by operators.

...

5. Requirements

   Based on the analysis above, some requirements for IP address
   management can be highlighted as following:

   1) An integrated, centralized IP address management is desirable as it offers 
   an aggregated view on all stages of the life cycle of IP address resources, from 
   selection, allocation, assignment to reclaiming them into to free resources 
   in an optimized and efficient way.
---cut---

-----draft-kumar-casm-problem-and-use-cases-00-----
Abstract

   The organisations 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.
---cut---

From the text above I guess the two draft shares the same target:  A centralized IP address management.  
As there are already detailed use cases and requirements written in the old PS draft, I would suggest that maybe we should combine them together if applicable... My 0.02

Btw, I will do finish review and send my detailed comments earlier next week. 

Regards,
Will (LIU Shucheng) 


-----Original Message-----
From: Rakesh Kumar [mailto:rkkumar@juniper.net] 
Sent: Friday, February 03, 2017 2:37 PM
To: Liushucheng (Will) <liushucheng@huawei.com>; Marc Blanchet <marc.blanchet@viagenie.ca>; Xie Chongfeng <xiechf.bri@chinatelecom.cn>
Cc: 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