1 / 13

RANGI (Routing Architecture for Next Generation Internet) Experiment Report

RANGI (Routing Architecture for Next Generation Internet) Experiment Report. Meilian LU, Xiangyang GONG, Wendong WANG <mllu, xygong , wdwang@bupt.edu.cn > Xiaohu Xu, Dacheng Zhang < xuxiaohu , zhang dacheng@huawei.com >. Background. What is RANGI?

maalik
Download Presentation

RANGI (Routing Architecture for Next Generation Internet) Experiment Report

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RANGI (Routing Architecture for Next Generation Internet) Experiment Report Meilian LU, Xiangyang GONG, Wendong WANG <mllu, xygong, wdwang@bupt.edu.cn> Xiaohu Xu, Dacheng Zhang <xuxiaohu, zhangdacheng@huawei.com>

  2. Background • What is RANGI? • A new ID/locator split based routing and addressing architecture. • Its major difference from HIP: hierarchical host identifiers. • This report describes the issues of implementation for RANGI • Host stack implementation (based on HIPL codes) • Network infrastructure implementation • Host mobility and muti-homing experiments 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 HIP RANGI IP

  3. n bits 128-n bits AD ID Local Host ID Country ID Authority ID Region ID Host Stack Implementations • RANGI completed a further extension to HIP • Reuses the user-space pattern of HIPL • CGA authentication in the base exchange: authenticate the binding relationship between sender’s ID and public key to confirm the authenticity of the data source • Common functions: • ID generation and registration. • ID->Locator mapping registration and resolution. • ID/Locator split based communication. Host ID Format Host ID Implementation Example

  4. Infrastructure Implementations • No impact on the traditional DNS infrastructure • The AAAA RR fields now are filled with host identifiers. • RANGI infrastructure consists of two parts: • IDMS is in charge of ID management, including the registration of host ID • ILMS is in charge of ID->Locator Mapping service, Including mapping registration, updating and resolution.

  5. ID Management System(IDMS) • IDMS has a hierarchical structure • Each IDMS is responsible for the management of IDs which belong to its AD domain. • Guaranteeing the uniqueness of ID within each AD domain • Maintaining TSIG shared secret per ID entry for protecting the dynamic updating process in the ILMS.

  6. ID to Locator Mapping System (DNS based) • ILMS based on reverse DNS • The mapping system server organizes hierarchical structure in accordance with the identity of RANGI • Brings trust boundaries • Interact with the corresponding IDMS to obtain TSIG shared secret for protecting the dynamic updating process

  7. ID to Locator Mapping System (DNS+DHT based) • ILMS based on DNS-DHT hybrid resolution • DNS is used to divide different management organizations • DHT is used to maintain the ID/Locator mapping information. • a DNS-DHT converter is needed for changing DNS message to DHT message

  8. ILM LD #2 DNS DNS ILM DNS LDBR2 LD #1 LD #3 LDBR3 LDBR1 R1 R2 ILMS update1 MN 1 RA 0 RS(可选) ILMS update2 move ILMS update 2updata1 CN 3updata2 4 updata3 MN CN update Host Mobility

  9. DUT7 DUT1 DUT3 DUT9 DUT11 DUT10 DUT4 DUT6 Experiment: Host Mobility IPv4 Local ILMS IDMS IPv4/IPv6 2003:0:3::/64 6PE G3/1/0 G3/1/0 G3/1/2 G3/1/2 G3/1/11 G3/1/1 G3/1/3 G3/1/7 2003:0:12::/64 2004:0:12::/64 2003::/16(AS#3) DUT4 2005:0:11::/64 6PE PC#22 G3/1/3 G3/0/0 G3/0/1 G3/1/10 G3/1/10 G3/1/8 G3/1/8 G3/0/9 G3/1/7 G3/1/3 G3/1/9 G3/1/9 Site #2 (IPv6) G3/0/0 Site #1 (IPv6) G3/0/4 G3/1/6 2005::/16(ISP#3) 2005::/16(AS#5) 6PE G3/1/7 G3/1/10 G3/1/5 G3/1/5 G3/1/4 G3/1/6 G3/0/0 G3/0/0 2004::/16(AS#4) 2004:0:4::/64 2004:0:6::/64 Authority ILMS root DNS server

  10. Views from Network Operators • Administration of ID namespace • AD ID is hierarchical, it consists of three administrative level: country level, authority level and region level. ID administrations have a corresponding hierarchical reverse tree structure. • the root part is a global administration which is similar asICANN • the root administration divides the namespace into some ID sub-namespaces

  11. Views from Network Operators • Security Considerations • IDMS uses certification, signature and other techniques for authentication and message integrity protection. • ILMS • use DNSSEC to provide the source authentication and integrity protection for resource records; • use DNS transaction authentication protocol TSIG (Secret Key Transaction Authentication for DNS) to protect update operation of mapping information

  12. Conclusion • RANGI can effectively support ID/Locator split • Support mobility, multi-homing and traffic engineering • From the introduction of hierarchical concept, RANGI has a reasonable business model and clear trust boundaries • Solve the problem of routing scalability

  13. Any Comments?

More Related