1. NAT Traversal in HIP
Xiang LIU
TML/HIIT 1

2. Agenda On Current Internet Traversal technologies (General vs. HIP)‏
DEMO details 2

3. On Current Internet Popular of NAT(IPv4)‏
NATs understand TCP & UDP, but not HIP 3

4. Behave/MMusic NAT traversal Solution
STUN (Hole Punching Technology)‏
TURN
ICE
Others (configure in NAT box)‏ 4

5. Solutions for HIP HIP over UDP (port 50500)‏ STUN <----> RVS
TURN <---->HIP relay(FULL relay)‏
ICE (design for SIP) <----> HIP ICE
code borrowed from PJ project 5

6. Demo Set Up FROG (HIP RELAY) VM ware NAT CRASH OOPS (VM host)‏6

7. DEMO Background Preconditions (registration): Phases:
FROG offers HIP Relay service
All the basic HIP exchange will go thorough FROG
Crash knows the HIT of OOPS
Crash Knows the IP of OOPS, which actually belongs to FROG (public IP)
Phases:
Locator exchange, candidates pairing, reachability testing 7

8. Registration OOPS register itself to FROG using the basic exchange.
OOPS sends keep-live messages to refresh the NAT state 8

9. Locator exchange Crash --I1-- >FROG(relay server) ---I1---> OOPS
Crash <--R1--FROG<---R1--- OOPS
Crash –I2-->FROG---I2--- >OOPS
Crash <--R2--FROG<---R2--- OOPS
Locators are exchanged in R1 and I2 9

10. FULL Relay FROG (HIP RELAY) VM ware NAT CRASH OOPS (VM host)‏10

11. ICE Session
After the basic exchange, the OOPS and Crash start ICE session at the same time.
Reachability testing starts. 11

12. Reachability Testing FROG (HIP RELAY) VM ware NAT CRASH OOPS
(VM host)‏
OOPS
(VM host)‏ 12

13. Establish Security Policies and Associations
ICE will give the best IP:port pair for the SA connection. 13

14. SP/SA
FROG
(HIP RELAY)
VM ware NAT
CRASH
(VM host)‏
OOPS
(VM host)‏ 14

15. Questions? 15