Re: [Casm] New Version Notification for draft-kumar-requirements-and-framework-00.txt
"Marc Blanchet" <marc.blanchet@viagenie.ca> Wed, 08 February 2017 14:09 UTC
Return-Path: <marc.blanchet@viagenie.ca>
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 79FBB129A9A for <casm@ietfa.amsl.com>; Wed, 8 Feb 2017 06:09:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 HZlcG5cWVtt9 for <casm@ietfa.amsl.com>; Wed, 8 Feb 2017 06:09:54 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8786A129A59 for <CASM@ietf.org>; Wed, 8 Feb 2017 06:09:53 -0800 (PST)
Received: from [206.123.31.198] (h198.viagenie.ca [206.123.31.198]) by jazz.viagenie.ca (Postfix) with ESMTPSA id D58A6403C3; Wed, 8 Feb 2017 09:09:52 -0500 (EST)
From: Marc Blanchet <marc.blanchet@viagenie.ca>
To: Xie Chongfeng <xiechf.bri@chinatelecom.cn>
Date: Wed, 08 Feb 2017 09:09:42 -0500
Message-ID: <81EE1EFF-931F-4A09-B6E5-0E9FCF79755F@viagenie.ca>
In-Reply-To: <2017020821595192051527@chinatelecom.cn>
References: <65913429-AE80-4226-AB9D-75DBCF7BE032@juniper.net> <2017020821515806195321@chinatelecom.cn> <5DDDE741-6126-4F18-AF20-37554F988E26@viagenie.ca> <2017020821595192051527@chinatelecom.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Mailer: MailMate (1.9.6r5344)
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/egF0f-coMalsnqxdiOSgPDqBbPk>
Cc: Rakesh Kumar <rkkumar@juniper.net>, "ian.farrer" <ian.farrer@telekom.de>, "normen.kowalewski@telekom.de" <normen.kowalewski@telekom.de>, Liushucheng <liushucheng@huawei.com>, "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, 08 Feb 2017 14:09:57 -0000
On 8 Feb 2017, at 8:59, Xie Chongfeng wrote: > From our experience, the centralized address management system need to > verify this by communicating with the routing system, to avoid any > abnormity. sure. I’m just trying to say that route injection does not have to be centralized. up to the operator. Marc. > Chongfeng > > > > xiechf.bri@chinatelecom.cn > > From: Marc Blanchet > Date: 2017-02-08 21:54 > To: Xie Chongfeng > CC: Rakesh Kumar; Liushucheng; CASM@ietf.org; ian.farrer; > normen.kowalewski@telekom.de > Subject: Re: [Casm] New Version Notification for > draft-kumar-requirements-and-framework-00.txt > On 8 Feb 2017, at 8:51, Xie Chongfeng wrote: > >> One of the basic requirments of centralized address management is >> that >> the mechanism shouled be aligned with the routing system, for >> instance, when one address block is allocated to an network equiment, >> the routing entry correspondent to this address block will be >> broadcasted accordingly, otherwise, the network will not work >> correctly. > > well, yes. but that route injection can be done by the network > equipment > into the routing realm. So in this case, the route injection is not > centralized per se. > > Marc. > >> Similarly,when one address block is withdrawl from an given network >> equipment, the routing entry will be withdrawl as well. >> >> Chongfeng Xie >> >> >> >> xiechf.bri@chinatelecom.cn >> >> From: Rakesh Kumar >> Date: 2017-02-06 06:02 >> To: Xie Chongfeng; 'Liushucheng (Will)'; marc.blanchet@viagenie.ca >> CC: CASM@ietf.org; ian.farrer; normen.kowalewski; Rakesh Kumar >> Subject: Re: [Casm] New Version Notification for >> draft-kumar-requirements-and-framework-00.txt >> Hi Dr Xie, Will >> >> We put two drafts based on earlier discussions. >> >> 1. >> https://tools.ietf.org/html/draft-kumar-casm-problem-and-use-cases-00 >> : Basically draft identifies the traditional IP address management >> tools (proprietary and open source) and what they lack. I think, >> almost every network deployment would need some sort of address >> management so talked about use-cases not from deployment but from >> implementation perspective. Basically approach taken in this draft >> regarding problem and use-cases is a bit different than >> https://datatracker.ietf.org/doc/draft-xie-ps-centralized-address-management. >> 2. >> https://tools.ietf.org/html/draft-kumar-casm-requirements-and-framework-00 >> : We have listed a set of requirement from a modern address >> management >> system that can be used for diverse set of deployments (Data Center, >> Metro Access, BNG, 3GPP, Enterprise branch & campus etc.). We have >> also specified an architecture framework to define and develop >> “CASM”. >> >> In summary, at top level this work looks similar to the earlier one >> but there are differences in approaches. >> >> Thanks & Regards, >> Rakesh >> >> From: Xie Chongfeng <xiechf.bri@chinatelecom.cn> >> Date: Saturday, February 4, 2017 at 6:35 PM >> To: Rakesh Kumar <rkkumar@juniper.net>, "'Liushucheng (Will)'" >> <liushucheng@huawei.com>, "marc.blanchet@viagenie.ca" >> <marc.blanchet@viagenie.ca> >> Cc: "CASM@ietf.org" <CASM@ietf.org>, "ian.farrer" >> <ian.farrer@telekom.de>, "normen.kowalewski" >> <normen.kowalewski@telekom.de> >> Subject: Re: Re: [Casm] New Version Notification for >> draft-kumar-requirements-and-framework-00.txt >> >> >> 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
- Re: [Casm] New Version Notification for draft-kum… Rakesh Kumar
- Re: [Casm] New Version Notification for draft-kum… Xie Chongfeng
- Re: [Casm] New Version Notification for draft-kum… Marc Blanchet
- Re: [Casm] New Version Notification for draft-kum… Xie Chongfeng
- Re: [Casm] New Version Notification for draft-kum… Marc Blanchet
- Re: [Casm] New Version Notification for draft-kum… Rakesh Kumar
- Re: [Casm] New Version Notification for draft-kum… Marc Blanchet
- Re: [Casm] New Version Notification for draft-kum… Brian E Carpenter