Re: [dispatch] Draft: CBUS (Condition-based URI Subscription) requirements draft - draft-holmberg-dispatch-cbus-00.txt

["Scott Lawrence" <[e-mail]>]

On Thu, 2009-05-28 at 08:53 +0200, Christer Holmberg wrote:
> 
> So, the idea is to use the existing SIP SUB/NOT mechanism. The only
> "new" thing is to provide the conditions as part of the subscription.

What's new about that?  The target of a SUBSCRIBE is a URI, which can
include parameters.  Putting a body on a SUBSCRIBE request that further
extends those parameters is already allowed (eg RFC 5367), and a server
is free to use any part of a SUBSCRIBE request to determine whether or
not to create a subscription and what data to send in the resulting
NOTIFY messages.

Neither defining an event package for a particular application (which is
what this appears to be), nor defining how to communicate parameters in
the requests used by that application require any change to the
protocol.

While I'm sure this is interesting work, I don't see any reason why it
should consume IETF working group time - you'd spend almost all the time
educating other participants about the application requirements.  

I'd say go ahead and develop what you need, and if you think it would be
useful to publish the results as an Informational document there's no
reason not to do so as an individual submission.

Of course, if you find some prohibition or constraint in the existing
specifications that you think needs modifying, then that would be worth
IETF review.