Re: [Sip] FW: New Draft - Suppression of Refer Implicit Subscription
Rohan Mahy <rohan@cisco.com> Tue, 29 October 2002 05:27 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11529 for <sip-archive@odin.ietf.org>; Tue, 29 Oct 2002 00:27:22 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9T5TNx09677 for sip-archive@odin.ietf.org; Tue, 29 Oct 2002 00:29:23 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T5Suv09589; Tue, 29 Oct 2002 00:28:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T5KXv09227 for <sip@optimus.ietf.org>; Tue, 29 Oct 2002 00:20:33 -0500
Received: from sj-msg-core-4.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11166 for <sip@ietf.org>; Tue, 29 Oct 2002 00:18:01 -0500 (EST)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44]) by sj-msg-core-4.cisco.com (8.12.2/8.12.2) with ESMTP id g9T5KLot011654; Mon, 28 Oct 2002 21:20:21 -0800 (PST)
Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134]) by imop.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA) with ESMTP id ABF27849; Mon, 28 Oct 2002 21:17:54 -0800 (PST)
Date: Mon, 28 Oct 2002 21:20:55 -0800
Subject: Re: [Sip] FW: New Draft - Suppression of Refer Implicit Subscription
Content-Type: text/plain; delsp="yes"; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v546)
Cc: sip@ietf.org
To: Sriram Parameswar <sriramkp@attbi.com>
From: Rohan Mahy <rohan@cisco.com>
In-Reply-To: <KEELKLOEMJCHGFFFAINJIECECAAA.sriramkp@attbi.com>
Message-Id: <335C21B4-EAFE-11D6-925C-0003938AF740@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Hi, So you are just trading a pair of messages (NOTIFY/481) for an option tag in the REFER? It doesn't seem that compelling to me personally. It certainly doesn't follow the generality over efficiency argument. Can you elaborate a bit more on your motivations? The transfer draft recommends waiting for NOTIFY for attended transfer for robustness, so I'm not convinced there. As for the "push content" model, I envisioned an immediate fetch, with a NOTIFY to deliver the status of that fetch. thanks, -rohan On Monday, October 28, 2002, at 01:00 AM, Sriram Parameswar wrote: > Hi All, > > I have submitted a draft (to SIPPING) that examines the requirements > and one > _potential_ mechanism to suppress the implicit subscription created by > the > REFER method. > > Till it appears in the IETF site - please pick up a copy at the site > below: > > http://home.attbi.com/~sriramkp/draft-parameswar-sipping-norefersub- > 00.txt > > <abstract> > The recipient of the REFER method [1] creates an implicit > subscription to the 'refer' event. This subscription causes the > REFER > recipient to send NOTIFY messages to the sender informing him of the > progress of the REFER. This memo provides for the requirements and > one potential mechanism to suppress the creation of this implicit > subscription, via an option tag - 'norefersub'. This gives the agent > sending the REFER control over the creation of the subscription, > while being backwards compatible with [1]. > </abstract> > > Your comments are highly appreciated. > > Regards, > > Sriram Parameswar > > _______________________________________________ > Sip mailing list https://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 _______________________________________________ Sip mailing list https://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
- [Sip] FW: New Draft - Suppression of Refer Implic… Sriram Parameswar
- Re: [Sip] FW: New Draft - Suppression of Refer Im… Rohan Mahy
- RE: [Sip] FW: New Draft - Suppression of Refer Im… Sriram Parameswar