Browse Prior Art Database

Session Initiation Protocol (SIP) Extension for Event State Publication (RFC3903)

IP.com Disclosure Number: IPCOM000032314D
Original Publication Date: 2004-Oct-01
Included in the Prior Art Database: 2004-Oct-30
Document File: 33 page(s) / 72K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Niemi: AUTHOR [+2]

Abstract

This document describes an extension to the Session Initiation Protocol (SIP) for publishing event state used within the SIP Events framework. The first application of this extension is for the publication of presence information.

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

Network Working Group                                      A. Niemi, Ed.

Request for Comments: 3903                                         Nokia

Category: Standards Track                                   October 2004

              Session Initiation Protocol (SIP) Extension

                      for Event State Publication

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 describes an extension to the Session Initiation

   Protocol (SIP) for publishing event state used within the SIP Events

   framework.  The first application of this extension is for the

   publication of presence information.

   The mechanism described in this document can be extended to support

   publication of any event state for which there exists an appropriate

   event package.  It is not intended to be a general-purpose mechanism

   for transport of arbitrary data, as there are better-suited

   mechanisms for this purpose.

Table of Contents

   1.   Introduction . . . . . . . . . . . . . . . . . . . . . . . .   2

   2.   Definitions and Document Conventions . . . . . . . . . . . .   3

   3.   Overall Operation  . . . . . . . . . . . . . . . . . . . . .   4

   4.   Constructing PUBLISH Requests  . . . . . . . . . . . . . . .   5

        4.1.  Identification of Published Event State. . . . . . . .   6

        4.2.  Creating Initial Publication . . . . . . . . . . . . .   7

        4.3.  Refreshing Event State . . . . . . . . . . . . . . . .   8

        4.4.  Modifying Event State  . . . . . . . . . . . . . . . .   9

        4.5.  Removing Event State . . . . . . . . . . . . . . . . .   9

   5.   Processing PUBLISH Responses . . . . . . . . . . . . . . . .  10

   6.   Processing PUBLISH Requests  . . . . . . . . . . . . . . . .  10

   7.   Processing OPTIONS Requests  . . . . . . . . . . . . . . . .  13

   8.   Use of Entity-tags in PUBLISH  . . . . . . . . . . . . . . .  13

Niemi                       Standards Track                     [Page 1]

RFC 3903              SIP Event State Publication           October 2004

        8.1.  General Notes. . . . . . . . . . . . . . . . . . . . .  13

        8.2.  Client Usage . . . . . . . . . . . . . . . . . . . . .  14

        8.3.  Server Usage . . . . . . ....