idnits 2.17.1 draft-singh-geopriv-pidf-lo-dynamic-05.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 (March 9, 2009) is 5520 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Unused Reference: 'GML' is defined on line 309, but no explicit reference was found in the text == Unused Reference: 'RFC4481' is defined on line 323, but no explicit reference was found in the text Summary: 1 error (**), 0 flaws (~~), 4 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 Columbia University 4 Intended status: Experimental H. Tschofenig 5 Expires: September 10, 2009 Nokia Siemens Networks 6 M. Thomson 7 Andrew Corporation 8 V. Singh 9 March 9, 2009 11 Dynamic Feature Extensions to the Presence Information Data Format 12 Location Object (PIDF-LO) 13 draft-singh-geopriv-pidf-lo-dynamic-05.txt 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 September 10, 2009. 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 The PIDF-LO specification made a subset of the functionality offered 55 by the Geography Markup Language (GML) standard 3.0 mandatory to 56 implement. This document defines child elements to the element specified in RFC 4119 to carry temporal feature 58 elements useful for tracking moving objects. Elements are defined 59 that enable expression of speed, heading, acceleration and facing of 60 the presentity. 62 Table of Contents 64 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 65 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 66 3. Dynamic Elements . . . . . . . . . . . . . . . . . . . . . . . 3 67 4. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 4 68 5. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 69 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 70 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 71 7.1. Dynamic Feature Extensions Namespace Registration . . . . . 7 72 7.2. Dynamic Feature Extensions Schema Registration . . . . . . 7 73 7.3. Units of Measure Registration . . . . . . . . . . . . . . . 8 74 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8 75 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 76 9.1. Normative References . . . . . . . . . . . . . . . . . . . 8 77 9.2. Informative References . . . . . . . . . . . . . . . . . . 8 78 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 80 1. Introduction 82 The Presence Information Data Format - Location Object (PIDF-LO) (see 83 RFC 4119 [RFC4119]) provides geographical location of a presentity. 84 This corresponds to a physical location at a given instance of time. 85 The PIDF-LO specification made a subset of the functionality offered 86 by the Geography Markup Language (GML) standard 3.0 mandatory to 87 implement. With the extensions defined in 88 [I-D.ietf-geopriv-pdif-lo-profile] more guidelines to implementers 89 are being provided with respect to a number of location shapes that 90 have to be supported for usage within PIDF-LO. 92 The addition of rate of change information to the PIDF-LO enables a 93 range of use cases. These use cases either directly use dynamic 94 information, or use that information for smoother tracking of a 95 position over time. For example, an application that continuously 96 tracks a presentity could use velocity information to extrapolate 97 positions in between times location information is measured. A 98 shipping company could directly use speed to monitor trucks speed to 99 ensure speed limits are observed. 101 2. Terminology 103 In this document, the key words "MUST", "MUST NOT", "REQUIRED", 104 "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", 105 and "OPTIONAL" are to be interpreted as described in RFC 2119 106 [RFC2119]. 108 3. Dynamic Elements 110 This document defines a new element, , for the conveyance of 111 dynamic information. Dynamic information MAY be included without any 112 other location information being present. When dynamic information 113 is associated with information about the instantaneous position of 114 the presentity, the element MUST be included in the same 115 element as the corresponding geodetic (or civic) 116 location information. Dynamic information can be ignored if a 117 recipient does not support this specification. The element 118 MUST include an "srsName" attribute that it set to 119 "urn:ogc:def:crs:EPSG::4979". This document uses the application 120 schema profile defined in [GeoShape] (reference the OGC shapes 121 document) with the addition of "direction.xsd" (identified by the URN 122 "urn:opengis:specification:gml:schema-xsd:direction:3.1.1"). 124 The element contains the following components: 126 speed: 128 Speed is the time rate of change in position of a presentity 129 without regard for direction. The value for the element 130 MUST be defined in meters per second and the 'uom' attribute MUST 131 be set to "urn:ietf:params:ns:geopriv:dynamic:uom#mps". 133 acceleration: 135 This element specifies the rate usually rapid at which something 136 happens. The element also contains a 'uom' 137 attribute that MUST be set to 138 "urn:ietf:params:ns:geopriv:dynamic:uom#mps2". 140 heading: 142 Heading is defined as the horizontal direction of one terrestrial 143 point from another, expressed as the angular distance from a 144 reference direction. It is usually measured from 000 degrees at 145 the reference direction clockwise through 360 degrees. 146 orientation: 148 The element describes the orientation of the 149 presentity; the direction that the object is pointing. 151 The and elements are of the type gml: 152 DirectionPropertyType, which allows many variations. For use in this 153 document , the element MUST be used with the 154 and child elements. The 155 element indicates an angle in degrees from 156 Northing to Easting; indicates an angle above the 157 horizontal plane. Inclusion of a vertical angle is mandated by 158 schema; setting the 'uom' attribute to "urn:ogc:def:uom:EPSG::9102" 159 (unity) with a value of "0" indicates that the vertical angle is not 160 known. 162 The and elements MUST 163 include a "uom" attribute set to "urn:ogc:def:uom:EPSG::9102". 165 4. XML Schema 166 167 175 177 180 181 182 183 184 186 188 190 192 193 194 195 197 199 5. Example 200 201 206 207 208 210 90 211 212 214 5 215 216 217 218 220 3.2 221 222 223 224 226 180 227 228 230 0 231 232 233 234 236 0 237 238 240 Figure 1: Example of a dynamic extension 242 6. Security Considerations 244 This document defines additional location elements carried by PIDF-LO 245 (see [RFC4119]). The security considerations of RFC 4119 [RFC4119] 246 are applicable to this document. 248 7. IANA Considerations 250 This section registers a new XML namespace (as described in 251 [RFC3688]) and a new XML schema. 253 7.1. Dynamic Feature Extensions Namespace Registration 255 URI: urn:ietf:params:xml:ns:pidf:geopriv10:dynamic10" 256 Registrant Contact: IETF Geopriv Working Group, Hannes Tschofenig 257 (hannes.tschofenig@nsn.com). 258 XML: 260 BEGIN 261 262 264 265 266 268 Dynamic Feature Extensions Namespace 269 270 271

