Geopriv                                                      C. Guenther
Internet-Draft                                             H. Tschofenig
Expires: April 25, 2005                                          Siemens
                                                        October 25, 2004


   An Extensible Markup Language (XML) Representation for Expressing
          Geographic Location Information Policy Capabilities
               draft-guenther-geopriv-policy-caps-01.txt

Status of this Memo

   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 become aware will be disclosed, in accordance with
   RFC 3668.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on April 25, 2005.

Copyright Notice

   Copyright (C) The Internet Society (2004).

Abstract

   This specification defines a set of Extensible Markup Language (XML)
   elements for expressing geographic location information policy
   capabilities.






Guenther & Tschofenig    Expires April 25, 2005                 [Page 1]

Internet-Draft        Geopriv Policy Capabilities           October 2004


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Structure of Geopriv Policy Capabilities . . . . . . . . . . .  5
   4.  XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . .  6
   5.  Example Document . . . . . . . . . . . . . . . . . . . . . . .  7
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . .  8
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  9
     7.1   Namespace Registration . . . . . . . . . . . . . . . . . .  9
     7.2   Supported Geopriv Permissions Schema Registration  . . . .  9
   8.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 11
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
   9.1   Normative References . . . . . . . . . . . . . . . . . . . . 12
   9.2   Informative References . . . . . . . . . . . . . . . . . . . 12
       Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 13
       Intellectual Property and Copyright Statements . . . . . . . . 14


































Guenther & Tschofenig    Expires April 25, 2005                 [Page 2]

Internet-Draft        Geopriv Policy Capabilities           October 2004


1.  Introduction

   Authorization policies are an important component of presence
   [RFC2778].  They allow the presentity to grant access to specific
   pieces of information to watchers.  Authorization policies haven been
   designed to be extensible.  For this reason
   [I-D.rosenberg-simple-common-policy-caps] defines a generic
   Extensible Markup Language (XML) based format for representing policy
   capabilities.  That format applies to many policy types, including
   location and presence.  This specification extends that one by
   defining policy capabilities specific to geographic location
   information.  Those policy capabilities correspond to the conditions,
   actions and transformations defined in [I-D.ietf-geopriv-policy].






































Guenther & Tschofenig    Expires April 25, 2005                 [Page 3]

Internet-Draft        Geopriv Policy Capabilities           October 2004


2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

   Furthermore, the terminology defined in [I-D.ietf-geopriv-policy] is
   used.











































Guenther & Tschofenig    Expires April 25, 2005                 [Page 4]

Internet-Draft        Geopriv Policy Capabilities           October 2004


3.  Structure of Geopriv Policy Capabilities

   The structure of common policy capability documents is defined in
   [I-D.rosenberg-simple-common-policy-caps].  In that specification,
   each policy capability document has three components - a list of
   supported conditions, a list of supported actions, and a list of
   supported transformations.  This specification merely extends that
   document with the conditions, actions and transformations defined in
   [I-D.ietf-geopriv-policy].  It does so by defining the following
   empty elements:

   o  civil-loc-condition
   o  geospatial-loc-condition
   o  civil-loc-transformation
   o  set-retention
   o  set-distribution
   o  keep-rules
   o  longitude-resolution
   o  latitude-resolution
   o  altitude-resolution
   o  provide-timezone

   Each of these elements indicates whether the respective attribute in
   [I-D.ietf-geopriv-policy] is supported.  All of these elements are
   defined within the namespace:

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
























Guenther & Tschofenig    Expires April 25, 2005                 [Page 5]

Internet-Draft        Geopriv Policy Capabilities           October 2004


4.  XML Schema


   <?xml version="1.0" encoding="UTF-8"?>
   <xs:schema
     targetNamespace=
       "urn:ietf:params:xml:ns:supported-geopriv-permissions"
     xmlns:sgp=
       "urn:ietf:params:xml:ns:supported-geopriv-permissions"
     xmlns:sp=
       "urn:ietf:params:xml:ns:supported-permissions"
     xmlns:xs=
       "http://www.w3.org/2001/XMLSchema"
     elementFormDefault="qualified"
     attributeFormDefault="unqualified">

     <xs:import namespace="urn:ietf:params:xml:ns:supported-permissions"
                schemaLocation="supported-permissions.xsd"/>

     <xs:element name="civil-loc-condition"
                 substitutionGroup="sp:condition"/>
     <xs:element name="geospatial-loc-condition"
                 substitutionGroup="sp:condition"/>

     <xs:element name="civil-loc-transformation"
                 substitutionGroup="sp:transformation"/>
     <xs:element name="set-retention"
                 substitutionGroup="sp:transformation"/>
     <xs:element name="set-distribution"
                 substitutionGroup="sp:transformation"/>
     <xs:element name="keep-rules"
                 substitutionGroup="sp:transformation"/>
     <xs:element name="longitude-resolution"
                 substitutionGroup="sp:transformation"/>
     <xs:element name="latitude-resolution"
                 substitutionGroup="sp:transformation"/>
     <xs:element name="altitude-resolution"
                 substitutionGroup="sp:transformation"/>
     <xs:element name="provide-timezone"
                 substitutionGroup="sp:transformation"/>

   </xs:schema>









Guenther & Tschofenig    Expires April 25, 2005                 [Page 6]

Internet-Draft        Geopriv Policy Capabilities           October 2004


