Network WG James Polk
Internet-Draft Cisco Systems
Intended status: Proposed Standard Feb 25, 2013
Expires: Aug 25, 2013
Dynamic Host Configuration Protocol (DHCP) IPv4 and IPv6
Option for a Location Uniform Resource Identifier (URI)
draft-ietf-geopriv-dhcp-lbyr-uri-option-19
Abstract
This document creates a Dynamic Host Configuration Protocol (DHCP)
Option for transmitting a client's geolocation Uniform Resource
Identifier (URI). This Location URI can then be dereferenced in a
separate transaction by the client or sent to another entity and
dereferenced to learn physically where the client is located, but
only while valid.
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 August 25, 2013.
Copyright Notice
Copyright (c) 2013 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. Code Components extracted from this
document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License.
Polk Expires August 25, 2013 [Page 1]
Internet-Draft Geopriv DHCP Location URI Option Feb 2013
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. DHCP LocationURI Option Format and Rules .. . . . . . . . . . 4
2.1. Overall Format of LocationURI Option in IPv4 . . . . . 4
2.2. Overall Format of LocationURI Option in IPv6 . . . . . 5
2.3. Rules for both LocationURI and Valid-For Options . . . 6
3. DHCP Option Operation . . . . . . . . . . . . . . . . . . . . 7
4. Architectural Assumptions . . . . . . . . . . . . . . . . . . 8
4.1 Harmful URIs and URLs . . . . . . . . . . . . . . . . . . 8
4.2 Valid Location URI Schemes or Types . . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 10
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
8.1. Normative References . . . . . . . . . . . . . . . . . . 12
8.2. Informative References . . . . . . . . . . . . . . . . . 13
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction
This document creates a Dynamic Host Configuration Protocol (DHCP)
Option for transmitting a client's geolocation Uniform Resource
Identifier (URI) [RFC3986]. In this scenario, the DHCP client is a
Geopriv Target (i.e., the entity whose geolocation is associated
with the location URI). The DHCP implementation of the client can
then make this location information available to other applications
for their usage. This location URI points to a Location Server
[RFC5808] which has the geolocation of the client (e.g., previously
uploaded into a wiremap database then the client attaches to a known
wall-jack, or by means of 802.11 geolocation mechanisms).
Applications within the Target can then choose to dereference this
location URI and/or transmit the URI to another entity as a means of
conveying where the Target is located. Both Conveying and
Dereferencing a location URI is described in [RFC6442]. Session
Initiation Protocol (SIP) [RFC3261] is not the only protocol that
can dereference a location URI; there is also HTTP-Enabled Location
Delivery (HELD) [RFC6753] and HTTP [RFC2616].
A Location Server (LS) stores the Target's location as a presence
document, called a Presence Information Data Format - Location
datatracker.ietf.org