IETF Logo Mail Archive

draft-roach-sip-acb, draft-roach-sip-subscribe

Henning Schulzrinne <schulzrinne@cs.columbia.edu> Wed, 08 March 2000 14:41 UTC

Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02082 for <sip-archive@odin.ietf.org>; Wed, 8 Mar 2000 09:41:59 -0500 (EST)
Received: by lists.research.bell-labs.com (Postfix) id DDCA252BB; Wed, 8 Mar 2000 09:39:22 -0500 (EST)
Delivered-To: sip-outgoing-local@paperless.dnrc.bell-labs.com
Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id 6462D52C4; Wed, 8 Mar 2000 09:39:22 -0500 (EST)
Delivered-To: sip-local@paperless.dnrc.bell-labs.com
Received: from scummy.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.10]) by lists.research.bell-labs.com (Postfix) with SMTP id DB6A152BB for <sip@lists.research.bell-labs.com>; Wed, 8 Mar 2000 09:39:06 -0500 (EST)
Received: from dusty.research.bell-labs.com ([135.104.2.7]) by scummy; Wed Mar 8 09:38:25 EST 2000
Received: from cs.columbia.edu ([128.59.16.20]) by dusty; Wed Mar 8 09:35:49 EST 2000
Received: from cs.columbia.edu (bart.cs.columbia.edu [128.59.19.191]) by cs.columbia.edu (8.9.1/8.9.1) with ESMTP id JAA01352; Wed, 8 Mar 2000 09:38:22 -0500 (EST)
Message-ID: <38C665DB.3C8622BF@cs.columbia.edu>
Date: Wed, 08 Mar 2000 09:38:19 -0500
From: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Organization: Columbia University, Dept. of Computer Science
X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: adam.roach@ericsson.com, sip@lists.research.bell-labs.com
Subject: draft-roach-sip-acb, draft-roach-sip-subscribe
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-sip@lists.research.bell-labs.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Some quick comments:

- It would be nice to align the event notification as much as possible
with PINT, since PINT is intended as a SIP profile. If their model is
broken, it needs to be fixed. (It may well may sense to extract the
event mechanism from PINT and have a common draft.)

- Expires: It might be cleaner to structure this similar to the Contact
mechanism in REGISTER. This also makes it possible to perform several
actions atomically. Something like

Event: waterboiling ;expires=3600 , dinnerdone;expires=7200

(I'm not sure that putting this is in the header is necessarily the best
solution, but that's a separate discussion.)
-- 
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs

v2.23.0 | Report a Bug | By Email