draft-ietf-mip6-location-privacy-ps-03.txt   draft-ietf-mip6-location-privacy-ps-04.txt 
MIP6 Working Group Rajeev Koodli MIP6 Working Group Rajeev Koodli
INTERNET DRAFT Nokia Research Center INTERNET DRAFT Nokia Research Center
Informational Informational
23 October 2006 23 October 2006
IP Address Location Privacy and Mobile IPv6: Problem Statement IP Address Location Privacy and Mobile IPv6: Problem Statement
draft-ietf-mip6-location-privacy-ps-03.txt draft-ietf-mip6-location-privacy-ps-04.txt
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note Task Force (IETF), its areas, and its working groups. Note
that other groups may also distribute working documents as that other groups may also distribute working documents as
Internet-Drafts. Internet-Drafts.
skipping to change at page 4, line 5 skipping to change at page 4, line 5
Consider a Mobile Node at its home network. Whenever it is involved Consider a Mobile Node at its home network. Whenever it is involved
in IP communication, its correspondents can see an IP address valid in IP communication, its correspondents can see an IP address valid
on the home network. Elaborating further, the users involved in peer on the home network. Elaborating further, the users involved in peer
- peer communication are likely to see a user-friendly identifier - peer communication are likely to see a user-friendly identifier
such as a SIP URI, and the communication end-points in the IP such as a SIP URI, and the communication end-points in the IP
stack will see IP addresses. Users uninterested in or unaware of stack will see IP addresses. Users uninterested in or unaware of
IP communication details will not see any difference when the MN IP communication details will not see any difference when the MN
acquires a new IP address. Of course any user can ``tcpdump'' or acquires a new IP address. Of course any user can ``tcpdump'' or
``ethereal'' a session, capture IP packets and map the MN's IP ``ethereal'' a session, capture IP packets and map the MN's IP
address to an approximate geo-location. When this mapping reveals a address to an approximate geo-location. This mapping may reveal
``home location'' of the user, the correspondent can conclude that the "home location" of a user, but a correspondent cannot ascertain
the user has not roamed. Assessing the physical location based on IP whether the user has actually roamed or not. Assessing the physical
addresses is similar, although there are differences, to assessing location based on IP addresses has some similarities to assessing the
the geographical location based on the area-code of a telephone geographical location based on the area-code of a telephone number.
number. The granularity of the physical area corresponding to an IP The granularity of the physical area corresponding to an IP address
address can vary depending on how sophisticated the available tools can vary depending on how sophisticated the available tools are, how
are, how often an ISP conducts its network re-numbering, etc. often an ISP conducts its network re-numbering, etc. And, an IP
address cannot also guarantee that a peer is at a certain geographic
area due to technologies such as VPN and tunneling.
When the MN roams to another network, the location privacy problem When the MN roams to another network, the location privacy problem
consists of two parts: revealing information to its correspondents consists of two parts: revealing information to its correspondents
and to on-lookers. and to on-lookers.
With its correspondents, the MN can either communicate directly or With its correspondents, the MN can either communicate directly or
reverse tunnel its packets through the Home Agent. Using reverse reverse tunnel its packets through the Home Agent. Using reverse
tunneling does not reveal the new IP address of the MN, although tunneling does not reveal the new IP address of the MN, although
end-to-end delay may vary depending on the particular scenario. With end-to-end delay may vary depending on the particular scenario. With
those correspondents with which it can disclose its new IP address those correspondents with which it can disclose its new IP address
skipping to change at page 5, line 48 skipping to change at page 5, line 48
current point of attachment unless the MN uses route optimization current point of attachment unless the MN uses route optimization
with them. with them.
4. Conclusion 4. Conclusion
In this document, we have discussed the location privacy problem In this document, we have discussed the location privacy problem
as applicable to Mobile IPv6. The problem can be summarized as as applicable to Mobile IPv6. The problem can be summarized as
follows: disclosing Care of Address to a correspondent and revealing follows: disclosing Care of Address to a correspondent and revealing
Home Address to an on-looker can compromise the location privacy Home Address to an on-looker can compromise the location privacy
of a Mobile Node, and hence that of a user. We have seen that of a Mobile Node, and hence that of a user. We have seen that
bidirectional tunneling allows a MN to protect its CoA to the CN, and bidirectional tunneling allows a MN to protect its CoA to the CN.
together with ESP encryption allows the MN to protect its HoA from And, ESP encryption of inner IP packet allows the MN to protect its
the on-lookers on the MN - HA path. HoA from the on-lookers on the MN - HA path.
However, with route optimization, the MN will reveal its CoA to the However, with route optimization, the MN will reveal its CoA to the
CN. Moreover, the HoA is revealed to on-lookers in the data packets CN. Moreover, route optimization causes the HoA to be revealed to
as well as in Mobile IPv6 signaling messages. The solutions to this on-lookers in the data packets as well as in Mobile IPv6 signaling
problem are expected to be protocol specifications assuming the messages. The solutions to this problem are expected to be protocol
existing Mobile IPv6 functional entities, namely, the Mobile Node, specifications assuming the existing Mobile IPv6 functional entities,
its Home Agent and the Correspondent Node. namely, the Mobile Node, its Home Agent and the Correspondent Node.
5. IANA Considerations 5. IANA Considerations
There are no IANA considerations introduced by this draft. There are no IANA considerations introduced by this draft.
6. Security Considerations 6. Security Considerations
This document discusses location privacy because of IP mobility. This document discusses location privacy because of IP mobility.
Solutions to provide location privacy, especially any signaling over Solutions to provide location privacy, especially any signaling over
the Internet, must be secure in order to be effective. Individual the Internet, must be secure in order to be effective. Individual
solutions must describe the security implications. solutions must describe the security implications.
7. Acknowledgment 7. Acknowledgment
Thanks to James Kempf, Qiu Ying and Sam Xia for the review and Thanks to James Kempf, Qiu Ying and Sam Xia for the review and
feedback. Thanks to Jari Arkko and Kilian Weniger for the last call feedback. Thanks to Jari Arkko and Kilian Weniger for the last call
review and for suggesting improvements and text. review and for suggesting improvements and text.
References Informative References
[1] W. Haddad and et al. Privacy for Mobile and Multi-homed Nodes: [1] W. Haddad and et al. Privacy for Mobile and Multi-homed Nodes:
MoMiPriv Problem Statement (work in progress). Internet Draft, MoMiPriv Problem Statement (work in progress). Internet Draft,
Internet Engineering Task Force, October 2004. Internet Engineering Task Force, October 2004.
[2] J. Polk, J. Schnizlein, and M. Linsner. DHCP Option for [2] J. Polk, J. Schnizlein, and M. Linsner. DHCP Option for
Coordinate-based Location Configuration Information. Request for Coordinate-based Location Configuration Information. Request for
Comments 3825, Internet Engineering Task Force, July 2004. Comments 3825, Internet Engineering Task Force, July 2004.
8. Author's Address 8. Author's Address
 End of changes. 5 change blocks. 
18 lines changed or deleted 20 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/