1. Routing Architecture for the Next-Generation Internet (RANGI) draft-xu-rangi-01.txt Xiaohu Xu (xuxh@huawei.com)xuxh@huawei.com IETF76 Hiroshima

2. Page 2 Design Goals for RANGI Hierarchical Management ID/locator split New Internet Architecture  Reasonable Business Model  Clear Trust Boundary  Mobility and Multi-homing  Routing Scalability  Business-friendly  Cryptographic Host Identifier Deployable Security  IPv4/IPv6 Coexistence and Transition  Transition Mechanism for RANGI

3. Page 3 RANGI Protocol Stack Demo Transport Flat Host ID (128bit) Locator (128bit) Data Link Transport Network Data Link IP HIP Transport Hierarchical Host ID (128bit) IPv4-embeded IPv6 Address (128bit) Data Link RANGI

4. Page 4 Host ID AD （ Administrative Domain ） ID –Organizational semantics and trust boundaries ． –Reasonable business model for the ID to locator mapping system ． Local Host ID –The hash over the AD ID and the public key of the host. –Secure the ID ownership. Use CGA (RFC3972) as host ID in our implementation for simplicity AD IDLocal Host ID Region IDCountry IDAuthority ID n bits (n=64)128-n bits 层次化 主机 ID Host ID (example)

5. Page 5 Locator LD （ Locator Domain ） ID –Globally identify each LD (e.g., site network). –LDID is actually PA (Provider Assigned) /96 IPv6 prefix. LL (Local Locator) –Each LD uses independent IPv4 address space (e.g., private address). –When ISP changed, only LDID changes, local locator unchanged. GL (Global Locator)= LDID + LL Use ISATAP (RFC5214) address as GL in our implementation for simplicity LD IDLL(IPv4) 96 bits32 bits 层次化 Locator

6. Page 6 层次化 路由系统 ID to Locator Resolution Hierarchical DHT based Mapping System –Reasonable business model and clear trust boundary. Use reverse-DNS as mapping system in our current implementation for simplicity Country 1 Root City 2City 3 Country 2Country n DHT City 1 City n DHT Routing based on the AD ID Routing based on the local host ID (i.e. Hash value) Mapping System

7. Page 7 Routing and Forwarding Use ISATAP like mechanism in site (edge) networks Use Softwire mechanism in provider ASes –Either intra-AS softwire [RFC5565] or inter-AS softwire (draft-xu- softwire-tunnel-endpoint) mechanism works well. Routing System LD #1 (Pub/Pri IPv4) HI(A)->HI(B) IPv4(A) ->IPv4(BR1) IPv6(A)->IPv6(B) IPv4(BR2) -> IPv4(BR3) IPv6(A)->IPv6(B) IPv4(BR4) -> IPv4(B) IPv6(A)->IPv6(B) Payload HI(A)->HI(B) Payload HI(A)->HI(B) Payload IPv4 Internet LD #3 (Pub/Pri IPv4) Host A Host B BR3(AFBR)BR1BR2(AFBR) BR4

8. Page 8 Site Multi-homing Multiple PA LDIDs are allocated to a multi-homed site network –Routing system scales well due to the usage of multiple PA locators. LD #1 ISP #2 Host A ISP #1 LDID_1 assigned by ISP #1 LDID_1+LL(A)->GL(B) Source LD ID based policy routing LDID_1+LL(A)->GL(B) Host B LDID_1+LL(A)->GL(B) LDID_2 assigned by ISP #2 BR1 BR2 BR3 Routing System

9. Page 9 Site-controlled Traffic-Engineering BR1 rewrites the source LDID before performing source- based policy routing LD #1 ISP #2 Host A ISP #1 LDID_1+LL(A)->GL(B) LDID_2+LL(A)->GL(B) Host B LDID_2+LL(A)->GL(B) BR1 BR2 BR3 Site LDBR rewrites source LDIDs of the outgoing packets before performing source-based policy routing. –Borrow ideas from GSE, Six/One. LDID_1 assigned by ISP #1 LDID_2 assigned by ISP #2 Routing System

10. Page 10 Site-controlled Traffic-Engineering LD #1 ISP #2 Host A ISP #1 Host B GL(B) -> LDID_2+LL(A) LDID_1 分配自 ISP #1 LDID_2 分配自 ISP #2 BR1 BR2 BR3 Return packets follow the same path as the outgoing packets travel along. Routing System

11. Page 11 How RANGI Matches the RRG Design Goals Required Routing Scalability ID/locator Split Route Security Deployable Strong desired Multi-homing Traffic-Engineering Simplified Renumbering Route Stability Desired Mobility

12. Page 12 Next Steps Implement and verify this architecture –Funded by China National High-Tech Program (863). Optimize it according to feedbacks and experiments Solicit more participants who are interested in this architecture