draft-ietf-sipping-consent-format-07.txt   draft-ietf-sipping-consent-format-08.txt 
SIPPING G. Camarillo SIPPING G. Camarillo
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Standards Track May 29, 2008 Intended status: Standards Track August 1, 2008
Expires: November 30, 2008 Expires: February 2, 2009
A Document Format for Requesting Consent A Document Format for Requesting Consent
draft-ietf-sipping-consent-format-07.txt draft-ietf-sipping-consent-format-08.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 34 skipping to change at page 1, line 34
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 30, 2008. This Internet-Draft will expire on February 2, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document defines an Extensible Markup Language (XML) format for This document defines an Extensible Markup Language (XML) format for
a permission document used to request consent. A permission document a permission document used to request consent. A permission document
written in this format is used by a relay to request a specific written in this format is used by a relay to request a specific
skipping to change at page 2, line 20 skipping to change at page 2, line 20
3.1. Conditions . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. Conditions . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1.1. Recipient Condition . . . . . . . . . . . . . . . . . 4 3.1.1. Recipient Condition . . . . . . . . . . . . . . . . . 4
3.1.2. Identity Condition . . . . . . . . . . . . . . . . . . 5 3.1.2. Identity Condition . . . . . . . . . . . . . . . . . . 5
3.1.3. Target Condition . . . . . . . . . . . . . . . . . . . 8 3.1.3. Target Condition . . . . . . . . . . . . . . . . . . . 8
3.1.4. Validity Condition . . . . . . . . . . . . . . . . . . 8 3.1.4. Validity Condition . . . . . . . . . . . . . . . . . . 8
3.1.5. Sphere Condition . . . . . . . . . . . . . . . . . . . 8 3.1.5. Sphere Condition . . . . . . . . . . . . . . . . . . . 8
3.2. Actions . . . . . . . . . . . . . . . . . . . . . . . . . 8 3.2. Actions . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2.1. Translation Handling . . . . . . . . . . . . . . . . . 8 3.2.1. Translation Handling . . . . . . . . . . . . . . . . . 8
4. Example Document . . . . . . . . . . . . . . . . . . . . . . . 9 4. Example Document . . . . . . . . . . . . . . . . . . . . . . . 9
5. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 10 5. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 10
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 6. Extensibility . . . . . . . . . . . . . . . . . . . . . . . . 11
6.1. XML Namespace Registration . . . . . . . . . . . . . . . . 11 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
6.2. XML Schema Registration . . . . . . . . . . . . . . . . . 12 7.1. XML Namespace Registration . . . . . . . . . . . . . . . . 12
7. Security Considerations . . . . . . . . . . . . . . . . . . . 12 7.2. XML Schema Registration . . . . . . . . . . . . . . . . . 12
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 8. Security Considerations . . . . . . . . . . . . . . . . . . . 13
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
9.1. Normative References . . . . . . . . . . . . . . . . . . . 13 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
9.2. Informative References . . . . . . . . . . . . . . . . . . 13 10.1. Normative References . . . . . . . . . . . . . . . . . . . 13
10.2. Informative References . . . . . . . . . . . . . . . . . . 14
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14
Intellectual Property and Copyright Statements . . . . . . . . . . 15 Intellectual Property and Copyright Statements . . . . . . . . . . 15
1. Introduction 1. Introduction
The framework for consent-based communications in the Session The framework for consent-based communications in the Session
Initiation Protocol (SIP) [I-D.ietf-sip-consent-framework] identifies Initiation Protocol (SIP) [I-D.ietf-sip-consent-framework] identifies
the need for a format to create permission documents. Such the need for a format to create permission documents. Such
permission documents are used by SIP [RFC3261] relays to request permission documents are used by SIP [RFC3261] relays to request
permission to perform translations. A relay is defined as any SIP permission to perform translations. A relay is defined as any SIP
skipping to change at page 10, line 8 skipping to change at page 10, line 8
+---------------------+ +---------------------+
| | | |
| Recipient | | Recipient |
| sip:bob@example.org | | sip:bob@example.org |
| | | |
+---------------------+ +---------------------+
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<cp:ruleset <cp:ruleset
xmlns="urn:ietf:params:xml:ns:consent-rules" xmlns="urn:ietf:params:xml:ns:consent-rules"
xmlns:cp="urn:ietf:params:xml:ns:common-policy" xmlns:cp="urn:ietf:params:xml:ns:common-policy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<cp:rule id="f1"> <cp:rule id="f1">
<cp:conditions> <cp:conditions>
<cp:identity> <cp:identity>
<cp:many/> <cp:many/>
</cp:identity> </cp:identity>
<recipient> <recipient>
<cp:one id="sip:bob@example.org"/> <cp:one id="sip:bob@example.org"/>
</recipient> </recipient>
<target> <target>
<cp:one id="sip:alices-friends@example.com"/> <cp:one id="sip:alices-friends@example.com"/>
</target> </target>
</cp:conditions> </cp:conditions>
<cp:actions> <cp:actions>
<trans-handling <trans-handling
perm-uri="sips:grant-1awdch5Fasddfce34@example.com"> perm-uri="sips:grant-1awdch5Fasddfce34@example.com"
grant</trans-handling> >grant</trans-handling>
<trans-handling <trans-handling
perm-uri="https://example.com/grant-1awdch5Fasddfce34"> perm-uri="https://example.com/grant-1awdch5Fasddfce34"
grant</trans-handling> >grant</trans-handling>
<trans-handling <trans-handling
perm-uri="sips:deny-23rCsdfgvdT5sdfgye@example.com"> perm-uri="sips:deny-23rCsdfgvdT5sdfgye@example.com"
deny</trans-handling> >deny</trans-handling>
<trans-handling <trans-handling
perm-uri="https://example.com/deny-23rCsdfgvdT5sdfgye"> perm-uri="https://example.com/deny-23rCsdfgvdT5sdfgye"
deny</trans-handling> >deny</trans-handling>
</cp:actions> </cp:actions>
<cp:transformations/> <cp:transformations/>
</cp:rule> </cp:rule>
</cp:ruleset> </cp:ruleset>
5. XML Schema 5. XML Schema
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:consent-rules" targetNamespace="urn:ietf:params:xml:ns:consent-rules"
xmlns:cr="urn:ietf:params:xml:ns:consent-rules" xmlns:cr="urn:ietf:params:xml:ns:consent-rules"
skipping to change at page 11, line 38 skipping to change at page 11, line 38
<xs:extension base="trans-values"> <xs:extension base="trans-values">
<xs:attribute name="perm-uri" type="xs:anyURI" <xs:attribute name="perm-uri" type="xs:anyURI"
use="required"/> use="required"/>
</xs:extension> </xs:extension>
</xs:simpleContent> </xs:simpleContent>
</xs:complexType> </xs:complexType>
</xs:element> </xs:element>
</xs:schema> </xs:schema>
6. IANA Considerations 6. Extensibility
This specification defines elements that do not have extension points
in the "urn:ietf:params:xml:ns:consent-rules" namespace. Instance
documents that utilize these element definitions SHOULD be schema
valid. Applications processing instance documents with content that
is not understood by the application MUST ignore that content. IETF
extension documents of this specification MAY reuse the
"urn:ietf:params:xml:ns:consent-rules" namespace to define new
elements.
7. IANA Considerations
This section registers a new XML namespace and a new XML schema per This section registers a new XML namespace and a new XML schema per
the procedures in [RFC3688]. the procedures in [RFC3688].
6.1. XML Namespace Registration 7.1. XML Namespace Registration
URI: urn:ietf:params:xml:ns:consent-rules URI: urn:ietf:params:xml:ns:consent-rules
Registrant Contact: IETF SIPPING working group, Registrant Contact: IETF SIPPING working group,
<sipping@ietf.org>, Gonzalo Camarillo <sipping@ietf.org>, Gonzalo Camarillo
<Gonzalo.Camarillo@ericsson.com> <Gonzalo.Camarillo@ericsson.com>
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <html xmlns="http://www.w3.org/1999/xhtml">
<head> <head>
<meta http-equiv="content-type" <meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
skipping to change at page 12, line 27 skipping to change at page 12, line 41
<h1>Namespace for Permission Documents</h1> <h1>Namespace for Permission Documents</h1>
<h2>urn:ietf:params:xml:ns:consent-rules</h2> <h2>urn:ietf:params:xml:ns:consent-rules</h2>
<p>See <a href="[URL of published RFC]">RFCXXXX <p>See <a href="[URL of published RFC]">RFCXXXX
[NOTE TO IANA/RFC-EDITOR: [NOTE TO IANA/RFC-EDITOR:
Please replace XXXX with the RFC number of this Please replace XXXX with the RFC number of this
specification.]</a>.</p> specification.]</a>.</p>
</body> </body>
</html> </html>
END END
6.2. XML Schema Registration 7.2. XML Schema Registration
URI: urn:ietf:params:xml:schema:consent-rules URI: urn:ietf:params:xml:schema:consent-rules
Registrant Contact: IETF SIPPING working group, Registrant Contact: IETF SIPPING working group,
<sipping@ietf.org>, Gonzalo Camarillo <sipping@ietf.org>, Gonzalo Camarillo
<Gonzalo.Camarillo@ericsson.com> <Gonzalo.Camarillo@ericsson.com>
XML: The XML schema to be registered is contained in Section 5. XML: The XML schema to be registered is contained in Section 5.
7. Security Considerations 8. Security Considerations
The framework for consent-based communications in the Session The framework for consent-based communications in the Session
Initiation Protocol (SIP) [I-D.ietf-sip-consent-framework] discusses Initiation Protocol (SIP) [I-D.ietf-sip-consent-framework] discusses
security-related issues, such as how to authenticate SIP and HTTP security-related issues, such as how to authenticate SIP and HTTP
requests granting permissions and how to transport permission requests granting permissions and how to transport permission
documents between relays and recipients, that are directly related to documents between relays and recipients, that are directly related to
this specification. this specification.
8. Acknowledgements 9. Acknowledgements
Jonathan Rosenberg provided useful ideas on this document. Hannes Jonathan Rosenberg provided useful ideas on this document. Hannes
Tschofenig helped align this document with common policy. Ben Tschofenig helped align this document with common policy. Ben
Campbell and Mary Barnes performed a thorough review of this Campbell and Mary Barnes performed a thorough review of this
document. Lakshminath Dondeti provided useful comments. document. Lakshminath Dondeti provided useful comments.
9. References 10. References
9.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2617] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., [RFC2617] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S.,
Leach, P., Luotonen, A., and L. Stewart, "HTTP Leach, P., Luotonen, A., and L. Stewart, "HTTP
Authentication: Basic and Digest Access Authentication", Authentication: Basic and Digest Access Authentication",
RFC 2617, June 1999. RFC 2617, June 1999.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
skipping to change at page 13, line 45 skipping to change at page 14, line 12
Polk, J., and J. Rosenberg, "Common Policy: A Document Polk, J., and J. Rosenberg, "Common Policy: A Document
Format for Expressing Privacy Preferences", RFC 4745, Format for Expressing Privacy Preferences", RFC 4745,
February 2007. February 2007.
[I-D.ietf-sip-consent-framework] [I-D.ietf-sip-consent-framework]
Rosenberg, J., Camarillo, G., and D. Willis, "A Framework Rosenberg, J., Camarillo, G., and D. Willis, "A Framework
for Consent-based Communications in the Session Initiation for Consent-based Communications in the Session Initiation
Protocol (SIP)", draft-ietf-sip-consent-framework-04 (work Protocol (SIP)", draft-ietf-sip-consent-framework-04 (work
in progress), January 2008. in progress), January 2008.
9.2. Informative References 10.2. Informative References
[RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", [RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers",
RFC 3966, December 2004. RFC 3966, December 2004.
[RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private [RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private
Extensions to the Session Initiation Protocol (SIP) for Extensions to the Session Initiation Protocol (SIP) for
Asserted Identity within Trusted Networks", RFC 3325, Asserted Identity within Trusted Networks", RFC 3325,
November 2002. November 2002.
Author's Address Author's Address
 End of changes. 18 change blocks. 
29 lines changed or deleted 41 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/