idnits 2.17.00 (12 Aug 2021) /tmp/idnits62138/draft-guenther-geopriv-policy-caps-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 339. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 316. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 323. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 329. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- 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 (June 21, 2006) is 5806 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: 'RFC3688' is defined on line 261, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-geopriv-common-policy' is defined on line 265, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 2778 == Outdated reference: draft-ietf-geopriv-common-policy has been published as RFC 4745 == Outdated reference: draft-ietf-geopriv-policy has been published as RFC 6772 == Outdated reference: A later version (-01) exists of draft-ietf-simple-common-policy-caps-00 == Outdated reference: A later version (-01) exists of draft-ietf-simple-pres-policy-caps-00 Summary: 4 errors (**), 0 flaws (~~), 9 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Geopriv C. Guenther 3 Internet-Draft H. Tschofenig 4 Expires: December 23, 2006 Siemens 5 June 21, 2006 7 An Extensible Markup Language (XML) Representation for Expressing 8 Geographic Location Information Policy Capabilities 9 draft-guenther-geopriv-policy-caps-04.txt 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on December 23, 2006. 36 Copyright Notice 38 Copyright (C) The Internet Society (2006). 40 Abstract 42 This specification defines a set of Extensible Markup Language (XML) 43 elements for expressing geographic location information policy 44 capabilities. 46 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 49 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 50 3. Structure of Geopriv Policy Capabilities . . . . . . . . . . . 5 51 4. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 6 52 5. Example Document . . . . . . . . . . . . . . . . . . . . . . . 7 53 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 54 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 55 7.1. Namespace Registration . . . . . . . . . . . . . . . . . . 9 56 7.2. Geopriv Policy Capabilities Schema Registration . . . . . 9 57 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 58 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 59 9.1. Normative References . . . . . . . . . . . . . . . . . . . 11 60 9.2. Informative References . . . . . . . . . . . . . . . . . . 11 61 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 62 Intellectual Property and Copyright Statements . . . . . . . . . . 13 64 1. Introduction 66 Authorization policies are an important component of presence 67 [RFC2778]. They allow the presentity to grant access to specific 68 pieces of information to watchers. Authorization policies have been 69 designed to be extensible. For this reason [I-D.ietf-simple-common- 70 policy-caps] defines a generic Extensible Markup Language (XML) based 71 format for representing policy capabilities. That format applies to 72 many policy types, including location and presence. This 73 specification extends that one by defining policy capabilities 74 specific to geographic location information. Those policy 75 capabilities correspond to the conditions, actions and 76 transformations defined in [I-D.ietf-geopriv-policy]. 78 2. Terminology 80 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 81 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 82 document are to be interpreted as described in [RFC2119]. 84 3. Structure of Geopriv Policy Capabilities 86 The structure of common policy capability documents is defined in 87 [I-D.ietf-simple-common-policy-caps]. In that specification, each 88 policy capability document has three components - a list of supported 89 conditions, a list of supported actions, and a list of supported 90 transformations. This specification merely extends that document 91 with the conditions, actions and transformations defined in 92 [I-D.ietf-geopriv-policy]. It does so by defining the following 93 empty elements: 95 civic-loc-condition 96 geospatial-loc-condition 97 distribution-transformation 98 retention-tranformation 99 keep-rules-transformation 100 civic-loc-transformation 101 geospatial-loc-transformation 103 Each of these elements indicates whether the respective attribute in 104 [I-D.ietf-geopriv-policy] is supported. All of these elements are 105 defined within the namespace: 107 urn:ietf:params:xml:ns:geopriv-policy-capabilities 109 4. XML Schema 111 120 123 126 129 132 135 138 141 142 143 144 146 148 150 151 152 154 156 5. Example Document 158 The following document indicates that the identity and validity 159 conditions are supported, each of which is defined in [I-D.ietf- 160 geopriv-common-policy], while no support of sphere conditions is 161 indicated. Furthermore, the example indicates that the geolocation- 162 specific condition named civic-loc-condition is supported. With 163 respect to transformations, the example gives the indication that the 164 geolocation-specific transformations named keep-rules-transformation 165 is supported. This is also the case for geospatial-loc- 166 transformations, namely, for latitude and longitude values, but not 167 for altitude values: 169 170 175 176 177 178 179 181 182 184 185 186 187 188 189 190 192 194 6. Security Considerations 196 This specification does not introduce any new security considerations 197 beyond those discussed in [I-D.ietf-simple-common-policy-caps]. 199 7. IANA Considerations 201 This section registers a new XML namespace and a new XML schema with 202 IANA. 204 7.1. Namespace Registration 206 URI: urn:ietf:params:xml:ns:geopriv-policy-capabilities 207 Registrant Contact: IETF Geopriv Working Group, Christian Guenther 208 (christian.guenther@siemens.com), Hannes Tschofenig 209 (hannes.tschofenig@siemens.com). 210 XML: 212 BEGIN 213 214 216 217 218 220 Geopriv Policy Capabilities 221 222 223

Namespace for Geopriv Policy Capabilities

224

urn:ietf:params:xml:ns:geopriv-policy-capabilities

225

See RFCXXXX.

226 227 228 END 230 7.2. Geopriv Policy Capabilities Schema Registration 232 URI: Please assign. 233 Registrant Contact: IETF Geopriv Working Group, Christian Guenther 234 (christian.guenther@siemens.com), Hannes Tschofenig 235 (hannes.tschofenig@siemens.com). 236 XML: The XML schema to be registered is contained in section 237 Section 4. Its first line is 239 245 8. Acknowledgments 247 The authors would like to thank Jonathan Rosenberg whose Presence 248 Policy Capabilities document [I-D.ietf-simple-pres-policy-caps] 249 served as template for this document. 251 9. References 253 9.1. Normative References 255 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 256 Requirement Levels", March 1997. 258 [RFC2778] Day, M., Rosenberg, J., and H. Sugano, "A Model for 259 Presence and Instant Messaging", February 2000. 261 [RFC3688] Mealling, M., "The IETF XML Registry", January 2004. 263 9.2. Informative References 265 [I-D.ietf-geopriv-common-policy] 266 Schulzrinne, H., "Common Policy: An XML Document Format 267 for Expressing Privacy Preferences", 268 draft-ietf-geopriv-common-policy-10 (work in progress), 269 May 2006. 271 [I-D.ietf-geopriv-policy] 272 Schulzrinne, H., "A Document Format for Expressing Privacy 273 Preferences for Location Information", 274 draft-ietf-geopriv-policy-08 (work in progress), 275 February 2006. 277 [I-D.ietf-simple-common-policy-caps] 278 Rosenberg, J., "An Extensible Markup Language (XML) 279 Representation for Expressing Policy Capabilities", 280 draft-ietf-simple-common-policy-caps-00 (work in 281 progress), July 2005. 283 [I-D.ietf-simple-pres-policy-caps] 284 Rosenberg, J., "An Extensible Markup Language (XML) 285 Representation for Expressing Presence Policy 286 Capabilities", draft-ietf-simple-pres-policy-caps-00 (work 287 in progress), July 2005. 289 Authors' Addresses 291 Christian Guenther 292 Siemens 293 Otto-Hahn-Ring 6 294 Munich, Bavaria 81739 295 Germany 297 Email: christian.guenther@siemens.com 299 Hannes Tschofenig 300 Siemens 301 Otto-Hahn-Ring 6 302 Munich, Bavaria 81739 303 Germany 305 Email: hannes.tschofenig@siemens.com 307 Intellectual Property Statement 309 The IETF takes no position regarding the validity or scope of any 310 Intellectual Property Rights or other rights that might be claimed to 311 pertain to the implementation or use of the technology described in 312 this document or the extent to which any license under such rights 313 might or might not be available; nor does it represent that it has 314 made any independent effort to identify any such rights. Information 315 on the procedures with respect to rights in RFC documents can be 316 found in BCP 78 and BCP 79. 318 Copies of IPR disclosures made to the IETF Secretariat and any 319 assurances of licenses to be made available, or the result of an 320 attempt made to obtain a general license or permission for the use of 321 such proprietary rights by implementers or users of this 322 specification can be obtained from the IETF on-line IPR repository at 323 http://www.ietf.org/ipr. 325 The IETF invites any interested party to bring to its attention any 326 copyrights, patents or patent applications, or other proprietary 327 rights that may cover technology that may be required to implement 328 this standard. Please address the information to the IETF at 329 ietf-ipr@ietf.org. 331 Disclaimer of Validity 333 This document and the information contained herein are provided on an 334 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 335 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 336 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 337 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 338 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 339 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 341 Copyright Statement 343 Copyright (C) The Internet Society (2006). This document is subject 344 to the rights, licenses and restrictions contained in BCP 78, and 345 except as set forth therein, the authors retain all their rights. 347 Acknowledgment 349 Funding for the RFC Editor function is currently provided by the 350 Internet Society.