idnits 2.17.00 (12 Aug 2021) /tmp/idnits10444/draft-guenther-geopriv-policy-caps-01.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 352. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 329. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 336. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 342. ** 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 (October 25, 2004) is 6416 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 270, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-simple-presence-rules' is defined on line 285, 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: draft-ietf-simple-presence-rules has been published as RFC 5025 == Outdated reference: A later version (-02) exists of draft-rosenberg-simple-common-policy-caps-01 == Outdated reference: A later version (-02) exists of draft-rosenberg-simple-pres-policy-caps-01 Summary: 6 errors (**), 0 flaws (~~), 10 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: April 25, 2005 Siemens 5 October 25, 2004 7 An Extensible Markup Language (XML) Representation for Expressing 8 Geographic Location Information Policy Capabilities 9 draft-guenther-geopriv-policy-caps-01.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 23 Internet-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 April 25, 2005. 38 Copyright Notice 40 Copyright (C) The Internet Society (2004). 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 Supported Geopriv Permissions Schema Registration . . . . 9 59 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11 60 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 61 9.1 Normative References . . . . . . . . . . . . . . . . . . . . 12 62 9.2 Informative References . . . . . . . . . . . . . . . . . . . 12 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 13 64 Intellectual Property and Copyright Statements . . . . . . . . 14 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 haven been 71 designed to be extensible. For this reason 72 [I-D.rosenberg-simple-common-policy-caps] defines a generic 73 Extensible Markup Language (XML) based format for representing policy 74 capabilities. That format applies to many policy types, including 75 location and presence. This specification extends that one by 76 defining policy capabilities specific to geographic location 77 information. Those policy capabilities correspond to the conditions, 78 actions and 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 Furthermore, the terminology defined in [I-D.ietf-geopriv-policy] is 87 used. 89 3. Structure of Geopriv Policy Capabilities 91 The structure of common policy capability documents is defined in 92 [I-D.rosenberg-simple-common-policy-caps]. In that specification, 93 each policy capability document has three components - a list of 94 supported conditions, a list of supported actions, and a list of 95 supported transformations. This specification merely extends that 96 document with the conditions, actions and transformations defined in 97 [I-D.ietf-geopriv-policy]. It does so by defining the following 98 empty elements: 100 o civil-loc-condition 101 o geospatial-loc-condition 102 o civil-loc-transformation 103 o set-retention 104 o set-distribution 105 o keep-rules 106 o longitude-resolution 107 o latitude-resolution 108 o altitude-resolution 109 o provide-timezone 111 Each of these elements indicates whether the respective attribute in 112 [I-D.ietf-geopriv-policy] is supported. All of these elements are 113 defined within the namespace: 115 urn:ietf:params:xml:ns:supported-geopriv-permissions 117 4. XML Schema 119 120 132 135 137 140 142 144 146 148 150 152 154 157 159 5. Example Document 161 The following document indicates that the identity, validity, and 162 sphere conditions are supported, each of which is defined in 163 [I-D.ietf-geopriv-common-policy]. It also indicates that the 164 geolocation-specific condition named geospatial-loc-condition is 165 supported. Support of the geolocation-specific transformations named 166 civil-loc-transformation, longitude-resolution and 167 latitude-resolution is indicated by the three child elements of the 168 element: 170 171 181 182 183 184 185 186 188 189 191 192 193 194 195 197 199 6. Security Considerations 201 This specification does not introduce any new security considerations 202 beyond those discussed in [I-D.rosenberg-simple-common-policy-caps]. 204 7. IANA Considerations 206 This section registers a new XML namespace and a new XML schema with 207 IANA. 209 7.1 Namespace Registration 211 URI: urn:ietf:params:xml:ns:supported-geopriv-permissions 212 Registrant Contact: IETF Geopriv Working Group, Christian Guenther 213 (christian.guenther@siemens.com), Hannes Tschofenig 214 (hannes.tschofenig@siemens.com). 215 XML: 217 BEGIN 218 219 221 222 223 225 Supported Geopriv Permissions 226 227 228

Namespace for Supported Geopriv Permissions

229

urn:ietf:params:xml:ns:supported-geopriv-permissions

230

See RFCXXXX 231 [NOTE TO IANA/RFC-EDITOR: 232 Please replace XXXX with the RFC number of this 233 specification.] 234 .

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