Browse Prior Art Database

A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP) (RFC3857)

IP.com Disclosure Number: IPCOM000030839D
Original Publication Date: 2004-Aug-01
Included in the Prior Art Database: 2019-Feb-11
Document File: 20 page(s) / 29K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Rosenberg: AUTHOR

Related Documents

10.17487/RFC3857: DOI

Abstract

This document defines the watcher information template-package for the Session Initiation Protocol (SIP) event framework. Watcher information refers to the set of users subscribed to a particular resource within a particular event package. Watcher information changes dynamically as users subscribe, unsubscribe, are approved, or are rejected. A user can subscribe to this information, and therefore learn about changes to it. This event package is a template-package because it can be applied to any event package, including itself. [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 8% of the total text.

Network Working Group J. Rosenberg Request for Comments: 3857 dynamicsoft Category: Standards Track August 2004

A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP)

Status of this Memo

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2004).

Abstract

This document defines the watcher information template-package for the Session Initiation Protocol (SIP) event framework. Watcher information refers to the set of users subscribed to a particular resource within a particular event package. Watcher information changes dynamically as users subscribe, unsubscribe, are approved, or are rejected. A user can subscribe to this information, and therefore learn about changes to it. This event package is a template-package because it can be applied to any event package, including itself.

Rosenberg Standards Track [Page 1]

RFC 3857 Watcher Information August 2004

Table of Contents

1. Introduction ........................................ 2 2. Terminology ......................................... 3 3. Usage Scenarios ..................................... 3 3.1. Presence Authorization ........................ 4 3.2. Blacklist Alerts .............................. 5 4. Package Definition .................................. 5 4.1. Event Package Name ............................ 5 4.2. Event Package Parameters ...................... 5 4.3. SUBSCRIBE Bodies .............................. 6 4.4. Subscription Duration ......................... 6 4.5. NOTIFY Bodies ................................. 7 4.6. Notifier Processing of SUBSCRIBE Requests...... 7 4.7. Notifier Generation of NOTIFY Requests ........ 8 4.7.1. The Subscription State Machine......... 9 4.7.2. Applying the State Machine............. 11 4.8. Subscriber Processing of NOTIFY Requests ...... 12 4.9. Handling of Forked Requests ................... 12 4.10. Rate of Notifications ......................... 13 4.11. State Agents .................................. 13 5. Example Usage ....................................... 14 6. Security Considerations ............................. 17 6.1. Denial of Service Attacks ..................... 17 6.2. Divulging Sensitive Information ............... 17 7. IANA Considerations ................................. 18 8. Acknowledgements .................................... 18 9. Normative References ................................ 18 10. Informative References .............................. 19 11. Author’s Address .................................... 19 12. Full Copyright Statement ............................ 20

1. Introduction

The Session Initiation Protocol (SIP) event framework is described in RFC 326...

Processing...
Loading...