5.  Example Document

   The following document indicates that the identity, validity, and
   sphere conditions are supported, each of which is defined in
   [I-D.ietf-geopriv-common-policy].  It also indicates that the
   geolocation-specific condition named geospatial-loc-condition is
   supported.  Support of the geolocation-specific transformations named
   civil-loc-transformation, longitude-resolution and
   latitude-resolution is indicated by the three child elements of the
   <transformations> element:


   <?xml version="1.0" encoding="UTF-8"?>
   <supported-permissions
     xmlns="urn:ietf:params:xml:ns:supported-permissions"
     xmlns:sgp="urn:ietf:params:xml:ns:supported-geopriv-permissions"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation=
       "urn:ietf:params:xml:ns:supported-permissions
        supported-permissions.xsd
        urn:ietf:params:xml:ns:supported-geopriv-permissions
        supported-geopriv-permissions.xsd">

     <conditions>
       <identity/>
       <validity/>
       <sphere/>
       <sgp:geospatial-loc-condition/>
     </conditions>

     <actions>
     </actions>

     <transformations>
       <sgp:civil-loc-transformation/>
       <sgp:longitude-resolution/>
       <sgp:latitude-resolution/>
     </transformations>

   </supported-permissions>











Guenther & Tschofenig    Expires April 25, 2005                 [Page 7]

Internet-Draft        Geopriv Policy Capabilities           October 2004


6.  Security Considerations

   This specification does not introduce any new security considerations
   beyond those discussed in [I-D.rosenberg-simple-common-policy-caps].















































Guenther & Tschofenig    Expires April 25, 2005                 [Page 8]

Internet-Draft        Geopriv Policy Capabilities           October 2004


7.  IANA Considerations

   This section registers a new XML namespace and a new XML schema with
   IANA.

7.1  Namespace Registration

   URI: urn:ietf:params:xml:ns:supported-geopriv-permissions
   Registrant Contact: IETF Geopriv Working Group, Christian Guenther
      (christian.guenther@siemens.com), Hannes Tschofenig
      (hannes.tschofenig@siemens.com).
   XML:

   BEGIN
   <?xml version="1.0"?>
   <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
     "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
   <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
     <meta http-equiv="content-type"
           content="text/html;charset=iso-8859-1"/>
     <title>Supported Geopriv Permissions</title>
   </head>
   <body>
     <h1>Namespace for Supported Geopriv Permissions</h1>
     <h2>urn:ietf:params:xml:ns:supported-geopriv-permissions</h2>
     <p>See <a href="[[[URL of published RFC]]]">RFCXXXX
         [NOTE TO IANA/RFC-EDITOR:
        Please replace XXXX with the RFC number of this
       specification.]
       </a>.</p>
   </body>
   </html>
   END


7.2  Supported Geopriv Permissions Schema Registration

   URI: Please assign.
   Registrant Contact: IETF Geopriv Working Group, Christian Guenther
      (christian.guenther@siemens.com), Hannes Tschofenig
      (hannes.tschofenig@siemens.com).
   XML: The XML schema to be registered is contained in section Section
      4.  Its first line is

   <?xml version="1.0" encoding="UTF-8"?>

       and its last line is



Guenther & Tschofenig    Expires April 25, 2005                 [Page 9]

Internet-Draft        Geopriv Policy Capabilities           October 2004


   </xs:schema>


















































Guenther & Tschofenig    Expires April 25, 2005                [Page 10]

Internet-Draft        Geopriv Policy Capabilities           October 2004


8.  Acknowledgments

   The authors would like to thank Jonathan Rosenberg whose Presence
   Policy Capabilities document [I-D.rosenberg-simple-pres-policy-caps]
   served as template for this document.














































Guenther & Tschofenig    Expires April 25, 2005                [Page 11]

Internet-Draft        Geopriv Policy Capabilities           October 2004


9.  References

9.1  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", March 1997.

   [RFC2778]  Day, M., Rosenberg, J. and H. Sugano, "A Model for
              Presence and Instant Messaging", February 2000.

   [RFC3688]  Mealling, M., "The IETF XML Registry", January 2004.

9.2  Informative References

   [I-D.ietf-geopriv-common-policy]
              Schulzrinne, H., "A Document Format for Expressing Privacy
              Preferences", draft-ietf-geopriv-common-policy-02 (work in
              progress), October 2004.

   [I-D.ietf-geopriv-policy]
              Schulzrinne, H., "A Document Format for Expressing Privacy
              Preferences for Location  Information",
              draft-ietf-geopriv-policy-03 (work in progress), October
              2004.

   [I-D.ietf-simple-presence-rules]
              Rosenberg, J., "Presence Authorization Rules",
              draft-ietf-simple-presence-rules-00 (work in progress),
              May 2004.

   [I-D.rosenberg-simple-common-policy-caps]
              Rosenberg, J., "An Extensible Markup Language (XML)
              Representation for Expressing Policy  Capabilities",
              draft-rosenberg-simple-common-policy-caps-01 (work in
              progress), July 2004.

   [I-D.rosenberg-simple-pres-policy-caps]
              Rosenberg, J., "An Extensible Markup Language (XML)
              Representation for Expressing Presence  Policy
              Capabilities", draft-rosenberg-simple-pres-policy-caps-01
              (work in progress), July 2004.










Guenther & Tschofenig    Expires April 25, 2005                [Page 12]

Internet-Draft        Geopriv Policy Capabilities           October 2004


Authors' Addresses

   Christian Guenther
   Siemens
   Otto-Hahn-Ring 6
   Munich, Bayern  81739
   Germany

   EMail: christian.guenther@siemens.com


   Hannes Tschofenig
   Siemens
   Otto-Hahn-Ring 6
   Munich, Bayern  81739
   Germany

   EMail: hannes.tschofenig@siemens.com

































Guenther & Tschofenig    Expires April 25, 2005                [Page 13]

Internet-Draft        Geopriv Policy Capabilities           October 2004


Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Disclaimer of Validity

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Copyright Statement

   Copyright (C) The Internet Society (2004).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.


Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.




Guenther & Tschofenig    Expires April 25, 2005                [Page 14]