Re: [sip-http-events] HTTP Subscribe: Remaining Open Issue

Adam Roach <> Wed, 25 November 2009 21:30 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 627F43A6B54 for <>; Wed, 25 Nov 2009 13:30:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.266
X-Spam-Status: No, score=-3.266 tagged_above=-999 required=5 tests=[AWL=-0.667, BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id bDIcOtM6xKxY for <>; Wed, 25 Nov 2009 13:30:19 -0800 (PST)
Received: from ( [IPv6:2001:470:1f03:267::2]) by (Postfix) with ESMTP id E82B23A6820 for <>; Wed, 25 Nov 2009 13:30:18 -0800 (PST)
Received: from [] ( []) (authenticated bits=0) by (8.14.3/8.14.3) with ESMTP id nAPLUBR1019337 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <>; Wed, 25 Nov 2009 15:30:11 -0600 (CST) (envelope-from
Message-ID: <>
Date: Wed, 25 Nov 2009 15:30:11 -0600
From: Adam Roach <>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv: Gecko/20091121 Thunderbird/3.0
MIME-Version: 1.0
To: SIP HTTP Subscription Package <>
References: <>
In-Reply-To: <>
Content-Type: multipart/alternative; boundary="------------080502080707010406020805"
Received-SPF: pass ( is authenticated by a trusted mechanism)
Subject: Re: [sip-http-events] HTTP Subscribe: Remaining Open Issue
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP HTTP Events <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 25 Nov 2009 21:30:20 -0000

Based on the feedback so far (thanks for replying so quickly!) it 
certainly seems like there is significant support for adding the ability 
to request inclusion of bodies in the NOTIFY messages. The -03 version 
of the document has incorporated this feature.


On 11/23/09 11:03 AM, Adam Roach wrote:
> There has been increasing interest in having a finalized version of 
> draft-roach-sip-http-subscribe ready for publication. I have a couple 
> of open items myself (mostly, generation of example messages), but 
> there is one open item called out in the draft at the moment. I expect 
> to take care of these in the near future, and request publication as 
> soon as feasible.
> Currently, the package mentions that notifications of HTTP resource 
> state changes don't include the actual resource state -- although it 
> leaves open the possibility that someone may define an extension to do 
> so in the future; the relevant text is:
>     When used in the HTTP monitor event package, the message/http MUST
>     NOT contain a message-body component, unless the corresponding
>     subscription has explicitly indicated the desire to receive such
>     bodies in the form of a filter.  Filters for this event package are
>     out of scope for this specification.
> In section 3.2, we ask whether this document should define a simple 
> filter parameter (e.g., "body=true") that would request that event 
> state changes include the new resource state. I *suspect* this would 
> be a very straightforward thing to define, and it may be quite useful 
> for certain usages (e.g., some of the proposed BLISS applications have 
> very, very small documents -- on the order of 4 to 40 characters or 
> so), as it would save the HTTP round-trip. On the other hand, the 
> prospect of pushing large HTTP documents through the SIP network may 
> prove problematic. (If we define this mechanism, I would definitely 
> propose that including this in a SUBSCRIBE is simply a request, and 
> give the server the option of declining to honor it).
> If you have an opinion one way or another about this topic, please 
> post is to the list.
> The current version of the document is here:
> /a
> _______________________________________________
> sip-http-events mailing list