idnits 2.17.00 (12 Aug 2021) /tmp/idnits9827/draft-guenther-geopriv-policy-caps-02.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.a on line 18. -- Found old boilerplate from RFC 3978, Section 5.5 on line 344. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 321. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 328. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 334. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement. ** 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. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: This document is an Internet-Draft and is subject to all provisions of Section 3 of RFC 3667. By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. 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 (April 25, 2005) is 6234 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 263, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-geopriv-common-policy' is defined on line 267, 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 Summary: 6 errors (**), 0 flaws (~~), 7 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: October 27, 2005 Siemens 5 April 25, 2005 7 An Extensible Markup Language (XML) Representation for Expressing 8 Geographic Location Information Policy Capabilities 9 draft-guenther-geopriv-policy-caps-02.txt 11 Status of this Memo 13 This document is an Internet-Draft and is subject to all provisions 14 of Section 3 of RFC 3667. By submitting this Internet-Draft, each 15 author represents that any applicable patent or other IPR claims of 16 which he or she is aware have been or will be disclosed, and any of 17 which he or she become aware will be disclosed, in accordance with 18 RFC 3668. 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 October 27, 2005. 38 Copyright Notice 40 Copyright (C) The Internet Society (2005). 42 Abstract 44 This specification defines a set of Extensible Markup Language (XML) 45 elements for expressing geographic location information policy 46 capabilities. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 52 3. Structure of Geopriv Policy Capabilities . . . . . . . . . . . 5 53 4. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 6 54 5. Example Document . . . . . . . . . . . . . . . . . . . . . . . 7 55 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 56 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 57 7.1 Namespace Registration . . . . . . . . . . . . . . . . . . 9 58 7.2 Geopriv Policy Capabilities Schema Registration . . . . . 9 59 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 60 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 61 9.1 Normative References . . . . . . . . . . . . . . . . . . . 11 62 9.2 Informative References . . . . . . . . . . . . . . . . . . 11 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 12 64 Intellectual Property and Copyright Statements . . . . . . . . 13 66 1. Introduction 68 Authorization policies are an important component of presence 69 [RFC2778]. They allow the presentity to grant access to specific 70 pieces of information to watchers. Authorization policies have been 71 designed to be extensible. For this reason [I-D.rosenberg-simple- 72 common-policy-caps] defines a generic Extensible Markup Language 73 (XML) based format for representing policy capabilities. That format 74 applies to many policy types, including location and presence. This 75 specification extends that one by defining policy capabilities 76 specific to geographic location information. Those policy 77 capabilities correspond to the conditions, actions and 78 transformations defined in [I-D.ietf-geopriv-policy]. 80 2. Terminology 82 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 83 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 84 document are to be interpreted as described in [RFC2119]. 86 3. Structure of Geopriv Policy Capabilities 88 The structure of common policy capability documents is defined in 89 [I-D.rosenberg-simple-common-policy-caps]. In that specification, 90 each policy capability document has three components - a list of 91 supported conditions, a list of supported actions, and a list of 92 supported transformations. This specification merely extends that 93 document with the conditions, actions and transformations defined in 94 [I-D.ietf-geopriv-policy]. It does so by defining the following 95 empty elements: 97 civic-loc-condition 98 geospatial-loc-condition 99 distribution-transformation 100 retention-tranformation 101 keep-rules-transformation 102 civic-loc-transformation 103 geospatial-loc-transformation 105 Each of these elements indicates whether the respective attribute in 106 [I-D.ietf-geopriv-policy] is supported. All of these elements are 107 defined within the namespace: 109 urn:ietf:params:xml:ns:geopriv-policy-capabilities 111 4. XML Schema 113 122 125 128 131 134 137 140 143 144 145 146 148 150 152 153 154 156 158 5. Example Document 160 The following document indicates that the identity and validity 161 conditions are supported, each of which is defined in [I-D.ietf- 162 geopriv-common-policy], while no support of sphere conditions is 163 indicated. Furthermore, the example indicates that the geolocation- 164 specific condition named civic-loc-condition is supported. With 165 respect to transformations, the example gives the indication that the 166 geolocation-specific transformations named keep-rules-transformation 167 is supported. This is also the case for geospatial-loc- 168 transformations, namely, for latitude and longitude values, but not 169 for altitude values: 171 172 177 178 179 180 181 183 184 186 187 188 189 190 191 192 194 196 6. Security Considerations 198 This specification does not introduce any new security considerations 199 beyond those discussed in [I-D.rosenberg-simple-common-policy-caps]. 201 7. IANA Considerations 203 This section registers a new XML namespace and a new XML schema with 204 IANA. 206 7.1 Namespace Registration 208 URI: urn:ietf:params:xml:ns:geopriv-policy-capabilities 209 Registrant Contact: IETF Geopriv Working Group, Christian Guenther 210 (christian.guenther@siemens.com), Hannes Tschofenig 211 (hannes.tschofenig@siemens.com). 212 XML: 214 BEGIN 215 216 218 219 220 222 Geopriv Policy Capabilities 223 224 225

Namespace for Geopriv Policy Capabilities

226

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

227

See RFCXXXX.

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