idnits 2.17.1 draft-murchison-tzdist-geolocate-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 14, 2016) is 2744 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 7807 (Obsoleted by RFC 9457) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group K. Murchison 3 Internet-Draft CMU 4 Intended status: Standards Track October 14, 2016 5 Expires: April 17, 2017 7 The Time Zone Data Distribution Service (TZDIST) Geolocate Extension 8 draft-murchison-tzdist-geolocate-00 10 Abstract 12 This document defines an extension to the Time Zone Data Distribution 13 Service (RFC 7808) to allow a client to determine the correct time 14 zone for a geographic point location using a 'geo' URI (RFC 5870). 16 Open Issues 18 o Does the 'geo' URI value have to be percent-encoded? 20 o Should we advertise the supported coordinate reference systems 21 (and if so, how?) or simply mandate crs=wgs84? 23 o Should we discuss territorial and/or international waters? 25 o What, if any, additional security and privacy concerns are 26 introduced by this extension? 28 Status of This Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at http://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on April 17, 2017. 45 Copyright Notice 47 Copyright (c) 2016 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 63 2. Conventions Used in This Document . . . . . . . . . . . . . . 3 64 3. "geolocate" Action . . . . . . . . . . . . . . . . . . . . . 3 65 3.1. Examples: geolocate 66 action . . . . . . . . . . . . . . . . . . . . . . . . . 4 67 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 68 5. Privacy Considerations . . . . . . . . . . . . . . . . . . . 6 69 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 70 6.1. Service Action Registration . . . . . . . . . . . . . . . 6 71 6.2. Registration of invalid-location Error URN . . . . . . . 6 72 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6 73 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 74 8.1. Normative References . . . . . . . . . . . . . . . . . . 6 75 8.2. Informative References . . . . . . . . . . . . . . . . . 7 76 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7 78 1. Introduction 80 Clients using a Time Zone Data Distribution Service (TZDIST), 81 particularly mobile clients, may not have prior knowledge of which 82 time zone is appropriate for a particular geographic region. This 83 specification defines a new TZDIST service action to allow a client 84 to query a server with a geographic point location and have that 85 server determine if the location lies within the boundaries of an 86 existing time zone and return the corresponding time zone 87 identifiers. 89 This specification does not define the source of the time zone 90 boundary data. It is assumed that a reliable and accurate source is 91 available. Two such sources are [TZSHAPE] and [TZBB]. 93 2. Conventions Used in This Document 95 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 96 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 97 "OPTIONAL" in this document are to be interpreted as described in 98 [RFC2119]. 100 3. "geolocate" Action 102 Name: gelocate 104 Request-URI Template: 105 {/service-prefix,data-prefix}/zones{?location} 107 Description: This action allows a client to query the time zone data 108 distribution service for the time zone identifier corresponding to 109 the given geographic point location, specified as a 'geo' URI 110 [RFC5870]. 112 If the 'geo' URI specifies an uncertainty value (";u=" parameter), 113 the server MUST return the time zone identifiers for all time 114 zones whose boundary passes through the radius of uncertainty. In 115 the absence of a client-supplied uncertainty value, the server MAY 116 use an implicit uncertainty to coincide with any uncertainty in 117 the time zone boundary data that it uses. 119 If the 'geo' URI specifies a coordinate reference system (";crs=" 120 parameter) that is unsupported by the server, the server SHOULD 121 return a JSON "problem details" object [RFC7807] in the response 122 body including a "type" member with an "invalid-location" error 123 URN as defined below. 125 Parameters: 127 location= REQUIRED, and MUST occur only once. 129 Response: The response has the same format as the "list" and "find" 130 actions (see [RFC7808] Section 6.2), with one result object for 131 each geolocated time zone. If for any reason the server can not 132 determine a time zone in which the point is located (e.g. 133 uninhabited location), it MUST return a "list" response containing 134 zero time zone objects. 136 Possible Error Codes 138 urn:ietf:params:tzdist:error:invalid-location The "location" URI 139 query parameter is missing, has an incorrect/unsupported value, 140 or appears more than once. 142 3.1. Examples: geolocate action 144 The examples below presume that the timezone context path has been 145 discovered (see [RFC7808] Section 4.2.1) to be "/tzdist". 147 In this example the client asks for the time zone corresponding to 148 Carnegie Mellon University. 150 >> Request << 152 GET /tzdist/zones?location=geo:40.44388,-79.94199 HTTP/1.1 153 Host: tz.example.com 155 >> Response << 157 HTTP/1.1 200 OK 158 Date: Fri, 30 Sep 2016 12:28:03 GMT 159 Content-Type: application/json; charset="utf-8" 160 Content-Length: xxxx 162 { 163 "synctoken": "890939292-1466089793", 164 "timezones": [ 165 { 166 "tzid": "America/New_York", 167 "etag": "6602582-1466089793", 168 "last-modified": "2016-06-16T15:09:53Z", 169 "publisher": "IANA Time Zone Database", 170 "version": "2016e", 171 "aliases": [ 172 "US/Eastern" 173 ] 174 } 175 ] 176 } 177 In this example the client asks for the timezone corresponding to the 178 Hoover Dam with an uncertainty of 25m. Note that the dam straddles 179 the Nevada/Arizona state line and therefore a time zone boundary. 181 >> Request << 183 GET /tzdist/zones?location=geo:36.01596,-114.73748;u=25 HTTP/1.1 184 Host: tz.example.com 186 >> Response << 188 HTTP/1.1 200 OK 189 Date: Fri, 30 Sep 2016 12:28:03 GMT 190 Content-Type: application/json; charset="utf-8" 191 Content-Length: xxxx 193 { 194 "synctoken": "890939292-1466089793", 195 "timezones": [ 196 { 197 "tzid": "America/Los_Angeles", 198 "etag": "52807330-1466089793", 199 "last-modified": "2016-06-16T15:09:53Z", 200 "publisher": "IANA Time Zone Database", 201 "version": "2016e", 202 "aliases": [ 203 "US/Pacific" 204 ] 205 }, 206 { 207 "tzid": "America/Phoenix", 208 "etag": "3297940-1466089793", 209 "last-modified": "2016-06-16T15:09:53Z", 210 "publisher": "IANA Time Zone Database", 211 "version": "2016e", 212 "aliases": [ 213 "US/Arizona" 214 ] 215 } 216 ] 217 } 219 4. Security Considerations 221 This specification does not introduce any additional security 222 concerns beyond those described in [RFC7808] 224 5. Privacy Considerations 226 This specification does not introduce any additional privacy concerns 227 beyond those described in [RFC7808]. 229 6. IANA Considerations 231 6.1. Service Action Registration 233 This document defines the following new TZDIST Service Action to be 234 added to the registry defined in Section 10.3.1 of [RFC7808]: 236 +-------------+--------------------+ 237 | Action Name | Reference | 238 +-------------+--------------------+ 239 | geolocate | RFCXXXX, Section 3 | 240 +-------------+--------------------+ 242 6.2. Registration of invalid-location Error URN 244 This section registers the "urn:ietf:params:tzdist:error:invalid- 245 location" URN in the "TZDIST Identifiers" registry defined in 246 Section 10.4 of [RFC7808]. 248 URN: urn:ietf:params:tzdist:error:invalid-location 250 Specification: RFCXXXX, Section 3 252 Repository: http://www.iana.org/assignments/tzdist-identifiers. 254 Contact: IESG 256 Index value: N/A. 258 7. Acknowledgments 260 The author would like to thank the following individuals for 261 contributing their ideas and support for writing this specification: 262 Cyrus Daboo. 264 8. References 266 8.1. Normative References 268 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 269 Requirement Levels", BCP 14, RFC 2119, 270 DOI 10.17487/RFC2119, March 1997, 271 . 273 [RFC5870] Mayrhofer, A. and C. Spanring, "A Uniform Resource 274 Identifier for Geographic Locations ('geo' URI)", 275 RFC 5870, DOI 10.17487/RFC5870, June 2010, 276 . 278 [RFC7807] Nottingham, M. and E. Wilde, "Problem Details for HTTP 279 APIs", RFC 7807, DOI 10.17487/RFC7807, March 2016, 280 . 282 [RFC7808] Douglass, M. and C. Daboo, "Time Zone Data Distribution 283 Service", RFC 7808, DOI 10.17487/RFC7808, March 2016, 284 . 286 8.2. Informative References 288 [TZBB] Siroky, E., "Timezone Boundary Builder", 289 . 291 [TZSHAPE] Muller, E., "A set of shapefiles for the TZ timezones", 292 . 294 Author's Address 296 Kenneth Murchison 297 Carnegie Mellon University 298 5000 Forbes Avenue 299 Pittsburgh, PA 15213 300 USA 302 Email: murch@andrew.cmu.edu