RANGI (Routing Architecture for Next Generation Internet) Experiment Report

Meilian LU, Xiangyang GONG, Wendong WANG Xiaohu Xu, Dacheng Zhang IETF82, TAIWAN

Background

Transport Network Transport Flat Host ID (128bit) Locator (128bit) Transport Hierarchical Host ID (128bit) IPv4-embeded IPv6 Address (128bit) Data Link Data Link Data Link HIP RANGI IP • 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

AD ID n bits

Host Stack Implementations

128-n bits Local Host ID Country ID Authority ID Region ID Host ID Format Host ID Implementation Example • 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.

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.

IDMS IDMS ID REG IST RAT ION or DE LET E ID_TO_LOC REGISTRATION IDMS ID_TO _LOC UPDAT E or RESOL UTION ILMS ILMS ILMS

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.

IANN-like Root Country level ID management system National ID authority National ID authority Beijing China Mobile China Japane se China Telec om … Shanghai … … Ameri ca Califo rnia …

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

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

Host Mobility

LD #2 MN R1 LD #1 LDBR1 0 RS( 可 选 ) R2 1 RA DNS DNS LDBR2 LDBR3 LD #3 CN MN

Experiment: Host Mobility

IPv4 IPv4/IPv6 Local ILMS IDMS 2003:0:12::/64 2004:0:12::/64 PC#22 G3/0/0 G3/1/10 G3/0/9 Site #1 (IPv6) 6PE G3/1/0 G3/1/11 DUT1 G3/1/2 G3/1/1 G3/1/2 G3/1/3 2003::/16(AS#3) 2003:0:3::/64 G3/1/0 DUT3 G3/1/7 G3/0/1 DUT10 G3/0/4 G3/1/3 G3/1/6 DUT7 G3/1/8 G3/1/7 DUT4 6PE G3/1/8 DUT9 G3/1/10 G3/1/9 DUT11 G3/0/0 2005:0:11::/64 Site #2 (IPv6)

wlan2

6PE G3/1/10 G3/0/0 2004:0:4::/64 DUT4 G3/1/5 G3/1/5 G3/1/4 G3/1/6 2004::/16(AS#4) G3/1/7 DUT6 G3/0/0 2004:0:6::/64

wlan1

Authority ILMS update root DNS server

PC#23

DNS Update

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 as ICANN – the root administration divides the namespace into some ID sub-namespaces

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

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

Any Comments?