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

Rakesh Kumar <rkkumar@juniper.net> Fri, 03 February 2017 16:34 UTC

Return-Path: <rkkumar@juniper.net>
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 23A7F129E11; Fri, 3 Feb 2017 08:34:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.057
X-Spam-Level:
X-Spam-Status: No, score=-3.057 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1.156, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=junipernetworks.onmicrosoft.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 LRzOV-6sIYuV; Fri, 3 Feb 2017 08:34:25 -0800 (PST)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0119.outbound.protection.outlook.com [104.47.33.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C073F12968D; Fri, 3 Feb 2017 08:34:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=uEdfgQaUToi5N19+p1fMIiqFRaWEFzeg0Mi85jsz7G0=; b=DaXHi3BzRQSqHk/fdMm85sidmxPnJK14rPLSF7zSWuR/uQhf3gWxlFDFznwcmfSzpaiZUWEYD/8iwuyRgVvj6xynv9TUAqKKb7XdZt4ALqjhsdmKgWwGNmc8LZEkQwmSfknkPb5wK9xootCBvyBB6QEokn9Yh2i5VpgI8qQUAqQ=
Received: from BN6PR05MB2993.namprd05.prod.outlook.com (10.173.19.11) by BN6PR05MB2996.namprd05.prod.outlook.com (10.173.19.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.5; Fri, 3 Feb 2017 16:34:17 +0000
Received: from BN6PR05MB2993.namprd05.prod.outlook.com ([10.173.19.11]) by BN6PR05MB2993.namprd05.prod.outlook.com ([10.173.19.11]) with mapi id 15.01.0888.020; Fri, 3 Feb 2017 16:34:17 +0000
From: Rakesh Kumar <rkkumar@juniper.net>
To: "Liushucheng (Will)" <liushucheng@huawei.com>, 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: AQHSevkbhAU8nf/OQkaIFIss4o0BxKFW1ugA//98/4CAAIpMAIAAHHWA
Date: Fri, 3 Feb 2017 16:34:17 +0000
Message-ID: <3844F850-2B59-417E-9669-BAD9EB7DF425@juniper.net>
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> <C9B5F12337F6F841B35C404CF0554ACB898BBD2A@SZXEMA509-MBS.china.huawei.com>
In-Reply-To: <C9B5F12337F6F841B35C404CF0554ACB898BBD2A@SZXEMA509-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.18.0.160709
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rkkumar@juniper.net;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [66.129.239.15]
x-ms-office365-filtering-correlation-id: 3dd59583-0966-4a0e-36aa-08d44c527f42
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081); SRVR:BN6PR05MB2996;
x-microsoft-exchange-diagnostics: 1; BN6PR05MB2996; 7:YUL7rjNl3F/kfAXfEpuipkspYqCMBVasR5+5iWDJEciCLkh5RClaJY1llwcFYrWr+eTN1phhfPByHIOpduKQEjXslkezT648UnZBwajMppq3dQCLgwTjpMuZJDwr3rKPjMmUfqi/nX+G+wo7NdbOCW1tScCsWsqLmQ0TW/D4RsxBJB0qy8ZrfvmHm8MK9iPk6nVuAVFjDzuVc+Kg8YUGsqBuCDuEt35ykguxwn6gzatsQW+MNpDpTEL7V8L082nN3j0j9ce6B5ogtGWP9EBNl5OlblRwSioxIIwYWsv1fOdyvUx34QaHt3HHSc4esBrxOP64brXvaDaAv6Aj9B0pmJo8OqvnBWEvc0d//ipXCxFaMws5ounVTFFnNBL1KS5mnjy6S9CbtY4lzSyXx98u7iv+2I0bWV+Nn1mK6siuusNedvhoMWZbm6Cv07fjI9ukboCYFGw/uNLPSIKtWoaEXPDPezNePEgOfKyRPd5YbwQnd63Bw07ygPaLAnK7V5YzF6fy5b/eHgUAgT3T7c1dYg==
x-microsoft-antispam-prvs: <BN6PR05MB299676C4F2298160F29DF3FBAD4F0@BN6PR05MB2996.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105)(209352067349851)(192374486261705)(138986009662008)(50582790962513);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026)(6041248)(20161123558025)(20161123555025)(20161123562025)(20161123564025)(20161123560025)(6072148); SRVR:BN6PR05MB2996; BCL:0; PCL:0; RULEID:; SRVR:BN6PR05MB2996;
x-forefront-prvs: 02070414A1
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(39860400002)(39840400002)(39410400002)(39850400002)(39450400003)(377424004)(189002)(199003)(24454002)(66654002)(13464003)(377454003)(230783001)(2906002)(189998001)(5660300001)(77096006)(6486002)(76176999)(53546003)(106356001)(50986999)(106116001)(68736007)(101416001)(6436002)(93886004)(4001350100001)(6506006)(97736004)(54356999)(5001770100001)(3660700001)(2900100001)(66066001)(7736002)(6246003)(305945005)(8936002)(33656002)(86362001)(4326007)(3280700002)(92566002)(15650500001)(38730400001)(229853002)(81156014)(122556002)(36756003)(82746002)(83506001)(81166006)(83716003)(2501003)(8676002)(102836003)(6116002)(3846002)(6306002)(6512007)(25786008)(105586002)(99286003)(53936002)(2950100002)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN6PR05MB2996; H:BN6PR05MB2993.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <94C8FB4B70AAC7409E6B263360F6559F@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Feb 2017 16:34:17.0416 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR05MB2996
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/WfNr6Ipf1nRz057c9JuVMg56BkE>
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 16:34:31 -0000

Hi Will,

I agree that we should have one set of drafts reflecting our ideas.
Actually Marc suggested that we write these draft and circulate so that others can contribute and start the discussion going.

Regards,
Rakesh

On 2/2/17, 10:52 PM, "Liushucheng (Will)" <liushucheng@huawei.com> wrote:

    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>om>; Marc Blanchet <marc.blanchet@viagenie.ca>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