Namespace for Dynamic Feature Extensions to PIDF-LO

272

urn:ietf:params:xml:ns:pidf:geopriv10:dynamic10

273

See RFCXXXX 274 [NOTE TO IANA/RFC-EDITOR: 275 Please replace XXXX with the RFC number of this 276 specification.].

277 278 279 END 281 7.2. Dynamic Feature Extensions Schema Registration 283 URI: urn:ietf:params:xml:ns:pidf:geopriv10:dynamic10 284 Registrant Contact: IETF Geopriv Working Group, Hannes Tschofenig 285 (hannes.tschofenig@nsn.com). 286 XML: The XML schema to be registered is contained in Section 4. Its 287 first line is 289 291 and its last line is 293 295 7.3. Units of Measure Registration 297 Placeholder for - urn:ietf:params:ns:geopriv:dynamic:uom#mps - 298 urn:ietf:params:ns:geopriv:dynamic:uom#mps2 300 8. Acknowledgements 302 We would like to thank Klaus Darilion, Cullen Jennings, Rohan Mahy, 303 Carl Reed, and Brian Rosen for their comments. 305 9. References 307 9.1. Normative References 309 [GML] "Geographic information - Geography Markup Language (GML), 310 OpenGIS 03-105r1, available at: 311 http://portal.opengeospatial.org/files/?artifact_id=4700", 312 April 2004. 314 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 315 Requirement Levels", RFC 2119, BCP 14, March 1997. 317 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 318 January 2004. 320 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 321 Format", RFC 4119, December 2005. 323 [RFC4481] Schulzrinne, H., "Timed Presence Extensions to the 324 Presence Information Data Format (PIDF) to Indicate Status 325 Information for Past and Future Time Intervals", RFC 4481, 326 July 2006. 328 9.2. Informative References 330 [GeoShape] 331 Thomson, M. and C. Reed, "GML 3.1.1 PIDF-LO Shape 332 Application Schema for use by the Internet Engineering 333 Task Force (IETF)", Candidate OpenGIS Implementation 334 Specification 06-142, Version: 0.0.9, December 2006. 336 [I-D.ietf-geopriv-pdif-lo-profile] 337 Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV 338 PIDF-LO Usage Clarification, Considerations and 339 Recommendations", draft-ietf-geopriv-pdif-lo-profile-14 340 (work in progress), November 2008. 342 Authors' Addresses 344 Henning Schulzrinne 345 Columbia University 346 Department of Computer Science 347 450 Computer Science Building, New York, NY 10027 348 US 350 Phone: +1 212 939 7004 351 Email: hgs@cs.columbia.edu 352 URI: http://www.cs.columbia.edu 354 Hannes Tschofenig 355 Nokia Siemens Networks 356 Linnoitustie 6 357 Espoo 02600 358 Finland 360 Phone: +358 (50) 4871445 361 Email: Hannes.Tschofenig@gmx.net 362 URI: http://www.tschofenig.priv.at 364 Martin Thomson 365 Andrew Corporation 366 Wollongong 367 NSW Australia 369 Email: martin.thomson@andrew.com 371 Singh Vishal 373 Email: singh.vishal@gmail.com