Browse Prior Art Database

A SIP Event Package for Subscribing to Changes to an HTTP Resource (RFC5989)

IP.com Disclosure Number: IPCOM000200900D
Original Publication Date: 2010-Oct-01
Included in the Prior Art Database: 2010-Oct-30
Document File: 38 page(s) / 41K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A.B. Roach: AUTHOR

Abstract

The Session Initiation Protocol (SIP) [3] is increasingly being used in systems that are tightly coupled with Hypertext Transport Protocol (HTTP) [2] servers for a variety of reasons. In many of these cases, applications can benefit from learning of changes to specified HTTP resources in near real-time. For example, user agent terminals may elect to store service-related data in an HTTP tree. When such configuration information is stored and retrieved using HTTP, clients may need to be informed when information changes, so as to make appropriate changes to their local behavior and user interface.

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

Internet Engineering Task Force (IETF)                        A.B. Roach Request for Comments: 5989                                       Tekelec Category: Standards Track                                   October 2010 ISSN: 2070-1721

    A SIP Event Package for Subscribing to Changes to an HTTP Resource

Abstract

   The Session Initiation Protocol (SIP) is increasingly being used in    systems that are tightly coupled with Hypertext Transport Protocol    (HTTP) servers for a variety of reasons.  In many of these cases,    applications can benefit from being able to discover, in near real-    time, when a specific HTTP resource is created, changed, or deleted.    This document proposes a mechanism, based on the SIP Event Framework,    for doing so.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc5989.

Copyright Notice

   Copyright (c) 2010 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    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

Roach                        Standards Track                    [Page 1]
 RFC 5989                 SIP HTTP Subscriptions             October 2010

 Table of Contents

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

   2. Terminology .....................................................3

   3. Associating Monitoring SIP URIs with HTTP URLs ..................3

      3.1. Monitoring a Single HTTP Resource ..........................4

      3.2. Monitoring Multiple HTTP Resources .........................5

   4. HTTP Change Event Package .......................................6

      4.1. Event Package Name .........................................6

      4.2....