Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
HIP RG, 63rd IETF Meeting Paris, August 5, 2005 “HIP Privacy Extensions” draft-matos-hip-privacy-extensions-00.txt Alfredo Matos, Justino Santos, Rui Aguiar IT Aveiro João Girão, Marco Liebsch NEC Europe Motivation ● ● ● Location privacy is a growing requirement Current Internet architecture does not provide location privacy HIP is an end to end protocol – ● ● Initiator/Responder learn the location of each other HIP decouples identifier and locator Separate layers provide more “space” for a location privacy solution Architecture: Topology ● ● ● Rendezvous Agent (RVA) – HI to IP resolution – assigns globally routable IP addresses (IPg) to attendants – readdresses IPg's to HITs and viceversa – handles mobility for attendants (through delegation) RVA Protected Area – no IPg are used inside these areas for routing – identity based routing RVA Advertisement System – Sustained by the AR – Announces the AR and RVA Identifiers Mobility ● Intra-RVA Handover – ● Handled locally between RVA and HMN Inter-RVA Handover – Base Exchange with new RVA – Update procedure to RVS – RVA to RVA signaling Location Privacy Gains ● ● ● Initiator never learns a Responder's location and vice versa An attacker is only able to learn a HMN's location if in the same AN and if no additional protection mechanisms are used (but this is also tied with L2 problem) Globally assigned IPv6 addresses and RVA protected areas limit the amount of location information revealed in the core network: ● ● ● an attacker cannot track local mobility an attacker may possibly learn inter RVA movement; size of RVA areas determines the amount of geographical information revealed Future Steps Fast Mobility ● – RVA supported (old and new RVA signaling) – allowing bi-cast data forwarding Network mobility ● – Yet another hierarchy level, a Mobile Router acts as an RVA Certification ● – How to do it – concrete definition. Depends on CERT parameter. ● Interesting topic for the HIPRG work ? ● Future Steps – In/Out of the scope of the HIPRG ? ● Additional proposals for in-scope items ?