A Location Dereference Protocol Using HTTP-Enabled Location Delivery (HELD)
RFC 6753
| Document | Type | RFC - Proposed Standard (October 2012; No errata) | |
|---|---|---|---|
| Authors | James Winterbottom , Hannes Tschofenig , Henning Schulzrinne , Martin Thomson | ||
| Last updated | 2015-10-14 | ||
| Replaces | draft-winterbottom-geopriv-deref-protocol | ||
| Stream | Internent Engineering Task Force (IETF) | ||
| Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 6753 (Proposed Standard) | |
| Action Holders |
(None)
|
||
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Robert Sparks | ||
| IESG note | Richard Barnes (rbarnes@bbn.com) is the document shepherd. | ||
| Send notices to | (None) | ||
Internet Engineering Task Force (IETF) J. Winterbottom
Request for Comments: 6753 Commscope
Category: Standards Track H. Tschofenig
ISSN: 2070-1721 Nokia Siemens Networks
H. Schulzrinne
Columbia University
M. Thomson
Microsoft
October 2012
A Location Dereference Protocol Using
HTTP-Enabled Location Delivery (HELD)
Abstract
This document describes how to use the Hypertext Transfer Protocol
(HTTP) over Transport Layer Security (TLS) as a dereference protocol
to resolve a reference to a Presence Information Data Format Location
Object (PIDF-LO). This document assumes that a Location Recipient
possesses a URI that can be used in conjunction with the HTTP-Enabled
Location Delivery (HELD) protocol to request the location of the
Target.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6753.
Winterbottom, et al. Standards Track [Page 1]
RFC 6753 HELD Dereferencing October 2012
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. 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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. HELD Dereference Protocol . . . . . . . . . . . . . . . . . . 4
3.1. HELD Usage Profile . . . . . . . . . . . . . . . . . . . . 4
3.2. HTTP GET Behavior . . . . . . . . . . . . . . . . . . . . 5
4. Authorization Models . . . . . . . . . . . . . . . . . . . . . 6
4.1. Authorization by Possession . . . . . . . . . . . . . . . 7
4.2. Authorization via Access Control . . . . . . . . . . . . . 8
4.3. Access Control with HELD Dereference . . . . . . . . . . . 9
5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
6. Security Considerations . . . . . . . . . . . . . . . . . . . 13
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
8.1. Normative References . . . . . . . . . . . . . . . . . . . 15
8.2. Informative References . . . . . . . . . . . . . . . . . . 15
Appendix A. GEOPRIV Using Protocol Compliance . . . . . . . . . . 18
Appendix B. Compliance to Location Reference Requirements . . . . 21
B.1. Requirements for a Location Configuration Protocol . . . . 21
B.2. Requirements for a Location Dereference Protocol . . . . . 23
Winterbottom, et al. Standards Track [Page 2]
RFC 6753 HELD Dereferencing October 2012
1. Introduction
A location URI [RFC5808] identifies a resource that contains the
location of an entity. This document specifies how a holder of an
"http:" or "https:" location URI uses that URI to retrieve location
information using a subset of HELD functionality or an HTTP GET
request.
A location URI can be acquired using a location configuration
protocol, such as HTTP-Enabled Location Delivery (HELD) [RFC5985] or
the Dynamic Host Configuration Protocol (DHCP) location URI option
[DHCP-URI-OPT].
A Location Recipient that dereferences a location URI acquires
location information in the form of a Presence Information Data
Format - Location Object (PIDF-LO) document [RFC4119]. HELD
parameters allow for specifying the type of location information,
Show full document text