[SIP] draft-roach-sip-acb, draft-roach-sip-subscribe
S_S_Dinesh/India/IBM@au1.ibm.com Mon, 08 May 2000 18:48 UTC
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15112 for <sip-archive@odin.ietf.org>; Mon, 8 May 2000 14:48:04 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 431D24436B; Mon, 8 May 2000 14:40:05 -0400 (EDT)
Delivered-To: sip@share.research.bell-labs.com
Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49]) by lists.bell-labs.com (Postfix) with SMTP id A0BE044365 for <sip@share.research.bell-labs.com>; Mon, 8 May 2000 14:39:58 -0400 (EDT)
Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Mon May 8 14:45:58 EDT 2000
Received: by lists.bell-labs.com (Postfix) id 9AAEE4434A; Mon, 8 May 2000 14:19:40 -0400 (EDT)
Delivered-To: sip@lists.bell-labs.com
Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by lists.bell-labs.com (Postfix) with ESMTP id 3FC2B44348 for <sip@lists.bell-labs.com>; Mon, 8 May 2000 14:19:40 -0400 (EDT)
Received: by lists.research.bell-labs.com (Postfix) id 3635552D4; Mon, 8 May 2000 14:19:38 -0400 (EDT)
Delivered-To: sip@lists.research.bell-labs.com
Received: from chair.dnrc.bell-labs.com (chair [135.180.161.201]) by lists.research.bell-labs.com (Postfix) with ESMTP id 680A852C8 for <sip@lists.research.bell-labs.com>; Mon, 8 May 2000 14:19:26 -0400 (EDT)
Received: from scummy.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.10] (may be forged)) by chair.dnrc.bell-labs.com (8.9.3/8.9.3) with SMTP id IAA20323 for <sip@lists.research.bell-labs.com>; Mon, 8 May 2000 08:07:51 -0400 (EDT)
From: S_S_Dinesh/India/IBM@au1.ibm.com
Received: from dusty.research.bell-labs.com ([135.104.2.7]) by scummy; Mon May 8 07:58:36 EDT 2000
Received: from ausmtp01.au.ibm.com ([202.135.136.97]) by dusty; Mon May 8 07:58:34 EDT 2000
Received: from f03n05e.au.ibm.com by ausmtp01.au.ibm.com (IBM AP 1.0) with ESMTP id VAA242262; Mon, 8 May 2000 21:53:09 +1000
Received: from d73mta05.au.ibm.com (f06n05s [9.185.166.67]) by f03n05e.au.ibm.com (8.8.8m2/8.8.7) with SMTP id VAA31400; Mon, 8 May 2000 21:58:26 +1000
Received: by d73mta05.au.ibm.com(Lotus SMTP MTA v4.6.5 (863.2 5-20-1999)) id CA2568D9.0041C43F ; Mon, 8 May 2000 21:58:20 +1000
X-Lotus-FromDomain: IBMAU@IBMIN@IBMAU
To: adam.roach@ericsson.com, sip@lists.research.bell-labs.com
Message-ID: <CA2568D9.0041C1C4.00@d73mta05.au.ibm.com>
Date: Mon, 08 May 2000 14:10:24 +0530
Mime-Version: 1.0
Content-type: text/plain; charset="us-ascii"
Content-Disposition: inline
Subject: [SIP] draft-roach-sip-acb, draft-roach-sip-subscribe
Sender: sip-admin@lists.bell-labs.com
Errors-To: sip-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id: IETF SIP Mailing List <sip.lists.bell-labs.com>
X-BeenThere: sip@lists.bell-labs.com
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 _______________________________________________ SIP mailing list SIP@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/sip
- [SIP] draft-roach-sip-acb, draft-roach-sip-subscr… S_S_Dinesh/India/IBM
- draft-roach-sip-acb, draft-roach-sip-subscribe Henning Schulzrinne