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

Rakesh Kumar <rkkumar@juniper.net> Fri, 03 February 2017 06:37 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 C08331295DC for <casm@ietfa.amsl.com>; Thu, 2 Feb 2017 22:37: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 ZNtyqLR7Sy-q for <casm@ietfa.amsl.com>; Thu, 2 Feb 2017 22:37:29 -0800 (PST)
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01on0123.outbound.protection.outlook.com [104.47.34.123]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A0D11295CD for <CASM@ietf.org>; Thu, 2 Feb 2017 22:37:28 -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=qeIokbAVxuxWeaYAXRQ2PsNsSRkg8t/VNnaeFivXe9Y=; b=DJqnv9dBlTYrrA0lNOD/FWGuXAUvnLTrPCKWse2GVLOIRaIs/ni7J2C4WkATToBB6pzdr8GcLAAD0IXMf8hgH9rmGH/WvimXiIfdXfyJS3NVP/wn5knVm2Dlf4kLUCR0yW7Ja27GP4jNpC/9VXm/3hQjZELwvf7Dy9W5mQ8TtQw=
Received: from BN6PR05MB2993.namprd05.prod.outlook.com (10.173.19.11) by BN6PR05MB2995.namprd05.prod.outlook.com (10.173.19.13) 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 06:37:27 +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 06:37:27 +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>
Thread-Topic: [Casm] New Version Notification for draft-kumar-requirements-and-framework-00.txt
Thread-Index: AQHSevkbhAU8nf/OQkaIFIss4o0BxKFW1ugA//98/4A=
Date: Fri, 03 Feb 2017 06:37:27 +0000
Message-ID: <2114F564-747D-4BDA-9909-20CA69C9A23C@juniper.net>
References: <C6E4C89A-AE5C-42F6-A533-1D14B2BEBA92@juniper.net> <0C1DF88F-E1D2-4A3A-B452-E964500EF93D@viagenie.ca> <C9B5F12337F6F841B35C404CF0554ACB898BBCC6@SZXEMA509-MBS.china.huawei.com>
In-Reply-To: <C9B5F12337F6F841B35C404CF0554ACB898BBCC6@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: 2c317174-2db0-4ee0-e528-08d44bff1eef
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081); SRVR:BN6PR05MB2995;
x-microsoft-exchange-diagnostics: 1; BN6PR05MB2995; 7:KTDprqS9EMX2fJmaaLcEsCS2LZAkAoVM0/3eR6zPuYFFOfKzfTmjRDi47lA6PLAz95vm/JfeUNgCC53q7E5CGSUyOEYtddWDw9Y+9m+IJjCGdqRNAM/aW+RnKuGmiSMXH9sa2NgJxXPO80NcumVKDHFQ7uKYSeFwxCTvsK2RnW6tXJKkIDXy2Kw7juc7hHow5Vjc6ArTToBxdhZhMZheQUNtZ25yxbc0ASJceKlxD3NoBJLM/bIHzD6zeJcIGLMoYa37Jcd0CjaYCfduziewrXpVypanZrdoLKR5Qgd8HuzT2Q6ik4mE/LRc8hnzsuRtiEgZjqRU+YG96kUagQ1ht6Woisy6yaQ9eLyw5II1TgfgiKyzNxVoP9EQ/BCCMWhaUvVFVvVfD37pUUM+ooV/g5onsJAXnQoxoOHVVYNdRXmXNhOVndJXbL8fEvQXw6UwG7FXMZYVjnpzP+WB4dGyzDOu5FY2EnqT4OGRKXp3rhEB++wJBGmIHdRD1m6tDG8Jb0emgUA41jDL2X5t58CYcMtwH8lrzCp4ig9kxwLqhcLHlJ4+kpHfr00qICjESnZc
x-microsoft-antispam-prvs: <BN6PR05MB2995E6906FC4D33C310A5EB8AD4F0@BN6PR05MB2995.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105)(209352067349851)(192374486261705)(50582790962513)(138986009662008);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026)(6041248)(20161123558025)(20161123562025)(20161123555025)(20161123564025)(20161123560025)(6072148); SRVR:BN6PR05MB2995; BCL:0; PCL:0; RULEID:; SRVR:BN6PR05MB2995;
x-forefront-prvs: 02070414A1
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(39450400003)(39410400002)(39850400002)(39840400002)(377424004)(199003)(189002)(377454003)(13464003)(24454002)(66654002)(97736004)(68736007)(4001350100001)(66066001)(6116002)(5001770100001)(3846002)(102836003)(15650500001)(92566002)(53936002)(101416001)(3660700001)(7736002)(305945005)(2900100001)(76176999)(54356999)(50986999)(122556002)(6306002)(6512007)(99286003)(82746002)(81156014)(81166006)(105586002)(8676002)(83506001)(229853002)(6506006)(77096006)(6486002)(38730400001)(3280700002)(25786008)(33656002)(6436002)(36756003)(189998001)(2950100002)(106356001)(230783001)(53546003)(6246003)(86362001)(2906002)(8936002)(83716003)(106116001)(5660300001)(4326007)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN6PR05MB2995; H:BN6PR05MB2993.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX: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: <88075DA6E92D5D41A37D505AB00E4036@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Feb 2017 06:37:27.2012 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR05MB2995
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/LijsVwNHF66Bc7PjLE_tICCTGKo>
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:37:31 -0000

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