idnits 2.17.00 (12 Aug 2021) /tmp/idnits13373/draft-guenther-geopriv-policy-caps-00.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 347. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 324. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 331. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 337. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 353), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 40. ** 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 (July 11, 2004) is 6522 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 266, 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 (-02) exists of draft-rosenberg-simple-common-policy-caps-00 == Outdated reference: A later version (-02) exists of draft-rosenberg-simple-pres-policy-caps-00 Summary: 7 errors (**), 0 flaws (~~), 8 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: January 9, 2005 Siemens 5 July 11, 2004 7 An Extensible Markup Language (XML) Representation for Expressing 8 Geographic Location Information Policy Capabilities 9 draft-guenther-geopriv-policy-caps-00.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 http:// 31 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 January 9, 2005. 38 Copyright Notice 40 Copyright (C) The Internet Society (2004). All Rights Reserved. 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 . . . . . . . . . . . . . . . . . . . . . . . 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 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 civil-loc-condition 101 geospatial-loc-condition 102 civil-loc-transformation 103 set-retention 104 set-distribution 105 keep-rules 106 longitude-resolution 107 latitude-resolution 108 altitude-resolution 109 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 232 233 END 235 7.2 Supported Geopriv Permissions Schema Registration 237 URI: Please assign. 238 Registrant Contact: IETF Geopriv Working Group, Christian Guenther 239 (christian.guenther@siemens.com), Hannes Tschofenig 240 (hannes.tschofenig@siemens.com). 241 XML: The XML schema to be registered is contained in section Section 242 4. Its first line is 244 246 and its last line is 248 250 8. Acknowledgments 252 The authors would like to thank Jonathan Rosenberg whose Presence 253 Policy Capabilities document [I-D.rosenberg-simple-pres-policy-caps] 254 served as template for this document. 256 9. References 258 9.1 Normative References 260 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 261 Requirement Levels", March 1997. 263 [RFC2778] Day, M., Rosenberg, J. and H. Sugano, "A Model for 264 Presence and Instant Messaging", February 2000. 266 [RFC3688] Mealling, M., "The IETF XML Registry", January 2004. 268 9.2 Informative References 270 [I-D.ietf-geopriv-common-policy] 271 Schulzrinne, H., Morris, J., Tschofenig, H., Polk, J. and 272 J. Rosenberg, "A Document Format for Expressing Privacy 273 Preferences", draft-ietf-geopriv-common-policy-01 (work in 274 progress), July 2004, 275 . 277 [I-D.ietf-geopriv-policy] 278 Schulzrinne, H., Morris, J., Tschofenig, H., Cuellar, J. 279 and J. Polk, "Geopriv Policy", 280 draft-ietf-geopriv-policy-01 (work in progress), February 281 2004, . 283 [I-D.rosenberg-simple-common-policy-caps] 284 Rosenberg, J., "An Extensible Markup Language (XML) 285 Representation for Expressing Policy Capabilities", 286 draft-rosenberg-simple-common-policy-caps-00 (work in 287 progress), February 2004, 288 . 290 [I-D.rosenberg-simple-pres-policy-caps] 291 Rosenberg, J., "An Extensible Markup Language (XML) 292 Representation for Expressing Presence Policy 293 Capabilities", draft-rosenberg-simple-pres-policy-caps-00 294 (work in progress), February 2004, 295 . 297 Authors' Addresses 299 Christian Guenther 300 Siemens 301 Otto-Hahn-Ring 6 302 Munich, Bayern 81739 303 Germany 305 EMail: christian.guenther@siemens.com 307 Hannes Tschofenig 308 Siemens 309 Otto-Hahn-Ring 6 310 Munich, Bayern 81739 311 Germany 313 EMail: hannes.tschofenig@siemens.com 315 Intellectual Property Statement 317 The IETF takes no position regarding the validity or scope of any 318 Intellectual Property Rights or other rights that might be claimed to 319 pertain to the implementation or use of the technology described in 320 this document or the extent to which any license under such rights 321 might or might not be available; nor does it represent that it has 322 made any independent effort to identify any such rights. Information 323 on the procedures with respect to rights in RFC documents can be 324 found in BCP 78 and BCP 79. 326 Copies of IPR disclosures made to the IETF Secretariat and any 327 assurances of licenses to be made available, or the result of an 328 attempt made to obtain a general license or permission for the use of 329 such proprietary rights by implementers or users of this 330 specification can be obtained from the IETF on-line IPR repository at 331 http://www.ietf.org/ipr. 333 The IETF invites any interested party to bring to its attention any 334 copyrights, patents or patent applications, or other proprietary 335 rights that may cover technology that may be required to implement 336 this standard. Please address the information to the IETF at 337 ietf-ipr@ietf.org. 339 Disclaimer of Validity 341 This document and the information contained herein are provided on an 342 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 343 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 344 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 345 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 346 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 347 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 349 Copyright Statement 351 Copyright (C) The Internet Society (2004). This document is subject 352 to the rights, licenses and restrictions contained in BCP 78, and 353 except as set forth therein, the authors retain all their rights. 355 Acknowledgment 357 Funding for the RFC Editor function is currently provided by the 358 Internet Society.