< draft-mdolly-sipping-push-00.txt   draft-mdolly-sipping-push-01.txt >
Network Working Group M. Dolly Network Working Group M. Dolly
Internet-Draft AT&T Internet-Draft AT&T
Intended status: Standards Track K. Bogestam Intended status: Standards Track S. Loreto
Expires: April 30, 2009 S. Loreto Expires: September 7, 2009 Ericsson
Ericsson K. Bogestam
Oct 27, 2008 March 6, 2009
Framework for Content Push Delivery over the Session Initiation Protocol Session Initiation Protocol (SIP) Event Package for Content Push
(SIP) Delivery
draft-mdolly-sipping-push-00 draft-mdolly-sipping-push-01
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
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.
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.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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 April 30, 2009. This Internet-Draft will expire on September 7, 2009.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Abstract Abstract
This document specifies a protocol for push delivery protocol over This document specifies an event package for content push delivery
SIP. The purpose is to allow an application on a UA to subscribe to protocol over SIP. The purpose is to allow an application on a UA to
updates to its own application events containing either content or subscribe to updates to its own application events containing either
references to the content. This document describes how content can content or references to the content. This document describes how
be pushed out to an application by the use of push events. As part content can be pushed out to an application by the use of push
of this framework, a new SIP event package is defined for events. A new SIP event package is defined for notification of push
notification of push events for content delivery. events for content delivery.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Definitions and Document Conventions . . . . . . . . . . . . . 3 2. Definitions and Document Conventions . . . . . . . . . . . . . 4
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. WAP (Wireless Application Protocol) Push . . . . . . . . . 3 3.1. WAP (Wireless Application Protocol) Push . . . . . . . . . 4
3.2. Web . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.2. Web . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2.1. Reversed Ajax . . . . . . . . . . . . . . . . . . . . 4 3.2.1. Reversed Ajax . . . . . . . . . . . . . . . . . . . . 5
3.2.2. Bidirectional-streams Over Synchronous HTTP (BOSH) . . 4 3.2.2. Bidirectional-streams Over Synchronous HTTP (BOSH) . . 5
4. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Motivation Scenarios . . . . . . . . . . . . . . . . . . . . . 4 5. Motivation Scenarios . . . . . . . . . . . . . . . . . . . . . 5
6. Push Delivery Framework . . . . . . . . . . . . . . . . . . . 5 6. Push Delivery Framework . . . . . . . . . . . . . . . . . . . 6
7. Discovery of Push AS . . . . . . . . . . . . . . . . . . . . . 5 7. Discovery of Push AS . . . . . . . . . . . . . . . . . . . . . 6
8. Push delivery stages . . . . . . . . . . . . . . . . . . . . . 6 8. Push delivery stages . . . . . . . . . . . . . . . . . . . . . 7
9. The "push" event package (Normative) . . . . . . . . . . . . . 6 9. The "push" event package (Normative) . . . . . . . . . . . . . 7
9.1. Event Package Definition . . . . . . . . . . . . . . . . . 7 9.1. Event Package Definition . . . . . . . . . . . . . . . . . 8
9.2. Event Package Name . . . . . . . . . . . . . . . . . . . . 7 9.2. Event Package Name . . . . . . . . . . . . . . . . . . . . 8
9.3. Event Package Parameters . . . . . . . . . . . . . . . . . 7 9.3. Event Package Parameters . . . . . . . . . . . . . . . . . 8
9.4. Event parameters . . . . . . . . . . . . . . . . . . . . . 7 9.4. Event parameters . . . . . . . . . . . . . . . . . . . . . 8
9.5. Parameters format . . . . . . . . . . . . . . . . . . . . 7 9.5. Parameters format . . . . . . . . . . . . . . . . . . . . 8
9.6. Dev-cap . . . . . . . . . . . . . . . . . . . . . . . . . 8 9.6. Dev-cap . . . . . . . . . . . . . . . . . . . . . . . . . 9
9.7. Event-app-id . . . . . . . . . . . . . . . . . . . . . . . 8 9.7. Event-app-id . . . . . . . . . . . . . . . . . . . . . . . 9
10. Push AS Processing of SUBSCRIBE Requests . . . . . . . . . . . 8 10. Push AS Processing of SUBSCRIBE Requests . . . . . . . . . . . 9
11. Push Enrollment . . . . . . . . . . . . . . . . . . . . . . . 9 11. Push Enrollment . . . . . . . . . . . . . . . . . . . . . . . 10
11.1. Initiation of a Push Enrollment . . . . . . . . . . . . . 9 11.1. Initiation of a Push Enrollment . . . . . . . . . . . . . 10
11.2. The Profile Enrollment Confirmation . . . . . . . . . . . 9 11.2. The Profile Enrollment Confirmation . . . . . . . . . . . 10
11.3. Content Push . . . . . . . . . . . . . . . . . . . . . . . 10 11.3. Content Push . . . . . . . . . . . . . . . . . . . . . . . 11
12. SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . . . . . . 10 12. SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . . . . . . 11
13. Subscription Duration . . . . . . . . . . . . . . . . . . . . 10 13. Subscription Duration . . . . . . . . . . . . . . . . . . . . 11
14. NOTIFY Bodies . . . . . . . . . . . . . . . . . . . . . . . . 10 14. NOTIFY Bodies . . . . . . . . . . . . . . . . . . . . . . . . 11
15. Deployment considerations . . . . . . . . . . . . . . . . . . 11 15. Deployment considerations . . . . . . . . . . . . . . . . . . 12
15.1. Support for NATs . . . . . . . . . . . . . . . . . . . . . 11 15.1. Support for NATs . . . . . . . . . . . . . . . . . . . . . 12
15.2. Handling of Forked Requests . . . . . . . . . . . . . . . 11 15.2. Handling of Forked Requests . . . . . . . . . . . . . . . 12
15.3. Rate of Notifications . . . . . . . . . . . . . . . . . . 11 15.3. Rate of Notifications . . . . . . . . . . . . . . . . . . 12
16. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 16. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
16.1. SIP Event Package . . . . . . . . . . . . . . . . . . . . 11 16.1. SIP Event Package . . . . . . . . . . . . . . . . . . . . 12
17. Security Considerations . . . . . . . . . . . . . . . . . . . 12 17. Security Considerations . . . . . . . . . . . . . . . . . . . 13
18. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 18. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
18.1. Normative References . . . . . . . . . . . . . . . . . . . 12 18.1. Normative References . . . . . . . . . . . . . . . . . . . 13
18.2. Informative References . . . . . . . . . . . . . . . . . . 12 18.2. Informative References . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13
Intellectual Property and Copyright Statements . . . . . . . . . . 14
1. Introduction 1. Introduction
Push service are usually based on information preference expressed in Push service are usually based on information preference expressed in
advanced, in a sort of Publish/Subscribe model. A client might advanced, in a sort of Publish/Subscribe model. A client might
"subscribe" to various information "channels". Whenever new content "subscribe" to various information "channels". Whenever new content
is available on one of those channels the server would push that is available on one of those channels the server would push that
information out of the user. Nowadays many applications depend on information out of the user. Nowadays many applications depend on
being able to get content delivered on by a an supporting network being able to get content delivered on by a an supporting network
service on a scheduled and non scheduled delivery model based on the service on a scheduled and non scheduled delivery model based on the
skipping to change at page 12, line 11 skipping to change at page 13, line 11
The following table illustrates the additions to the IANA SIP Header The following table illustrates the additions to the IANA SIP Header
Field Parameters and Parameter Values: (Note to RFC Editor: Please Field Parameters and Parameter Values: (Note to RFC Editor: Please
fill in XXXX with the RFC number of this specification) fill in XXXX with the RFC number of this specification)
Predefined Predefined
Header FieldParameter Name Values Reference Header FieldParameter Name Values Reference
---------------------------- --------------------------------- ---------------------------- ---------------------------------
Event profile-typeYes[RFCXXXX] Event profile-typeYes[RFCXXXX]
17. Security Considerations 17. Security Considerations
The security considerations listed in The security considerations listed in SIP events [RFC3265], which the
[I-D.ietf-sipping-config-framework] apply in entirety. Push mechanism extends, apply in entirety. In particular,
authentication and message integrity SHOULD be applied to
subscriptions with the Push extension.
18. References 18. References
18.1. Normative References 18.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.
[RFC2234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [RFC2234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997. Specifications: ABNF", RFC 2234, November 1997.
skipping to change at page 13, line 16 skipping to change at page 14, line 16
Martin Dolly Martin Dolly
AT&T AT&T
200 Laurel Ave 200 Laurel Ave
Middletown, NJ, Middletown, NJ,
US US
Phone: Phone:
Email: mdolly@att.com Email: mdolly@att.com
Kent Bogestam
Ericsson
Kistavaegen 27
Stockholm 164 80
Sweden
Email: kent.bogestam@ericsson.com
Salvatore Loreto Salvatore Loreto
Ericsson Ericsson
Hirsalantie 11 Hirsalantie 11
Jorvas 02420 Jorvas 02420
Finland Finland
Email: salvatore.loreto@ericsson.com Email: salvatore.loreto@ericsson.com
Full Copyright Statement Kent Bogestam
Sweden
Copyright (C) The IETF Trust (2008).
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.
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, THE IETF TRUST 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.
Intellectual Property
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 Email: kent.bogestam@cumbari.com
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.
 End of changes. 10 change blocks. 
102 lines changed or deleted 73 lines changed or added

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