Tony - please see attached for the IRON-RANGER rebuttal. Fred fred.l.temp...@boeing.com
________________________________ From: rrg-boun...@irtf.org [mailto:rrg-boun...@irtf.org] On Behalf Of Tony Li Sent: Wednesday, February 10, 2010 1:37 PM To: 'RRG' Subject: Re: [rrg] Reminder Hi folks, Remember this? I've seen one submission. Are folks working on things? Tony ---------------- Hi all, We've had a bit of a schedule slip. We are still trying to hit a final document date of Mar. 8. That gives us just less than 7 weeks. The next deadline for a rebuttal is Feb. 9. The deadline for counterpoints will then be Mar. 2. This will give us a few days for final document prep. The word count limit for the rebuttal is 500 words. Regards, Tony
The Internet Routing Overlay Network (IRON) [draft-templin-iron] is a scalable Internet routing architecture that builds on the RANGER recursive enterprise network hierarchy [draft-templin-ranger]. IRON bonds together participating RANGER networks using VET [draft-templin-intarea-vet] and SEAL [draft-templin-intarea-seal] to enable secure and scalable routing through automatic tunneling within the Internet core. The IRON-RANGER automatic tunneling abstraction views the entire global Internet DFZ as a virtual NBMA link similar to ISATAP [RFC5214]. IRON-RANGER is an example of a Core-Edge Separation (CES) system. Instead of a classical mapping database, however, IRON-RANGER uses a hybrid combination of a proactive dynamic routing protocol for distributing highly aggregated Virtual Prefixes (VPs) and an on-demand data driven protocol for distributing more-specific Provider Independent (PI) prefixes derived from the VPs. The IRON-RANGER hierarchy consists of recursively-nested RANGER enterprise networks joined together by IRON routers that participate in a global BGP instance. The IRON BGP instance is maintained separately from the current Internet BGP Routing LOCator (RLOC) address space (i.e., the set of all public IPv4 prefixes in the Internet). Instead, the IRON BGP instance maintains VPs taken from Endpoint Interface iDentifier (EID) address space, e.g., the IPv6 global unicast address space. To accommodate scaling, only O(10k) - O(100k) VPs are allocated e.g., using /20 or shorter IPv6 prefixes. IRON routers lease portions of their VPs as Provider Independent (PI) prefixes for customer equipment (CEs), thereby creating a sustaining business model. CEs that lease PI prefix propagate address mapping(s) throughout their attached RANGER networks and up to VP-owning IRON router(s) through periodic transmission of "bubbles" with authenticating and PI prefix information. Routers in RANGER networks and IRON routers then securely install PI prefixes in their FIBs, but do not inject them into the RIB. IRON routers therefore keep track of only their customer base via the FIB entries and keep track of only the Internet-wide VP database in the RIB. Each IRON router therefore has full knowledge of all VPs but only partial knowledge of all PI prefixes. IRON routers propagate more-specific prefixes using secure redirection. When CE 'A' within RANGER network 'X' sends a packet to CE 'E' within RANGER network 'Y', the packet ascends through the 'X' hierarchy until it reaches IRON router 'B' that connects 'X' to the IRON. 'B' forwards the packet to IRON router 'C' owned by the leasing agency for the VP that covers the PI prefix for 'E'. 'C' then forwards the packet to IRON router 'D' that connects 'Y' to the IRON, then sends a redirect message to 'B'. 'B' then places the route 'E'->'D' into its FIB but does not advertise it within the RIB. FIB entries are kept as soft state that is purged after expiration or route failure. Neighbor unreachability detection is used to detect failure. CEs can move from old RANGER networks and re-inject their PI prefixes into new RANGER networks. This would be accommodated by IRON-RANGER as a site multihoming event while host mobility and true locator-ID separation is accommodated via HIP [5201].
_______________________________________________ rrg mailing list rrg@irtf.org http://www.irtf.org/mailman/listinfo/rrg
