Presentation is loading. Please wait.

Presentation is loading. Please wait.

for the Next-Generation Internet (RANGI) draft-xu-rangi-01.txt

Similar presentations


Presentation on theme: "for the Next-Generation Internet (RANGI) draft-xu-rangi-01.txt"— Presentation transcript:

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

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

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

4 Host ID AD(Administrative Domain)ID Local Host ID
层次化 主机ID AD ID Local Host ID Region ID Country ID Authority ID n bits (n=64) 128-n bits (example) 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 只介绍标题。围绕图进行介绍。 Page 4

5 Locator LD(Locator Domain)ID LL (Local Locator)
层次化 Locator Locator 96 bits 32 bits LD ID LL(IPv4) 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 Page 5

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

7 Routing and Forwarding
System Payload Payload Payload HI(A)->HI(B) HI(A)->HI(B) HI(A)->HI(B) IPv6(A)->IPv6(B) IPv6(A)->IPv6(B) IPv6(A)->IPv6(B) IPv4(A) ->IPv4(BR1) IPv4(BR2) -> IPv4(BR3) IPv4(BR4) -> IPv4(B) Host A LD #1 (Pub/Pri IPv4) Host B LD #3 (Pub/Pri IPv4) BR1 BR2(AFBR) BR3(AFBR) BR4 IPv4 Internet Use ISATAP like mechanism in site (edge) networks Use Softwire [RFC5565]mechanism in provider ASes Either intra-AS softwire or inter-AS softwire mechanism works well. IPV6只是一个实例,强调通用性。之前增加一个通用模型的SLIDE。 Page 7

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

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

10 Site-controlled Traffic-Engineering
Routing System 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. Page 10

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

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 Page 12


Download ppt "for the Next-Generation Internet (RANGI) draft-xu-rangi-01.txt"

Similar presentations


Ads by Google