Message-ID: <4B0DA1E3.4070304@nostrum.com>
Date: Wed, 25 Nov 2009 15:30:11 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
 rv:1.9.1.5) Gecko/20091121 Thunderbird/3.0
MIME-Version: 1.0
To: SIP HTTP Subscription Package <sip-http-events@ietf.org>
References: <4B0AC057.5040703@nostrum.com>
In-Reply-To: <4B0AC057.5040703@nostrum.com>
Content-Type: multipart/alternative;
 boundary="------------080502080707010406020805"
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
 mechanism)
Subject: Re: [sip-http-events] HTTP Subscribe: Remaining Open Issue
Precedence: list

This is a multi-part message in MIME format.
--------------080502080707010406020805
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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.

/a

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:
>
> http://tools.ietf.org/html/draft-roach-sip-http-subscribe-02
>
> /a
>
>
> _______________________________________________
> sip-http-events mailing list
> sip-http-events@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-http-events
>    


--------------080502080707010406020805
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
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.<br>
<br>
/a<br>
<br>
On 11/23/09 11:03 AM, Adam Roach wrote:
<blockquote cite="mid:4B0AC057.5040703@nostrum.com" type="cite">
  <meta http-equiv="content-type"
 content="text/html; charset=ISO-8859-1">
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.<br>
  <br>
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:<br>
  <meta http-equiv="content-type"
 content="text/html; charset=ISO-8859-1">
  <pre class="newpage">   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.

  </pre>
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).<br>
  <br>
If you have an opinion one way or another about this topic, please post
is to the list.<br>
  <br>
The current version of the document is here:<br>
  <br>
  <a moz-do-not-send="true" class="moz-txt-link-freetext"
 href="http://tools.ietf.org/html/draft-roach-sip-http-subscribe-02">http://tools.ietf.org/html/draft-roach-sip-http-subscribe-02</a><br>
  <br>
/a<br>
  <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
sip-http-events mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sip-http-events@ietf.org">sip-http-events@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/sip-http-events">https://www.ietf.org/mailman/listinfo/sip-http-events</a>
  </pre>
</blockquote>
<br>
</body>
</html>

--------------080502080707010406020805--