draft-ietf-sipcore-presence-scaling-requirements-01.txt   draft-ietf-sipcore-presence-scaling-requirements-02.txt 
SIPPING WG A. Houri SIPPING WG A. Houri
Internet-Draft IBM Internet-Draft IBM
Intended status: Informational S. Parameswar Intended status: Informational S. Parameswar
Expires: January 14, 2010 Microsoft Corporation Expires: March 6, 2010 Microsoft Corporation
E. Aoki E. Aoki
AOL LLC AOL LLC
V. Singh V. Singh
H. Schulzrinne H. Schulzrinne
Columbia U. Columbia U.
July 13, 2009 September 2, 2009
Scaling Requirements for Presence in SIP/SIMPLE Scaling Requirements for Presence in SIP/SIMPLE
draft-ietf-sipcore-presence-scaling-requirements-01.txt draft-ietf-sipcore-presence-scaling-requirements-02.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and 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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 January 14, 2010. This Internet-Draft will expire on March 6, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. and restrictions with respect to this document.
Abstract Abstract
The document provides a set of requirements for enabling inter-domain The document lists requirements for optimizations of SIP/SIMPLE.
scaling in presence for SIP/SIMPLE. These optimizations should reduce the load on the network and the
presence servers due to inter-domain presence subscriptions. The
need for the requirements is based on a separate document that
provides scaling analysis for inter-domain presence over SIP/SIMPLE.
Table of Contents Table of Contents
1. Requirements notation . . . . . . . . . . . . . . . . . . . . . 3 1. Requirements notation . . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Backward Compatibility Requirements . . . . . . . . . . . . 4 3.1. Backward Compatibility Requirements . . . . . . . . . . . . 4
3.2. Policy, Privacy, Permissions Requirements . . . . . . . . . 4 3.2. Policy, Privacy, Permissions Requirements . . . . . . . . . 4
3.3. Scalability Requirements . . . . . . . . . . . . . . . . . 4 3.3. Scalability Requirements . . . . . . . . . . . . . . . . . 4
3.4. Topology Requirements . . . . . . . . . . . . . . . . . . . 5 3.4. Topology Requirements . . . . . . . . . . . . . . . . . . . 5
skipping to change at page 6, line 21 skipping to change at page 6, line 21
assumptions about the network (using only TCP, for example. In assumptions about the network (using only TCP, for example. In
[I-D.ietf-simple-interdomain-scaling-analysis], see the section that [I-D.ietf-simple-interdomain-scaling-analysis], see the section that
calculates the number of bytes and messages for an imaginary, calculates the number of bytes and messages for an imaginary,
optimized SIP). optimized SIP).
When a presence server connects to another server using current SIP/ When a presence server connects to another server using current SIP/
SIMPLE, there is an extreme number of redundant messages due to SIP's SIMPLE, there is an extreme number of redundant messages due to SIP's
support of both TCP and UDP and due to privacy controls that cause support of both TCP and UDP and due to privacy controls that cause
the sending of multiple presence documents for the same presentity. the sending of multiple presence documents for the same presentity.
A server-to-server protocol will have to address these issues. Some A server-to-server protocol will have to address these issues. Some
initial work to address= these issues can be found in: initial work to address these issues can be found in:
[I-D.ietf-simple-view-sharing] and [I-D.ietf-simple-view-sharing] and
[I-D.ietf-simple-intradomain-federation] and in other (still [I-D.ietf-simple-intradomain-federation] and in other (still
individual) drafts. individual) drafts.
Another issue related to protocol design is whether NOTIFY messages Another issue related to protocol design is whether NOTIFY messages
should not be considered as media just like audio, video, and even should not be considered as media just like audio, video, and even
text messaging. The SUBSCRIBE method may be extended to negotiate text messaging. The SUBSCRIBE method may be extended to negotiate
the route and other parameters of the NOTIFY messages, similar to the the route and other parameters of the NOTIFY messages, similar to the
way the INVITE method negotiates media parameters. This way, the way the INVITE method negotiates media parameters. This way, the
load can be shifted to specialized NOTIFY "relays" and taken off the load can be shifted to specialized NOTIFY "relays" and taken off the
skipping to change at page 7, line 40 skipping to change at page 7, line 40
[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.
9.2. Informational References 9.2. Informational References
[I-D.ietf-simple-interdomain-scaling-analysis] [I-D.ietf-simple-interdomain-scaling-analysis]
Houri, A., Aoki, E., Parameswar, S., Rang, T., Singh, V., Houri, A., Aoki, E., Parameswar, S., Rang, T., Singh, V.,
and H. Schulzrinne, "Presence Interdomain Scaling Analysis and H. Schulzrinne, "Presence Interdomain Scaling Analysis
for SIP/SIMPLE", for SIP/SIMPLE",
draft-ietf-simple-interdomain-scaling-analysis-07 (work in draft-ietf-simple-interdomain-scaling-analysis-08 (work in
progress), July 2009. progress), August 2009.
[I-D.ietf-simple-intradomain-federation] [I-D.ietf-simple-intradomain-federation]
Rosenberg, J., Houri, A., Smyth, C., and F. Audet, "Models Rosenberg, J., Houri, A., Smyth, C., and F. Audet, "Models
for Intra-Domain Presence and Instant Messaging (IM) for Intra-Domain Presence and Instant Messaging (IM)
Bridging", draft-ietf-simple-intradomain-federation-03 Bridging", draft-ietf-simple-intradomain-federation-04
(work in progress), March 2009. (work in progress), July 2009.
[I-D.ietf-simple-simple] [I-D.ietf-simple-simple]
Rosenberg, J., "SIMPLE made Simple: An Overview of the Rosenberg, J., "SIMPLE made Simple: An Overview of the
IETF Specifications for Instant Messaging and Presence IETF Specifications for Instant Messaging and Presence
using the Session Initiation Protocol (SIP)", using the Session Initiation Protocol (SIP)",
draft-ietf-simple-simple-05 (work in progress), draft-ietf-simple-simple-05 (work in progress),
March 2009. March 2009.
[I-D.ietf-simple-view-sharing] [I-D.ietf-simple-view-sharing]
Rosenberg, J., Donovan, S., and K. McMurry, "Optimizing Rosenberg, J., Donovan, S., and K. McMurry, "Optimizing
 End of changes. 8 change blocks. 
11 lines changed or deleted 14 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/