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

"Xie Chongfeng" <xiechf.bri@chinatelecom.cn> Wed, 15 February 2017 01:27 UTC

Return-Path: <xiechf.bri@chinatelecom.cn>
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 61E3412999F for <casm@ietfa.amsl.com>; Tue, 14 Feb 2017 17:27:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.891
X-Spam-Level:
X-Spam-Status: No, score=-1.891 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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] 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 X-BfOOoKeXSy for <casm@ietfa.amsl.com>; Tue, 14 Feb 2017 17:27:21 -0800 (PST)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.222]) by ietfa.amsl.com (Postfix) with ESMTP id 0E46A12998B for <casm@ietf.org>; Tue, 14 Feb 2017 17:27:19 -0800 (PST)
HMM_SOURCE_IP: 172.18.0.218:37443.226884232
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-1.202.6.97 (unknown [172.18.0.218]) by chinatelecom.cn (HERMES) with ESMTP id B04B5280092; Wed, 15 Feb 2017 09:27:05 +0800 (CST)
Received: from ip<1.202.6.97> ([172.18.0.218]) by App0025(MEDUSA 0.0.0.0) with ESMTP id 45eaf657-c036-44c8-adff-1dfe3a1bc60e for bclaise@cisco.com; Wed Feb 15 09:27:14 2017
0/X-Total-Score: 0:
X-FILTER-SCORE: to=<83848d828a948661848a9484904f84908e>, score=<1487122034gv88888j88q88S8jqSyoQ5n77777x77i77T7xiT2LHbJ>
X-Real-From: xiechf.bri@chinatelecom.cn
X-Receive-IP: 172.18.0.218
X-MEDUSA-Status: 0
Date: Wed, 15 Feb 2017 09:27:08 +0800
From: "Xie Chongfeng" <xiechf.bri@chinatelecom.cn>
To: bclaise <bclaise@cisco.com>, "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>, <462548f7-ddcf-1a0a-8ea8-c17c02cbeba5@cisco.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 7, 166[cn]
Mime-Version: 1.0
Message-ID: <201702150927072506232@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart762814640127_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/TA8DhZQJMfPoA7sAM0fmfqTgNsU>
Cc: lichen <lichen@ctbri.com.cn>, "'ian.farrer'" <ian.farrer@telekom.de>, "normen.kowalewski@telekom.de" <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: Wed, 15 Feb 2017 01:27:25 -0000

Hi, Benoit, 

Thank you for your notififying me. we are updating the 3 drafts and will submit them soon.


Best regards
Chongfeng 




xiechf.bri@chinatelecom.cn
 
From: Benoit Claise
Date: 2017-02-14 23:50
To: Xie Chongfeng; Rakesh Kumar; 'Liushucheng (Will)'; marc.blanchet@viagenie.ca
CC: ian.farrer; normen.kowalewski; CASM@ietf.org
Subject: Re: [Casm] New Version Notification for draft-kumar-requirements-and-framework-00.txt
Chongfeng,

For my understanding...
So the plan is to stop working on these three drafts in OPSAWG?
draft-xi-ps-centralized-address-management      expired
draft-sun-i2apm-address-pool-management-arch  expired 
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
Date: 2017-02-03 14:37
To: Liushucheng (Will); Marc Blanchet; Xie Chongfeng
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