Browse Prior Art Database

Session Initiation Protocol (SIP)-Specific Event Notification (RFC3265)

IP.com Disclosure Number: IPCOM000009210D
Original Publication Date: 2002-Jun-01
Included in the Prior Art Database: 2002-Aug-13
Document File: 39 page(s) / 89K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. B. Roach: AUTHOR

Abstract

This document describes an extension to the Session Initiation Protocol (SIP). The purpose of this extension is to provide an extensible framework by which SIP nodes can request notification from remote nodes indicating that certain events have occurred.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 3% of the total text.

Network Working Group� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � A. B. Roach

Request for Comments: 3265� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � dynamicsoft

Updates: 2543� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � June 2002

Category: Standards Track

� � � � Session Initiation Protocol (SIP)-Specific Event Notification

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 (2002).� All Rights Reserved.

Abstract

� � This document describes an extension to the Session Initiation

� � Protocol (SIP).� The purpose of this extension is to provide an

� � extensible framework by which SIP nodes can request notification from

� � remote nodes indicating that certain events have occurred.

� � Concrete uses of the mechanism described in this document may be

� � standardized in the future.

� � Note that the event notification mechanisms defined herein are NOT

� � intended to be a general-purpose infrastructure for all classes of

� � event subscription and notification.

Table of Contents

� � 1.� � � � � � Introduction...........................................� 3

� � 1.1.� � � � Overview of Operation..................................� 4

� � 1.2.� � � � Documentation Conventions..............................� 4

� � 2.� � � � � � Definitions............................................� 5

� � 3.� � � � � � Node Behavior..........................................� 6

� � 3.1.� � � � Description of SUBSCRIBE Behavior......................� 6

� � 3.1.1.� � Subscription Duration..................................� 6

� � 3.1.2.� � Identification of Subscribed Events and Event Classes..� 6

� � 3.1.3.� � Additional SUBSCRIBE Header Values..................... � 7

� � 3.1.4.� � Subscriber SUBSCRIBE Behavior..........................� 7

� � 3.1.5.� � Proxy SUBSCRIBE Behavior...............................� 9

� � 3.1.6.� � Notifier SUBSCRIBE Behavior............................ 10

Roach� � � � � � � � � � � � � � � � � � � � � � Standards Track� � � � � � � � � � � � � � � � � � � � [Page 1]

RFC 3265� � � � � � � � � � � SIP-Specific Event Notification� � � � � � � � � � � June 2002

� � 3.2.� � � � Description of NOTIFY Behavior......................... 13

� � 3.2.1.� � Identification of Reported Events, Event Classes, and

� � � � � � � � � � � Current State.......................................... 13

� � 3.2.2.� � Notifier NOTIFY Behavior............................... 14

� � 3.2.3.� � Proxy NOTIFY Behavior.................................. 15

� � 3.2.4.� � Subscriber NOTIFY Behavior.......