RFC 5839 on An Extension to Session Initiation Protocol (SIP) Events for Conditional Event Notification
rfc-editor@rfc-editor.org Thu, 06 May 2010 00:53 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 396A828C19C; Wed, 5 May 2010 17:53:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.717
X-Spam-Level:
X-Spam-Status: No, score=-0.717 tagged_above=-999 required=5 tests=[AWL=-1.131, BAYES_40=-0.185, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FXPw1qwGbCjm; Wed, 5 May 2010 17:53:53 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 7A09B28C161; Wed, 5 May 2010 17:53:53 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D4E92E067F; Wed, 5 May 2010 17:53:40 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5839 on An Extension to Session Initiation Protocol (SIP) Events for Conditional Event Notification
From: rfc-editor@rfc-editor.org
Message-Id: <20100506005340.D4E92E067F@rfc-editor.org>
Date: Wed, 05 May 2010 17:53:40 -0700
Cc: sipcore@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 May 2010 00:53:54 -0000
A new Request for Comments is now available in online RFC libraries. RFC 5839 Title: An Extension to Session Initiation Protocol (SIP) Events for Conditional Event Notification Author: A. Niemi, D. Willis, Ed. Status: Standards Track Stream: IETF Date: May 2010 Mailbox: aki.niemi@nokia.com, dean.willis@softarmor.com Pages: 25 Characters: 52999 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-sipcore-subnot-etags-04.txt URL: http://www.rfc-editor.org/rfc/rfc5839.txt The Session Initiation Protocol (SIP) events framework enables receiving asynchronous notification of various events from other SIP user agents. This framework defines the procedures for creating, refreshing, and terminating subscriptions, as well as fetching and periodic polling of resource state. These procedures provide no tools to avoid replaying event notifications that have already been received by a user agent. This memo defines an extension to SIP events that allows the subscriber to condition the subscription request to whether the state has changed since the previous notification was received. When such a condition is true, either the body of a resulting event notification or the entire notification message is suppressed. [STANDARDS TRACK] This document is a product of the Session Initiation Protocol Core Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: 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. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC