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

Benoit Claise <bclaise@cisco.com> Wed, 15 February 2017 15:51 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 2D7CF129646 for <casm@ietfa.amsl.com>; Wed, 15 Feb 2017 07:51:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 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, URIBL_BLOCKED=0.001, 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 s2heSGv1BGG2 for <casm@ietfa.amsl.com>; Wed, 15 Feb 2017 07:50:57 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18D5B129615 for <CASM@ietf.org>; Wed, 15 Feb 2017 07:50:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=20783; q=dns/txt; s=iport; t=1487173857; x=1488383457; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=FMFrZJ4Y3xalqHKYICd3OnKcmgGs9QBf+BsRsbo67M0=; b=JE19voP0e5qylaoeDIjQbg94/5PtTlC8RsNsphXXDG9TXry/L/3CrR3Z LKNP1JnpZYdaeZEB+7LaY4XhWKWmJKEpFSNJPaxslRCBRcFRVO22sLvUn HhbQQCVaT/Cm4EKvkb89jcRoEXHPkSq9lv9kgcBQqU2CJyIeHtdl3GBHC E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AtAwB/eKRY/xbLJq1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgm+BRAOBBoNZighykH8fkAqFLIIMHwEMgjCDRgKCURgBAgEBAQE?= =?us-ascii?q?BAQFiKIRwAQEBBAEBIUsEBQIMBAsOAwMBAQEBJwMCAicfCQgGDQYCAQEXiVAOs?= =?us-ascii?q?AuCJSuLMwEBAQEBAQEBAQEBAQEBAQEBAQEBAR2GTYIFCIJihHSCZoJfBYkFhj+?= =?us-ascii?q?BRopthm+LJYF7U4REgy2GR4gtgmSIBh84VSsgFAgVFRglhHuBST81AYpQAQEB?=
X-IronPort-AV: E=Sophos;i="5.35,166,1484006400"; d="scan'208,217";a="652505536"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Feb 2017 15:50:54 +0000
Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v1FForSI022749; Wed, 15 Feb 2017 15:50:54 GMT
To: Ralph Droms <rdroms.ietf@gmail.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> <2017020510350947064621@chinatelecom.cn> <462548f7-ddcf-1a0a-8ea8-c17c02cbeba5@cisco.com> <201702150927072506232@chinatelecom.cn> <6fea7045-a85c-080b-0d80-139a4daa195d@cisco.com> <9DDC7976-7C54-407C-94CB-4C445DFEA696@gmail.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <843aeb36-1881-fd9e-96ee-6b4e74c984fe@cisco.com>
Date: Wed, 15 Feb 2017 16:50:53 +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: <9DDC7976-7C54-407C-94CB-4C445DFEA696@gmail.com>
Content-Type: multipart/alternative; boundary="------------6BF4276645FBCC6A80B21BB7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/MHAgdEkHmk2taIQ-Rst4sc-w-ho>
Cc: Rakesh Kumar <rkkumar@juniper.net>, "ian.farrer" <ian.farrer@telekom.de>, "normen.kowalewski@telekom.de" <normen.kowalewski@telekom.de>, "CASM@ietf.org" <CASM@ietf.org>, Xie Chongfeng <xiechf.bri@chinatelecom.cn>, lichen <lichen@ctbri.com.cn>, "Liushucheng \(Will\)" <liushucheng@huawei.com>, "marc.blanchet@viagenie.ca" <marc.blanchet@viagenie.ca>
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 15:51:00 -0000

On 2/15/2017 4:12 PM, Ralph Droms wrote:
>> On Feb 15, 2017, at 8:29 AM, Benoit Claise <bclaise@cisco.com> wrote:
>>
>> On 2/15/2017 2:27 AM, Xie Chongfeng wrote:
>>> Hi, Benoit,
>>>
>>> Thank you for your notififying me. we are updating the 3 drafts and will submit them soon.
>> Does it mean that you consider those 3 drafts as potential outcomes for CASM?
>> If yes, here is a question I asked to the mailing list:
>> If the solution is this YANG module, based on draft-sun-i2apm-address-pool-management-arch, should we jump directly to the solution? In other words, what is the BoF added value? Note: I thought that those two drafts received some (mild) support in OPSAWG already in IETF 94.
>> Or maybe the 3 drafts are not complete. So what's missing?
> Benoit - what do you mean by "jump directly to the solution"?  Go directly to WG formation?
No. I meant progressing draft-sun-i2apm-address-pool-management-yang

Quoting Chongfeng Xie (China Telecom):

    Since the requirements are pressing to CT, we
    begun the filed trial last year and 3 vendors have implementated the interface defined
    in draft-sun-i2apm-address-pool-management-yang, luckily they all passed the field test by our joint efforts.

It seems that some operators know what they want already.

Regards, Benoit
>
> - Ralph
>
>> Trying to understand.
>>
>> Regards, Benoit
>>>
>>> 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
>>>>      
>>>>   
>> _______________________________________________
>> CASM mailing list
>> CASM@ietf.org
>> https://www.ietf.org/mailman/listinfo/casm
> .
>