| Internet-Draft | The geo Link-Format Attribute | October 2013 |
| Fossati | Expires 4 May 2014 | [Page] |
This memo proposes a new CoAP link format attribute, "geo", that can be used to associate positioning metadata to a CoAP resource.¶
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 4 April 2014.¶
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.¶
This memo proposes a new CoAP link-format attribute, "geo", that can be used to associate positioning metadata to a CoAP resource, and make this information available to other endpoints that, directly or indirectly, participate in to CoAP link-format discovery [RFC6690].¶
The ability for a consuming application to access positioning information about a sensing resource is crucial in a number of use cases, especially those in which one or more sensor networks provide input to an emergency handling service (e.g. fire, flood, etc.).¶
This spec reuses the geo URI syntax [RFC5870], which is capable to describe physical locations in two or three dimensions (also supporting underground and underwater localisation using negative numbers) in a compact, simple and human readable way.¶
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].¶
Location-aware applications and location-based services like seismic networks, gas pipeline monitoring deployments, fire or flood detection systems, etc., need to precisely locate the source of sensed stimulus in order to react in a sensible way.¶
{TODO collect other use cases}¶
This section defines a new Web Linking [RFC5988] link-param, "geo", to be used within the [RFC6690] framework, having the following syntax:¶
link-extension = "geo" "=" geo-path geo-path ; defined in Section 3.3. of RFC 5870¶
The geo attribute MUST NOT appear more than once in a link.¶
(NOTE about Link-Format queries: non exact matches cannot be easily/effectively queried.)¶
REQ: GET /.well-known/core RES: 2.05 Content </fire>;ct=40;if="sensor;geo="40,16.34"¶
REQ: GET /.well-known/core RES: 2.05 Content </water>;ct=40;if="sensor;geo="38.295326,20.642624,-20"¶
TODO¶
The "geo" link-format attributes share the same security issues as any other attribute involved in the discovery process described in [RFC6690].¶
Further to that, the privacy considerations regarding distribution, protection, usage, retention, and storage of the location information of the target resource found in [RFC6280] fully apply.¶