Enhancing Location Based IP Services
draft-add-location-to-ipv6-header-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Ammar J. Salih | ||
| Last updated | 2013-11-18 (Latest revision 2013-05-17) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes IP-LOC, a proposed extension to IPv6 header which suggests adding optional geo-location field, in order to enhance existing geo-location based IP service as well as adding new ones. The current method of determining geo-location of IP traffic is through RIR (Regional Internet Registry) database, this information 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 could 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 might also be required in the future when mobile routers move from one geo-location to another, which has a different policy.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)