1 / 10

IETF #64, Nov 2005

Route Optimization and Location Privacy using Tunneling Agents (ROTA) draft-weniger-rota-01 Kilian Weniger, Takashi Aramaki. IETF #64, Nov 2005. Background.

sherillj
Download Presentation

IETF #64, Nov 2005

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. Route Optimization and Location Privacy using Tunneling Agents (ROTA)draft-weniger-rota-01Kilian Weniger, Takashi Aramaki IETF #64, Nov 2005

  2. Background • „Location privacy is the ability to prevent other parties from learning one's current or past location. In order to get such ability, the mobile node must conceal any relation between its location and the personal identifiable information“ [draft-haddad-momipriv-problem-statement-02] • [draft-ietf-mip6-location-privacy-ps-00] describes IP address location privacy problem in MIPv6 context and identifies two main problems • disclosure of CoA to CN • revealing HoA to eavesdropper • Our draft addresses problem 1 • Proposed solutions for this problem • reverse tunneling • HMIPv6

  3. Problem Providing location privacy and optimized routing simultaneously location privacy in terms of hiding location from CN Scenario Mobile-to-mobile communication (e.g., VoIP) Both users request location privacy Both users have different home networks and are away from home Problem definition and scenario MN1‘s HA MN2‘s HA MN1 MN2 Fig:Example scenario

  4. Reverse tunneling to HA CoA is hidden from CN, but optimized routing cannot be provided tunneled data packets non-tunneled data packets Reverse tunneling in given scenario MN1‘s HA MN2‘s HA MN1 MN2 Fig:Data path in case of reverse tunneling

  5. Reverse tunneling + bootstrapping with local HAs (integrated scenario) CoA is hidden from CN and optimized routing is provided, but potential to compromise location privacy since HoA contains location information however, CN would have to know that MN‘s HA is local granularity of location information depends on location of local HA Reverse tunneling in given scenario MN1‘s HA(local) MN2‘s HA(local) MN1 MN2 Fig: Data path in case of reverse tunneling after bootstrapping with local HAs

  6. HMIPv6 (L)CoA is hidden from CN and optimized routing can be provided, but location privacy support is limited, since RCoA is disclosed granularity of location information depends on location of MAP HMIPv6 in given scenario MN1‘s HA MN2‘s HA MAP MAP MN1 MN2 Fig: Data path in HMIPv6 route optimization mode

  7. Summary • MIPv6 can provide limited support for simultaneous location privacy and optimized routing • „location privacy“ in terms of hiding MN‘s location from CN

  8. (Optional) route optimization by reverse tunneling to Tunneling Agents (TA) TA is outside of home link TA maintains bindings for HoAs not matching TA prefix MN‘s home link (and HoA) does not change TA can e.g. be co-located with MN1‘s HA or MN2‘s HA local HA or MAP Possible approach for improving location privacy and optimized routing support Binding Cache HoAMN2CoAMN2 (H) HoAMN1CoAMN1 (TA) MN1‘s HA MN2‘s HA/ MN1‘s TA Binding Cache HoAMN1CoAMN1 (H) MN1 MN2 Fig: Data path in case TA is co-located with MN‘s HA

  9. (Optional) route optimization by reverse tunneling to Tunneling Agents (TA) TA is outside of home link TA maintains bindings for HoAs not matching TA prefix MN‘s home link (and HoA) does not change TA can e.g. be co-located with MN1‘s HA or MN2‘s HA local HA or MAP Binding Cache HoAMN2ATA2 (TA) HoAMN1CoAMN1 (TA) HA or MAP/MN1‘s TA HA or MAP/MN2‘s TA Binding Cache HoAMN1ATA1 (TA) HoAMN2CoAMN2 (TA) Possible approach for improving location privacy and optimized routing support MN1‘s HA MN2‘s HA MN1 MN2 Fig: Data path in case TA is co-located with local HAs/MAPs

  10. Questions • Is there interest in improving MIPv6 support for simultaneous location privacy and optimized routing? • „location privacy“ in terms of hiding MN‘s location from CN • How to proceed? • Other comments?

More Related