Hi Tony, I understand you weren't just asking how map-encap could solve the routing scaling problem by reducing the number of prefixes in the DFZ routing table. I understand you were asking about this without renumbering. You were referring to Lixia's statement:
> I would like to add another solution, map-and-encap (without > renumber), which seems holding best promise to me. Regarding renumbering, as I have written: Renumbering once might be OK when converting to Scalable PI (SPI space) http://psg.com/lists/rrg/2008/msg02355.html 2008-08-26 Re: Fast and sparse mapping? aggregated EIDs, OITRDs etc. http://psg.com/lists/rrg/2008/msg02475.html 2008-09-16 also: http://psg.com/lists/rrg/2008/msg02536.html some very large end-user networks may decide to convert their existing PI address space to an MAB, and therefore be responsible for its management, mapping and OITRDs (Open ITRs in the DFZ - like LISP "Proxy Tunnel Routers"). This address space then becomes the new kind: Scalable PI (SPI) space, since it is managed by Ivip and can be split into as many micronets as there are IPv4 addresses (or IPv6 /64s). A single MAB is a single advertised prefix in the DFZ, but it supports as many sites as this end-user wants, via it being split into multiple micronets. So assuming the end-user network would otherwise have used this PI space in multiple sites, with multiple advertised prefixes in the DFZ, then we have a scalable routing benefit - and this end-user network has not had to renumber. (This end-user network might choose to go into business renting out some of its space to other end-users - in which case it is taking on a new kind of role, not really like an ISP, since there is no physical Internet connectivity, but a new role of an MAB Company. In this case, it is not really just an "end-user" network any more, since it is selling Internet services of this new kind to customers.) I anticipate that most end-user networks adopting the new SPI kind of space will be those with PA space at present, including those who only need one or a few IPv4 addresses (or /64s for IPv6. They need to renumber anyway if they change ISPs for another PA service. To adopt the new kind of SPI space, they renumber once, to gain some SPI space rented to them on a long-term basis by some MAB Company - a company (including perhaps an RIR) which has an MAB for this purpose. The MAB company pays for the mapping distribution of all micronets in the MAB, and for the OITRD services to support packets from hosts in non-upgraded networks which are addressed to any address in the MAB. The MAB Company charges their customers for this, according to OITRD traffic, number of mapping changes etc. in addition to whatever they charge for renting a subset of the MAB's address space. So this is renumbering once only for all these smaller networks, and for any large network which doesn't want to run its own MAB. After that, there is no renumbering. Multihoming and portability work fine, including for all packets from hosts in non-upgraded networks (networks without ITRs) - as long as there is an OITRD or more likely multiple OITRDs around the Net, supporting this MAB. - Robin _______________________________________________ rrg mailing list [email protected] https://www.irtf.org/mailman/listinfo/rrg
