The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Author Ammar Salih
Last updated 2012-11-14
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet-Draft                                       Ammar J. Salih

Title:            IP-LOC
Expires:          May 14, 2013
Intended status:  Proposed Standard
Filename:         draft-add-location-to-ipv6-header-00.txt

Status of this Memo

This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF).  Note that other groups may also distribute
working documents as Internet-Drafts.  The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time.  It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."

           This Internet-Draft will expire on May 14, 2013.

Copyright Notice

Copyright (c) 2012 IETF Trust and the persons identified as the
document authors.  All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions
Relating to IETF Documents (http://trustee.ietf.org/license-info)
in effect on the date of publication of this document.  Please
review these documents carefully, as they describe your rights and
restrictions with respect to this document.

                     Adding GPS location to IPv6 header


 This document describes IP-LOC, a proposed extension which suggests
adding GPS coordinates to IPv6 header. 

The current method of determining location of IP traffic is through
IP address registration database, which is not very accurate as it
depends on how the ISP registers its IP subnets, that is normally
done in a country/city format.

It also assumes that in the future, GPS capability will be added to
the router itself (just like smart phones) and packet marking and
classification based on geo-location will be required.

QoS, firewall and routing based on geo-location will be highly
required when mobile routers move from one geo-location to another
which has different policy.

Benefits of adding GPS location to IPv6 header (IP-LOC)

Web Services: getting more accurate locations will enhance many
services provided by the web, like Targeted Advertising (for
example, I would get Ads regarding restaurants available in my
neighborhoods instead of all restaurants in the city), another good
example would be preferred language, my language will be detected
more accurately based on my area rather than my country, as there
are many countries with more than one popular language, not
mentioning that many ip registrations does not even reflect the
traffic originating country.


Information accuracy and control: Nowadays, locations are assigned
to IP addresses without user awareness or control, every time a
user performs ip-lookup query the response would be different based
on how the ISP has registered this IP subnet, IP-LOC suggests
making locations more accurate and controllable through OS and
network devices, exactly like IP addresses (user can change his/her
IP address, but router can also modify the header information - in
case its required).


Routing: Policy based routing, based on geo-location, like routing
predefined traffic through certain server or path, for different
purposes (security, manageability, serviceability like choosing
call agent language for VoIP calls, or routing traffic to specific
cashing or proxy server based on country .. etc)


Copyright law: It happens when certain media/web content is not
available to certain countries due to copyright law, the current
method of determining locations is not accurate, on the other
hand, If layer-7 application to be used then the user might be able
to manipulate the location field, in this case (if its required in
future) the ISP can tag traffic with country/city more accurately
as traffic passes through ISP boarder routers.


Flexibility and Compatibility: Currently, many applications do not
share same mechanisms to obtain location or location-related data,
like detecting language, for example, if a VoIP user called in to a
customer call center, the VoIP softswitch might not support http
requests in order to detect customer language and redirect the call 
to the proper agent, so although http and VoIP signaling protocols
work at the same application layer, they can not always share the
same mechanism, a lower layer mechanism is necessary to obtain the
location data.

Show full document text