[sip-http-events] Fwd: Protocol Action: 'A SIP Event Package for Subscribing to Changes to an HTTP Resource' to Proposed Standard

Adam Roach <adam@nostrum.com> Mon, 08 February 2010 19:05 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: sip-http-events@core3.amsl.com
Delivered-To: sip-http-events@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id BEB433A7257 for <sip-http-events@core3.amsl.com>; Mon, 8 Feb 2010 11:05:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id cte-wls81Aps for <sip-http-events@core3.amsl.com>; Mon, 8 Feb 2010 11:05:50 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 251DC3A725F for <sip-http-events@ietf.org>; Mon, 8 Feb 2010 11:05:49 -0800 (PST)
Received: from [] (vicuna-alt.estacado.net []) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o18J6pUW022440 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <sip-http-events@ietf.org>; Mon, 8 Feb 2010 13:06:51 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <4B7060CB.4020105@nostrum.com>
Date: Mon, 08 Feb 2010 13:06:51 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv: Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: SIP HTTP Subscription Package <sip-http-events@ietf.org>
Content-Type: multipart/alternative; boundary="------------010005020400080807010307"
Received-SPF: pass (nostrum.com: is authenticated by a trusted mechanism)
Subject: [sip-http-events] Fwd: Protocol Action: 'A SIP Event Package for Subscribing to Changes to an HTTP Resource' to Proposed Standard
X-BeenThere: sip-http-events@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP HTTP Events <sip-http-events.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip-http-events>, <mailto:sip-http-events-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-http-events>
List-Post: <mailto:sip-http-events@ietf.org>
List-Help: <mailto:sip-http-events-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-http-events>, <mailto:sip-http-events-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2010 19:05:51 -0000


The IESG has approved the SIP HTTP Subscription Package for publication. 
It should appear in the RFC Editor's Queue shortly.


-------- Original Message --------
Subject: 	Protocol Action: 'A SIP Event Package for Subscribing to 
Changes to an HTTP Resource' to Proposed Standard
Date: 	Mon, 8 Feb 2010 09:11:04 -0800 (PST)
From: 	The IESG <iesg-secretary@ietf.org>
To: 	IETF-Announce <ietf-announce@ietf.org>
CC: 	Internet Architecture Board <iab@iab.org>rg>, RFC Editor 

The IESG has approved the following document:

- 'A SIP Event Package for Subscribing to Changes to an HTTP Resource '
    <draft-roach-sip-http-subscribe-07.txt>  as a Proposed Standard

This document has been reviewed in the IETF but is not the product of an
IETF Working Group.

The IESG contact person is Alexey Melnikov.

A URL of this Internet-Draft is:

Technical Summary

    This document defines a mechanism whereby the Session Initiation
    Protocol (SIP) Event Framework can be used to provide notification
    of changes to the state of resources available through the
    Hypertext Transport Protocol (HTTP).  This facilitates the
    development of applications that provide near real time updates to
    information through HTTP without frequent polling or continuously
    open transport connections.

Working Group Summary

    This is not a Working Group document - it is an individual
    submission, but has received review from participants active in the
    SIP and HTTP communities.  Based on discussion on the DISPATCH
    working group list during the summer of 2009, a consensus was
    reached that it was close enough to complete that a Working Group
    was not needed, but a separate list [1] was created to complete the

Document Quality

    There is not yet significant implementation of this protocol, but
    it has been incorporated as a key component in the SIP Forum User
    Agent Configuration Recommendation (currently in SIP Forum Last
    Call); a number of implementations of that recommendation are
    believed to be in progress.



    Scott Lawrence<scottlawrenc@avaya.com>  is the Document Shepherd.
    Alexey Melnikov is the Responsible Area Director.

IETF-Announce mailing list