A Evolvable RANGI Transition Strategy

Transcription

1 A Evolvable RANGI Transition Strategy 1

2 Overview 5 Types of Sites: Progressive deployment of RANGI Interoperability between Type i and j (Total 10 cases) More RANGI deployment Smaller BGP Tables Less Address Shortage Easier Mobility and Multihoming 2

3 RANGI Deployment Levels 1. Full RANGI: RANGI enabled border routers and RANGI enabled hosts 2. Partial RANGI: RANGI enabled border routers acting as RANGI Proxy but hosts are RANGI unaware v6 R RANGI Proxy RANGI 3. Null RANGI: Legacy / site with RANGI unaware border routers (no Proxy) and RANGI unaware hosts v4 RANGI Proxy v6 BR v4 BR 3

4 Interoperability Cases 1. Full RANGI Full RANGI 2. Full RANGI - Partial RANGI() and vice versa 3. Full RANGI - Partial RANGI() and vice versa 4. Full RANGI Null RANGI() and vice versa 5. Full RANGI Null RANGI() and vice versa (TBD) 4

5 Records A Records: Contain 32-bit addresses. Legacy hosts always ask for A records AAAA Records: Contain 128-bit addresses. Legacy hosts always ask for AAAA records. BAAA Records: Contain 128-bit RANGI IDs. RANGI hosts always ask for BAAA records. RANGI-aware servers: If BAAA is requested, Return BAAA. IF AAAA is requested but BAAA is found, Consult ID-> mapping and return AAAA 5

6 Transition Assumptions Not all servers are assumed to be RANGI aware. servers are easy to update with RANGI software RANGI Proxies allow incremental advantages and so will be deployed first before full RANGI conversion. 6

7 1. Full RANGI Full RANGI FQDN->ID 1 and 2 Host A obtains the identifier of host B as an BAAA record in reply. 3 and 4. Host A gets host B s ID resolved to host B s locator(96 bit LDID + 32 bit Local locator ) through the hierarchical DHT mapping system 3 ILM ID-> RANGI host Legacy host Host A (RANGI) /RANGI Internet LDBR 7 Host B (RANGI) 5. Host A builds RANGI packets and sends them to host B. 6. RANGI based routing on the destination LDID 7 7. Destination site LDBR forwards the RANGI packets based on the 32 bit local locator of host B

8 2. Full RANGI Partial RANGI() FQDN ID 3 and 4. Host A obtains the identifier of host B as an BAAA record in reply and 6. Host A gets host B s ID resolved to proxy s locator through the hierarchical DHT mapping system 6 5 ILM ID 2. Proxy registers its locator mapped to B s Identifier in the ILM ILM 1. Proxy registers a BAAA record for host B in the 1 Host A (RANGI) 7 7. Host A builds RANGI packets and sends them to host B. LDBR 8 /RANGI Internet 8. /RANGI based routing routes the packet to the Proxy Proxy 9. Proxy removes the s from the packet and forwards them as simple packet to the host. Proxy remembers the ID of A for converting return packets to RANGI 9 2 Site Host B () 8

9 3. Partial RANGI() Full RANGI 8. Proxy returns B s to A. Also, it remembers A s identifier 1. Proxy registers a BAAA record for host A in the 3. Host A makes (A + AAAA) query for B s FQDN 1 4 and 5. Proxy converts the request to ( A + AAAA + BAAA) request and sends it to the. replies with a BAAA record for B ILM RANGI host Legacy host 2. Proxy registers its locator mapped to A s Identifier in the ILM Host A () 9 8 Site Proxy /RANGI Internet 10 6 and 7. Proxy gets B s identifier (BAAA) mapped to B s locator from the ILM LDBR 11 Host B (RANGI) 9. Host A builds packets and sends them to host B. 10. Proxy converts the packets from host A to RANGI packets for host B and sends them over the /RANGI internet LDBR forwards the RANGI packet to host B

10 4. Full RANGI Partial RANGI() 3 and 4. Host A obtains the identifier of host B as an BAAA record in reply. Host A (RANGI) FQDN ID 7 7. Host A builds RANGI packets and sends them to host B and 6. Host A gets host B s ID resolved to proxy s locator through the hierarchical DHT mapping system LDBR /RANGI based routing routes the packet to the Proxy 10 ILM /RANGI Internet ID 2. Proxy registers its 96 bit LDID + 32 bit address of host B mapped to B s Identifier in the ILM Proxy 9 ILM Site 1. Proxy registers a BAAA record for host B in the Host B () 9. Proxy removes the s from the packet and forwards them as simple packet to the host. Proxy remembers the ID of A for converting return packets to RANGI 2 1

11 5. Partial RANGI() Full RANGI 8. Proxy remembers B s ID and RANGI locator. It assigns a local address to B for use by A in constructing packets for B Host A () 9 3. Host A makes A query for B s FQDN 8 Site 9. Host A builds packets and sends them to host B. 1. Proxy registers a BAAA record for host A in the and 5. Proxy converts the request to ( A + AAAA + BAAA) request and sends it to the. replies with a BAAA record for B ILM /RANGI Internet Proxy Proxy converts the packets from host A to RANGI packets for host B and sends them over the /RANGI internet 6 7 LDBR 2 6 and 7. Proxy gets B s identifier (BAAA) mapped to B s locator from the ILM LDBR forwards the RANGI packet to host B ID 2. Proxy registers its 96 bit LDID + 32 bit address of host A mapped to A s Identifier in the ILM Host B (RANGI) 11

12 Limitations of Null-RANGI Full RANGI transitions The Transition mechanisms of Null RANGI(Legacy and legacy )- Full RANGI only aim at maintaining minimal reachability between these sites. The advantages of RANGI deployment such as Multi-homing, mobility, traffic engineering etc are not available in such scenarios. Also, RANGI LDBR s need to be aware of such a communication session and not apply RANGI mechanisms of traffic engineering and mobility by header re-writing on packets for these sessions 12

13 6. Full RANGI Legacy RANGI host Host A (RANGI) 1 and 2. Host A asks for (BAAA + AAAA + A) record of host B. replies with a AAAA record of host B 3 1 FQDN-> 2 LDBR 4 /RANGI Internet Router Null RANG()Site 5 Legacy host Host B () 3. Host A (dual stack behavior) builds packets and sends them to host B. 4. LDBR is dual stacked and forwards the packet into the RANGI/ internet Destination site border router forwards the packets to host B.

14 7. Legacy Full RANGI 5. sends back 128 bit -like RANGI locator of host B 1. Host A asks for AAAA + A) record of host B. Host A () 6. Host A constructs an packet with B s RANGI locator. 5 1 Null RANG()Site 6 2. finds a BAAA (host ID of B) record for host B s FQDN. realizes that the original request was for AAAA and hence from a legacy host 2 Router 4 FQDN-> /RANGI Internet 7 7. The RANGI locator is routable in the /RANGI internet 3 3. The forwards the BAAA record of host B to the hierarchical DHT based mapping system to get it mapped to B s RANGI LDBR ILM 4. The ID- mapping system returns the RANGI of B ID-> Host B (RANGI) 8. Destination site LDBR forwards the packets to host B. Both, LDBR and host B are dual stack and so they can handle an session 8 RANGI host Legacy host 14

15 8. Full RANGI Legacy RANGI host Host A (RANGI) 1 and 2. Host A asks for (BAAA + AAAA + A) record of host B. replies with a A record of host B 3 3. Host A (dual stack behavior) builds packets and sends them to host B. 1 FQDN 2 LDBR Internet 4 4. LDBR is dual stacked and forwards the packet into the internet Need to show over packet Router Null RANG()Site 5 5. Destination site border router forwards the packets to host B Legacy host Host B () 15

16 TBD 9. Legacy to RANGI Hosts 16

17 Routing Scalability RANGI Aware [< > RANGI Aware] Does not need a PI address for stub sites seeking routing independence Evolution of Benefits RANGI Proxy [ <-> RANGI aware] Does not need a PI address for stub sites seeking routing independence RANGI Proxy [<-> RANGI aware] Does not need a PI address for stub sites seeking routing independence Scalable Traffic Engineering Scalable site traffic Engineering Scalable Site traffic engineering Scalable site traffic engineering Scalable support for Multi-Homing Multi-homing without PI prefixes Multi-homing without PI prefixes Multi-homing without PI prefixes Scalable Mobility Feasible Host mobility and site mobility Host mobility through triangulation at the proxy, Site mobility allowed Host mobility through triangulation at the proxy, Site mobility allowed Simplifying Renumbering Simplified - when changing provider, only a fixed common prefix has to be changed for all hosts All bindings at the proxy need to be renumbered Proxy could be a single point of failure All bindings at the proxy need to be renumbered Proxy could be a single point of failure /Identifier split Host aware Host unaware Host unaware Routing Quality TBA TBA TBA Routing Security Provision for end host end host secure routing and secure communication Provision for secure communication till the proxy. Legacy security between proxy and end host Provision for secure communication till the proxy. Legacy security between proxy and end host Deployability Requires host + site border router modifications + new RR Requires site border router modifications + Additional proxy functions at the site routers+ New mechanism Requires site border router modifications + Additional proxy functions at the site routers + New Mechanism 17

18 Summary Complete transition strategy starting from current Internet to RANGI-aware Internet Three Steps: 1. update, 2. Site Proxies, 3. RANGI-aware Hosts The benefits increase as deployment levels and investment increases. 18