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

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 27 May 2009 15:03 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: dispatch@core3.amsl.com
Delivered-To: dispatch@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BCD4C3A6892 for <dispatch@core3.amsl.com>; Wed, 27 May 2009 08:03:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.459
X-Spam-Level:
X-Spam-Status: No, score=-3.459 tagged_above=-999 required=5 tests=[AWL=0.140, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 Ocl4cIqdxCj8 for <dispatch@core3.amsl.com>; Wed, 27 May 2009 08:03:40 -0700 (PDT)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id D7EC03A68F6 for <dispatch@ietf.org>; Wed, 27 May 2009 08:03:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id C04044303B6 for <dispatch@ietf.org>; Wed, 27 May 2009 08:05:01 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.100] (pool-71-161-52-172.clppva.btas.verizon.net [71.161.52.172]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTP id 307E0430380 for <dispatch@ietf.org>; Wed, 27 May 2009 08:05:01 -0700 (PDT)
Message-ID: <4A1D569B.3040401@joelhalpern.com>
Date: Wed, 27 May 2009 11:04:59 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: dispatch@ietf.org
References: <CA9998CD4A020D418654FCDEF4E707DF0D234264@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF0D234264@esealmw113.eemea.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [dispatch] Draft: CBUS (Condition-based URI Subscription) requirements draft - draft-holmberg-dispatch-cbus-00.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 May 2009 15:03:44 -0000

Reading this draft, I am wondering if this actually has anything to do 
with SIP?  (Other than the fact that OMA chose to work on it, and 
decided SIP was the right solution space.)

It appears that the client is looking for some "servers" (which may be 
people) which meet certain constraints.  I am as likely to want xmpp: 
URIs, or even HTTP: URIs, as SIP: URIs (should I say TEL:?) for the 
cases that I can imagine based on the example in the draft.

This seems an interesting general application.  Unless we really want to 
turn SIP into the next HTTP: (REST over HTTP as a general application 
infrastructure), I am slightly confused.

Yours,
Joel

Christer Holmberg wrote:
> 
> 
> Hi,
> 
> I've submitted a draft which proposes SIP requirements for CBUS, based 
> on work ongoing in OMA.
> 
> (The most likely protocol output is going to be a new event package, and 
> some mechanism to provide conditions to the CBUS server).
> 
> The document can also be found in:
> 
> http://users.piuha.net/cholmber/drafts/draft-holmberg-dispatch-cbus-00.txt 
> <http://users.piuha.net/cholmber/drafts/draft-holmberg-dispatch-cbus-00.txt> 
> 
> 
> Regards,
> 
> Christer
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch