Hello Lorand and the other authors, I have following comments to the draft:
section 2.4 You introduce RLOC to RLOC bindings for recursive LISP use case. On the other hand in draft-ietf-lisp-eid-block and EID block of /16 IPv6 prefix is introduced with a target of " By defining an IPv6 EID Block is possible to configure the router so to natively forward all packets that have not a destination address in the block, without performing any lookup whatsoever. " Clearly this benefit is lost in the recursive LISP use case. Also you introduce "a private database" for RLOC mappings to be used instead of the global LISP mapping system. Further you recommend that the use of recursion only between two ISPs. To me this appears quite a heavy arrangement especially when taking account the main disadvantages you enumerate in the draft. Why can't you just tunnel (using your favorite tunneling protocol) between the two ISPs? Without any mapping system. What does the mapping system bring in to the scenario? Especially when the number of recursion ITRs and ETRs between the two ISPs are not that many (order of tens I believe). An editorial nit in section 5.4 Migration Summary: Acronym PITR-RD has not been opened up anywhere in the draft. Wouldn't it be simpler (at least more reader friendly) to talk about EID route servers instead of PITR-RDs? Best regards Hannu -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of ext Loránd Jakab Sent: Monday, July 11, 2011 1:36 PM To: [email protected] Subject: Re: [lisp] I-D Action: draft-ietf-lisp-deployment-01.txt Folks, We moved the PITR scenarios to a new section discussing coexistence/migration/transition, and evolved the Tier 1 scenario into a much better PITR route distribution architecture, that will be presented in Quebec. Regards, Lorand Jakab (on behalf of the draft authors) On 07/11/11 12:26, [email protected] wrote: > A New Internet-Draft is available from the on-line Internet-Drafts > directories. This draft is a work item of the Locator/ID Separation Protocol > Working Group of the IETF. > > Title : LISP Network Element Deployment Considerations > Author(s) : Lorand Jakab > Albert Cabellos-Aparicio > Florin Coras > Jordi Domingo-Pascual > Darrel Lewis > Filename : draft-ietf-lisp-deployment-01.txt > Pages : 22 > Date : 2011-07-11 > > This document discusses the different scenarios for the deployment of > the new network elements introduced by the Locator/Identifier > Separation Protocol (LISP). > > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-lisp-deployment-01.txt > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > This Internet-Draft can be retrieved at: > ftp://ftp.ietf.org/internet-drafts/draft-ietf-lisp-deployment-01.txt > _______________________________________________ > lisp mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/lisp _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
