draft-ietf-sipping-capacity-attribute-05.txt   draft-ietf-sipping-capacity-attribute-06.txt 
SIPPING Working Group M. Garcia-Martin SIPPING Working Group M. Garcia-Martin
Internet-Draft Nokia Siemens Networks Internet-Draft Nokia Siemens Networks
Intended status: Standards Track G. Camarillo Intended status: Standards Track G. Camarillo
Expires: May 16, 2008 Ericsson Expires: June 20, 2008 Ericsson
November 13, 2007 December 18, 2007
Extensible Markup Language (XML) Format Extension for Representing Copy Extensible Markup Language (XML) Format Extension for Representing Copy
Control Attributes in Resource Lists Control Attributes in Resource Lists
draft-ietf-sipping-capacity-attribute-05.txt draft-ietf-sipping-capacity-attribute-06.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 36 skipping to change at page 1, line 36
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 May 16, 2008. This Internet-Draft will expire on June 20, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
In certain types of multimedia communications, a Session Initiation In certain types of multimedia communications, a Session Initiation
Protocol (SIP) request is distributed to a group of SIP User Agents Protocol (SIP) request is distributed to a group of SIP User Agents
(UAs). The sender sends a single SIP request to a server which (UAs). The sender sends a single SIP request to a server which
skipping to change at page 7, line 27 skipping to change at page 7, line 27
use URIs marked with the "bcc" 'copyControl' attribute to route SIP use URIs marked with the "bcc" 'copyControl' attribute to route SIP
requests, but MUST NOT include them in recipient-history lists. requests, but MUST NOT include them in recipient-history lists.
A new 'anonymize' attribute can be included in a <entry> element of A new 'anonymize' attribute can be included in a <entry> element of
the resource list document format [RFC4826]. If set to a "true" the resource list document format [RFC4826]. If set to a "true"
value, it provides an indication to the URI-list server for not value, it provides an indication to the URI-list server for not
disclosing the URI itself in a URI-list sent to the recipient, but disclosing the URI itself in a URI-list sent to the recipient, but
instead, to anonymize the URI (i.e., making it bogus in the instead, to anonymize the URI (i.e., making it bogus in the
recipient-history XML resource list). URI-list servers can use URIs recipient-history XML resource list). URI-list servers can use URIs
tagged with the 'anonymize' attribute for routing SIP requests, but tagged with the 'anonymize' attribute for routing SIP requests, but
MUST convert them to an anonymized URI (such as MUST convert them the SIP URI "sip:anonymous@anonymous.invalid" in
sip:anonymous@anonymous.invalid) in recipient-history lists. The recipient-history lists. The default value of the 'anonymize'
default value of the 'anonymize' attribute is "false". attribute is "false".
There are occasions where the URI-list server encounters the same URI There are occasions where the URI-list server encounters the same URI
entry duplicated in a resource list, where duplicated URI entries are entry duplicated in a resource list, where duplicated URI entries are
tagged with the same or different values of the 'copyControl' tagged with the same or different values of the 'copyControl'
attribute. There are no reasonable usages that justify duplicated attribute. There are no reasonable usages that justify duplicated
URIs in resource lists, thus, this is considered an error. URI-list URIs in resource lists, thus, this is considered an error. URI-list
servers should not send duplicated copies of the same SIP request to servers should not send duplicated copies of the same SIP request to
the same intended recipient. In case the URI-list server encounters the same intended recipient. In case the URI-list server encounters
the same URI entry duplicated in a resource list, it should send at the same URI entry duplicated in a resource list, it should send at
most a single copy of the request to that intended recipient. For most a single copy of the request to that intended recipient. For
skipping to change at page 10, line 42 skipping to change at page 10, line 42
URIs listed in the recipient list (so, in our example, it creates 7 URIs listed in the recipient list (so, in our example, it creates 7
SIP requests). The URI-list server processes the recipient list and SIP requests). The URI-list server processes the recipient list and
creates a recipient-history list that is included in each of the creates a recipient-history list that is included in each of the
outgoing SIP requests. The process is as follows: the URI-list outgoing SIP requests. The process is as follows: the URI-list
server creates a new recipient-history list, based on the recipient server creates a new recipient-history list, based on the recipient
list, but with changes. First it copies all the URIs (<entry> list, but with changes. First it copies all the URIs (<entry>
elements) marked with the "to" or "cc" 'copyControl' attributes, elements) marked with the "to" or "cc" 'copyControl' attributes,
which do not contain an 'anonymize' attribute (or when the which do not contain an 'anonymize' attribute (or when the
'anonymize' attribute is set to "false"). Then all the URIs marked 'anonymize' attribute is set to "false"). Then all the URIs marked
with a 'copyControl' attribute set to "to" and 'anonymize' attribute with a 'copyControl' attribute set to "to" and 'anonymize' attribute
set to "true" are replaced with an anonymous URI, such as set to "true" are replaced with the SIP anonymous URI
"sip:anonymous@anonymous.invalid". In this entry the URI-list server "sip:anonymous@anonymous.invalid". In this entry the URI-list server
also adds the original value of the 'copyControl' attribute ("to" in also adds the original value of the 'copyControl' attribute ("to" in
our example), and it adds a 'count' attribute containing the number our example), and it adds a 'count' attribute containing the number
of anonymous entries in this group ("2" in our example). Then the of anonymous entries in this group ("2" in our example). Then the
URI-list server does the same operation to the URIs tagged with the URI-list server does the same operation to the URIs tagged with the
'copyControl' attribute set to "cc" and 'anonymize' attribute set to 'copyControl' attribute set to "cc" and 'anonymize' attribute set to
"true", adding also the 'count' attribute containing the number of "true", adding also the 'count' attribute containing the number of
anonymous attributes in this group ("1" in the example). Last, the anonymous attributes in this group ("1" in the example). Last, the
URI-list server completely removes URIs marked with the "bcc" URI-list server completely removes URIs marked with the "bcc"
'copyControl' attribute. The resulting recipient-history list is 'copyControl' attribute. The resulting recipient-history list is
skipping to change at page 14, line 42 skipping to change at page 14, line 42
Registrant Contact: IETF, SIPPING working group, (sipping@ietf.org), Registrant Contact: IETF, SIPPING working group, (sipping@ietf.org),
Miguel Garcia-Martin (miguel.an.garcia@nokia.com). Miguel Garcia-Martin (miguel.an.garcia@nokia.com).
The XML for this schema can be found as the sole content of The XML for this schema can be found as the sole content of
Section 5. Section 5.
10. Acknowledgements 10. Acknowledgements
Thanks to Dean Willis, Jari Urpalainen, Pekka Kuure, Atsushi Sato, Thanks to Dean Willis, Jari Urpalainen, Pekka Kuure, Atsushi Sato,
Brian Rosen, Mary Barnes, and James Polk for reviewing this document Brian Rosen, Mary Barnes, James Polk, and Brian E. Carpenter for
and providing helpful comments. reviewing this document and providing helpful comments.
11. References 11. References
11.1. Normative References 11.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.
[RFC2183] Troost, R., Dorner, S., and K. Moore, "Communicating [RFC2183] Troost, R., Dorner, S., and K. Moore, "Communicating
Presentation Information in Internet Messages: The Presentation Information in Internet Messages: The
skipping to change at page 15, line 40 skipping to change at page 15, line 40
[RFC4346] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC4346] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.1", RFC 4346, April 2006. (TLS) Protocol Version 1.1", RFC 4346, April 2006.
[RFC4826] Rosenberg, J., "Extensible Markup Language (XML) Formats [RFC4826] Rosenberg, J., "Extensible Markup Language (XML) Formats
for Representing Resource Lists", RFC 4826, May 2007. for Representing Resource Lists", RFC 4826, May 2007.
[I-D.ietf-sipping-uri-services] [I-D.ietf-sipping-uri-services]
Camarillo, G. and A. Roach, "Framework and Security Camarillo, G. and A. Roach, "Framework and Security
Considerations for Session Initiation Protocol (SIP) Considerations for Session Initiation Protocol (SIP)
Uniform Resource Identifier (URI)-List Services", Uniform Resource Identifier (URI)-List Services",
draft-ietf-sipping-uri-services-06 (work in progress), draft-ietf-sipping-uri-services-07 (work in progress),
September 2006. November 2007.
11.2. Informational References 11.2. Informational References
[I-D.ietf-sip-uri-list-conferencing] [I-D.ietf-sip-uri-list-conferencing]
Camarillo, G. and A. Johnston, "Conference Establishment Camarillo, G. and A. Johnston, "Conference Establishment
Using Request-Contained Lists in the Session Initiation Using Request-Contained Lists in the Session Initiation
Protocol (SIP)", draft-ietf-sip-uri-list-conferencing-01 Protocol (SIP)", draft-ietf-sip-uri-list-conferencing-02
(work in progress), January 2007. (work in progress), November 2007.
[I-D.ietf-sip-uri-list-message] [I-D.ietf-sip-uri-list-message]
Garcia-Martin, M. and G. Camarillo, "Multiple-Recipient Garcia-Martin, M. and G. Camarillo, "Multiple-Recipient
MESSAGE Requests in the Session Initiation Protocol MESSAGE Requests in the Session Initiation Protocol
(SIP)", draft-ietf-sip-uri-list-message-01 (work in (SIP)", draft-ietf-sip-uri-list-message-02 (work in
progress), January 2007. progress), November 2007.
[I-D.ietf-sip-body-handling] [I-D.ietf-sip-body-handling]
Camarillo, G., "Message Body Handling in the Session Camarillo, G., "Message Body Handling in the Session
Initiation Protocol (SIP)", Initiation Protocol (SIP)",
draft-ietf-sip-body-handling-00 (work in progress), draft-ietf-sip-body-handling-00 (work in progress),
August 2007. August 2007.
Authors' Addresses Authors' Addresses
Miguel A. Garcia-Martin Miguel A. Garcia-Martin
 End of changes. 9 change blocks. 
16 lines changed or deleted 16 lines changed or added

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