idnits 2.17.1 draft-singh-geopriv-pidf-lo-dynamic-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.ii or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) 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 seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (August 17, 2009) is 5364 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) == Unused Reference: 'GeoShape' is defined on line 358, but no explicit reference was found in the text Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group H. Schulzrinne 3 Internet-Draft V. Singh 4 Intended status: Standards Track Columbia University 5 Expires: February 18, 2010 H. Tschofenig 6 Nokia Siemens Networks 7 M. Thomson 8 Andrew Corporation 9 August 17, 2009 11 Dynamic Extensions to the Presence Information Data Format Location 12 Object (PIDF-LO) 13 draft-singh-geopriv-pidf-lo-dynamic-07 15 Status of this Memo 17 This Internet-Draft is submitted to IETF in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on February 18, 2010. 38 Copyright Notice 40 Copyright (c) 2009 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents in effect on the date of 45 publication of this document (http://trustee.ietf.org/license-info). 46 Please review these documents carefully, as they describe your rights 47 and restrictions with respect to this document. 49 Abstract 51 The Geopriv Location Object introduced by the Presence Information 52 Data Format - Location Object (PIDF-LO), RFC 4119, defines a basic 53 XML format for carrying geographical information of a presentity. 54 This document defines PIDF-LO extensions that are intended to convey 55 information about moving objects. Elements are defined that enable 56 expression of spatial orientation, speed, heading, and acceleration 57 of the presentity. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 3. Dynamic Elements . . . . . . . . . . . . . . . . . . . . . . . 3 64 3.1. Angular Measures and Coordinate Reference Systems . . . . 5 65 4. Dynamic Feature XML Schema . . . . . . . . . . . . . . . . . . 7 66 5. Security Considerations . . . . . . . . . . . . . . . . . . . 8 67 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 68 6.1. Dynamic Feature Extensions Namespace Registration . . . . 8 69 6.2. Dynamic Feature Extensions Schema Registration . . . . . . 8 70 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 71 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 72 8.1. Normative References . . . . . . . . . . . . . . . . . . . 9 73 8.2. Informative References . . . . . . . . . . . . . . . . . . 9 74 Appendix A. Earth Centered, Earth Fixed Direction Vectors . . . . 10 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 77 1. Introduction 79 The Presence Information Data Format - Location Object (PIDF-LO) (see 80 RFC 4119 [RFC4119]) provides geographical location of a presentity. 81 This corresponds to a physical location at a given instance of time. 82 With the extensions defined in [RFC5491] more guidelines to 83 implementers are being provided with respect to the expression 84 location information in PIDF-LO. 86 The addition of rate of change information to the PIDF-LO enables a 87 range of use cases. These use cases either directly use dynamic 88 information, or use that information for smoother tracking of a 89 position over time. For example, an application that continuously 90 tracks a presentity could use velocity information to extrapolate 91 positions in between times location information is measured. A 92 shipping company could directly use speed to monitor delivery truck 93 speed to ensure speed limits are observed. 95 2. Terminology 97 In this document, the key words "MUST", "MUST NOT", "REQUIRED", 98 "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", 99 and "OPTIONAL" are to be interpreted as described in RFC 2119 100 [RFC2119]. 102 3. Dynamic Elements 104 This document defines a new element, , for the conveyance of 105 dynamic information. 107 Dynamic information MAY be included without any other location 108 information being present. When dynamic information is associated 109 with information about the instantaneous position of the presentity, 110 the element MUST be included in the same 111 element as the corresponding geodetic (or civic) location 112 information. 114 Dynamic information can be safely ignored by a recipient that does 115 not support this specification. 117 The element contains the following components: 118 orientation: 120 The element describes the spatial orientation of the 121 presentity; the direction that the object is pointing. For a 122 device, this orientation might depend on the type of device. See 123 Section 3.1 for details. 125 speed: 127 Speed is the time rate of change in position of a presentity 128 without regard for direction; the scalar component of velocity. 129 The value for the element is a measure that is defined in 130 meters per second. 132 heading: 134 Heading is directional component of velocity. See Section 3.1 for 135 details. 137 acceleration: 139 Acceleration is the time rate of change of velocity. This element 140 contains the scalar component of velocity, measured in meters per 141 second per second. 143 Each element can be omitted if no information is available. In the 144 following example the presentity is approximately oriented to the 145 North at a slightly elevated angle. The presentity is travelling 24 146 meters per second to the West: 148 149 156 157 158 159 160 -3 12 161 24 162 278 163 164 165 166 gps 167 168 2009-06-22T20:57:29Z 169 mac:1234567890ab 170 172 174 Another example shows a PIDF-LO document of the presentity 175 alice@example.com on a bike traveling 12 meters per second and with 176 an acceleration of 2 meters per second. Her position is indicated as 177 a circle. The values for speed and acceleration might be used by a 178 receiver to adjust the uncertainty over time. 180 181 189 190 191 192 193 42.5463 -73.2512 194 195 100 196 197 198 199 12 200 2 201 202 203 204 gps 205 206 2009-06-22T20:57:29Z 207 mac:1234567890ab 208 209 211 3.1. Angular Measures and Coordinate Reference Systems 213 [RFC5491] constrains the coordinate reference system (CRS) used in 214 PIDF-LO to World Geodetic System 1984 (WGS 84) using either the two- 215 dimensional (latitude, longitude) CRS identified by 216 "urn:ogc:def:crs:EPSG::4326" or the two-dimensional (latitude, 217 longitude, altitude) CRS identified by "urn:ogc:def:crs:EPSG::4979". 218 Dynamic locations similarly assume that either of these coordinate 219 reference systems are used. 221 The and establish a direction. Both measures 222 contain one or two angular values that are expressed relative to the 223 current position of the presentity (see Appendix A). Angular 224 measures are expressed in degrees and values MAY be negative. If two 225 measures are present, the values MUST be separated by whitespace. 227 The first measure specifies the horizontal direction from the current 228 position of the presentity to a point that it either pointing towards 229 or travelling towards. Horizontal angles are measured from Northing 230 to Easting. Horizontal angles start from zero when pointing to or 231 travelling towards the North and increase towards the East. 233 The second measure, if present, specifies the vertical component of 234 this angle. This angle is the elevation from the local horizontal 235 plane. If the second angle value is omitted, the vertical component 236 is unknown and the speed measure MAY be assumed to only contain the 237 horizontal component of speed. 239 4. Dynamic Feature XML Schema 241 242 249 251 252 253 254 255 257 259 261 263 265 266 267 268 269 271 272 273 274 275 276 278 279 280 282 284 5. Security Considerations 286 This document defines additional location elements carried by 287 PIDF-LO. No additional security considerations beyond those 288 described in RFC 4119 [RFC4119] are applicable to this document. 290 6. IANA Considerations 292 This section registers a new XML namespace (as described in 293 [RFC3688]) and a new XML schema. 295 6.1. Dynamic Feature Extensions Namespace Registration 297 URI: urn:ietf:params:xml:ns:pidf:dynamic" 299 Registrant Contact: IETF Geopriv Working Group, Hannes Tschofenig 300 (hannes.tschofenig@gmx.net). 302 XML: 304 BEGIN 305 306 308 309 310 Dynamic Feature Extensions Namespace 311 312 313

Namespace for Dynamic Feature Extensions to PIDF-LO

314

urn:ietf:params:xml:ns:pidf:dynamic

315

See RFCXXXX 316 [NOTE TO IANA/RFC-EDITOR: 317 Please replace XXXX with the RFC number of this 318 specification.].

319 320 321 END 323 6.2. Dynamic Feature Extensions Schema Registration 325 URI: urn:ietf:params:xml:schema:pidf:dynamic 326 Registrant Contact: IETF Geopriv Working Group, Hannes Tschofenig 327 (hannes.tschofenig@gmx.net) 329 XML: The XML schema to be registered is contained in Section 4. Its 330 first line is 332 334 and its last line is 336 338 7. Acknowledgements 340 We would like to thank Klaus Darilion, Cullen Jennings, Rohan Mahy, 341 Carl Reed, and Brian Rosen for their comments. 343 8. References 345 8.1. Normative References 347 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 348 Requirement Levels", BCP 14, RFC 2119, March 1997. 350 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 351 January 2004. 353 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 354 Format", RFC 4119, December 2005. 356 8.2. Informative References 358 [GeoShape] 359 Thomson, M. and C. Reed, "GML 3.1.1 PIDF-LO Shape 360 Application Schema for use by the Internet Engineering 361 Task Force (IETF)", Candidate OpenGIS Implementation 362 Specification 06-142, Version: 0.0.9, December 2006. 364 [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV 365 Presence Information Data Format Location Object (PIDF-LO) 366 Usage Clarification, Considerations, and Recommendations", 367 RFC 5491, March 2009. 369 Appendix A. Earth Centered, Earth Fixed Direction Vectors 371 The absolute orientation or heading of a presentity depends on its 372 latitude and longitude. The following vectors can be used to 373 determine the absolute direction in the WGS 84 Earth Centered, Earth 374 Fixed (X, Y, Z) coordinate space. 376 The direction of North as a unit vector in ECEF coordinates is: 378 North = [ -1 * sin(latitude) * cos(longitude), 379 -1 * sin(latitude) * sin(longitude), 380 cos(latitude) ] 382 The direction of "up" (the upward normal of the horizontal plane) as 383 a unit vector in ECEF coordinates is: 385 Up = [ cos(latitude) * cos(longitude), 386 cos(latitude) * sin(longitude), 387 sin(latitude) ] 389 Authors' Addresses 391 Henning Schulzrinne 392 Columbia University 393 Department of Computer Science 394 450 Computer Science Building, New York, NY 10027 395 US 397 Phone: +1 212 939 7004 398 Email: hgs@cs.columbia.edu 399 URI: http://www.cs.columbia.edu/ 401 Vishal Singh 402 Columbia University 403 Department of Computer Science 404 450 Computer Science Building, New York, NY 10027 405 US 407 Email: vs2140@cs.columbia.edu 408 URI: http://www.cs.columbia.edu/~vs2140 409 Hannes Tschofenig 410 Nokia Siemens Networks 411 Linnoitustie 6 412 Espoo 02600 413 Finland 415 Phone: +358 (50) 4871445 416 Email: Hannes.Tschofenig@gmx.net 417 URI: http://www.tschofenig.priv.at/ 419 Martin Thomson 420 Andrew Corporation 421 Wollongong 422 NSW Australia 424 Email: martin.thomson@andrew.com