Dynamic Host Configuration Protocol (DHCP) IPv4 and IPv6 Option for a Location Uniform Resource Identifier (URI)
draft-ietf-geopriv-dhcp-lbyr-uri-option-17

The information below is for an old version of the document
Document Type Active Internet-Draft (geopriv WG)
Last updated 2013-01-29 (latest revision 2013-01-28)
Replaces draft-polk-geopriv-dhcp-lbyr-uri-option
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd None
Shepherd write-up Show (last changed 2012-05-31)
IESG IESG state IESG Evaluation
Telechat date
Needs a YES. Has 3 DISCUSSes. Needs 8 more YES or NO OBJECTION positions to pass.
Responsible AD Robert Sparks
IESG note The document shepherd for this document is Alissa Cooper (acooper@cdt.org).
Send notices to geopriv-chairs@tools.ietf.org, draft-ietf-geopriv-dhcp-lbyr-uri-option@tools.ietf.org
Network WG                                                   James Polk
Internet-Draft                                            Cisco Systems
Intended status: Proposed Standard                         Jan 28, 2013
Expires: June 28, 2013

        Dynamic Host Configuration Protocol (DHCP) IPv4 and IPv6 
         Option for a Location Uniform Resource Identifier (URI)
              draft-ietf-geopriv-dhcp-lbyr-uri-option-17

Abstract

   This document creates a Dynamic Host Configuration Protocol (DHCP) 
   Option for transmitting a client's geolocation Uniform Resource 
   Identifier (URI), and another Option to explicitly indicate how long
   that location URI is to be considered valid. 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 June 28, 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 June 28, 2013                  [Page 1]
Internet-Draft     Geopriv DHCP Location URI Option            Jan 2013

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  Format of the DHCP LocationURI and Valid-For Options  . . . .  4
       2.1.  Overall Format of LocationURI Option in IPv4  . . . . .  4
       2.2.  Overall Format of LocationURI Option in IPv6  . . . . .  5
       2.3.  Overall Format of Valid-For Option in IPv4  . . . . . .  5
       2.4.  Overall Format of Valid-For Option in IPv6  . . . . . .  6
       2.5.  Rules for both LocationURI and Valid-For Options  . . .  6
   3.  DHCP Option Operation . . . . . . . . . . . . . . . . . . . .  8
       3.1 Architectural Assumptions . . . . . . . . . . . . . . . .  9
       3.2 Harmful URIs and URLs . . . . . . . . . . . . . . . . . . 10
       3.3 Valid Location URI Schemes or Types . . . . . . . . . . . 10
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . 11
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . 12
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . . 12
       7.1. Normative References . . . . . . . . . . . . . . . . . . 12
       7.2. Informative References . . . . . . . . . . . . . . . . . 13
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . 14

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

1.  Introduction

   This document creates a Dynamic Host Configuration Protocol (DHCP) 
   Option for transmitting a client's geolocation Uniform Resource 
   Identifier (URI), and another Option to explicitly indicate how long
   that location URI is to be considered valid. 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 a Location 
   Server [RFC5808] which has the geolocation of the client (e.g., 
   uploaded into a wiremap database when the client attached wall-jack,
   or by means of 802.11 geolocation mechanisms).  
Show full document text