IETF Logo Mail Archive

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

"Scott Lawrence" <scott.lawrence@nortel.com> Wed, 27 May 2009 18:18 UTC

Return-Path: <scott.lawrence@nortel.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 C4EFC3A7151 for <dispatch@core3.amsl.com>; Wed, 27 May 2009 11:18:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.171
X-Spam-Level:
X-Spam-Status: No, score=-6.171 tagged_above=-999 required=5 tests=[AWL=0.428, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 OC1vCHB2WAmf for <dispatch@core3.amsl.com>; Wed, 27 May 2009 11:18:14 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id 40FB728C1B8 for <dispatch@ietf.org>; Wed, 27 May 2009 11:16:37 -0700 (PDT)
Received: from zrtphxs1.corp.nortel.com (casmtp.ca.nortel.com [47.140.202.46]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id n4RIGtS13161; Wed, 27 May 2009 18:16:56 GMT
Received: from [127.0.0.1] ([47.17.25.99]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 27 May 2009 14:18:04 -0400
From: Scott Lawrence <scott.lawrence@nortel.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF0D234264@esealmw113.eemea.ericsson.se>
References: <CA9998CD4A020D418654FCDEF4E707DF0D234264@esealmw113.eemea.ericsson.se>
Content-Type: text/plain
Organization: Nortel Networks
Date: Wed, 27 May 2009 14:18:03 -0400
Message-Id: <1243448283.13614.283.camel@host.home.skrb.org>
Mime-Version: 1.0
X-Mailer: Evolution 2.24.5 (2.24.5-1.fc10)
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 May 2009 18:18:04.0421 (UTC) FILETIME=[7A239350:01C9DEF7]
Cc: dispatch@ietf.org
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 18:18:14 -0000

On Wed, 2009-05-27 at 14:45 +0200, Christer Holmberg wrote:

> 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 would have been significantly easier to understand had it
actually defined some of the several acronyms it used.

As far as I can tell, this describes (in very very general terms) a
framework for a particular application.  I don't see anything here that
motivates any new feature in the SIP protocol, or indeed any reason why
SIP is especially well suited to the application.

v2.23.0 | Report a Bug | By Email