[Sip] non-SUBSCRIBE mechanisms for Event Notification

"Lessing, FrancoisX" <francoisx.lessing@intel.com> Wed, 12 September 2001 16:52 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27590 for <sip-archive@odin.ietf.org>; Wed, 12 Sep 2001 12:52:52 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA02421; Wed, 12 Sep 2001 12:30:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA02393 for <sip@optimus.ietf.org>; Wed, 12 Sep 2001 12:30:35 -0400 (EDT)
Received: from ganymede.or.intel.com (jffdns01.or.intel.com [134.134.248.3]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26966 for <sip@ietf.org>; Wed, 12 Sep 2001 12:30:04 -0400 (EDT)
Received: from SMTP (orsmsxvs02-1.jf.intel.com [192.168.65.201]) by ganymede.or.intel.com (8.9.1a+p1/8.9.1/d: relay.m4, v 1.42 2001/09/04 16:24:19 root Exp $) with SMTP id QAA29354 for <sip@ietf.org>; Wed, 12 Sep 2001 16:29:37 GMT
Received: from orsmsx26.jf.intel.com ([192.168.70.26]) by 192.168.70.201 (Norton AntiVirus for Internet Email Gateways 1.0) ; Wed, 12 Sep 2001 16:29:37 0000 (GMT)
Received: from SMTP (orsmsxvs01-1.jf.intel.com [192.168.65.200]) by orsmsx26.jf.intel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id SYGS7TNS; Wed, 12 Sep 2001 09:29:36 -0700
Received: from intel.com ([10.242.97.86]) by 192.168.65.200 (Norton AntiVirus for Internet Email Gateways 1.0) ; Wed, 12 Sep 2001 16:29:35 0000 (GMT)
Message-ID: <3B9F8D6D.4E989C69@intel.com>
Date: Wed, 12 Sep 2001 09:29:34 -0700
From: "Lessing, FrancoisX" <francoisx.lessing@intel.com>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: SIP mailing list <sip@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sip] non-SUBSCRIBE mechanisms for Event Notification
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Session Initiation Protocol <sip.ietf.org>
X-BeenThere: sip@ietf.org
Content-Transfer-Encoding: 7bit

Hi,

The subscribe-notify draft RFC allows for alternate mechanisms to
"register" a subscription
at SIP nodes. I understand that an example of this is the REFER method,
where the
REFER effectively is used to create a subscription.

Are there other examples where this flexibility would be useful ?

Francois Lessing






_______________________________________________
Sip mailing list  http://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip