Re: [sipcore] About SUBSCRIBE method's performance and Out-of-Dialog notification suggestion:
gao.yang2@zte.com.cn Wed, 05 January 2011 06:13 UTC
Return-Path: <gao.yang2@zte.com.cn>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3567B3A6992 for <sipcore@core3.amsl.com>; Tue, 4 Jan 2011 22:13:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.538
X-Spam-Level:
X-Spam-Status: No, score=-101.538 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
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 nYBcE8NuJ9eR for <sipcore@core3.amsl.com>; Tue, 4 Jan 2011 22:13:43 -0800 (PST)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id 652233A6A77 for <sipcore@ietf.org>; Tue, 4 Jan 2011 22:13:41 -0800 (PST)
Received: from [10.34.0.130] by mx5.zte.com.cn with surfront esmtp id 35101727820181; Wed, 5 Jan 2011 14:13:56 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.15] with StormMail ESMTP id 68277.3337783744; Wed, 5 Jan 2011 14:15:43 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id p056FDF5096226; Wed, 5 Jan 2011 14:15:13 +0800 (CST) (envelope-from gao.yang2@zte.com.cn)
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A0585048F8C5A@ESESSCMS0356.eemea.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
MIME-Version: 1.0
X-KeepSent: 358C491E:316767BF-4825780F:001F809A; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF358C491E.316767BF-ON4825780F.001F809A-4825780F.002258A2@zte.com.cn>
From: gao.yang2@zte.com.cn
Date: Wed, 05 Jan 2011 14:12:22 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-01-05 14:15:01, Serialize complete at 2011-01-05 14:15:01
Content-Type: multipart/alternative; boundary="=_alternative 002258A04825780F_="
X-MAIL: mse2.zte.com.cn p056FDF5096226
Cc: "sipcore@ietf.org" <sipcore@ietf.org>
Subject: Re: [sipcore] About SUBSCRIBE method's performance and Out-of-Dialog notification suggestion:
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2011 06:13:45 -0000
Hi Christer, > 1. I assume the SUB sender would still need store some data, in > order to match the out-of-dialog NOT to the previous SUB dialog? By my primary thinking, I'd like this feature Event Package specific, that is some Event Packages which have the requirement could send notification out-of-dialog. Further, I think some Event Packages might need matching mechanism, some migt cut it out. But I think the matching mechanism is not the so heavy here, as the most memory usage is for Route Set. This heavey part could be saved while we use notification out-of-dialog. > > 2. If 1 is true, for how long would the SUB sender keep this data, > and be prepared to receive the out-of-dialog NOT? I guess the > subscription timers don't apply in this case, or? I think this could be defined Event Package specific too. > > 3. Would the out-of-dialog NOT be routed using a Contact/GRUU, > rather than the AOR, of the SUB sender, to ensure it reaches the SUB sender? To be honest, my proposal is row now, and I hadn't think this point. I agree that considering a specific heavy SUBSCRIBE usage, the "out-of-dialog" suggestion might not save impressive resource. But considering general usage, I think it would be meaningful. Thanks, Gao -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender. This message has been scanned for viruses and Spam by ZTE Anti-Spam system.
- Re: [sipcore] About SUBSCRIBE method's performanc… Paul Kyzivat
- [sipcore] About SUBSCRIBE method's performance an… gao.yang2
- Re: [sipcore] About SUBSCRIBE method's performanc… Christer Holmberg
- Re: [sipcore] About SUBSCRIBE method's performanc… Worley, Dale R (Dale)
- Re: [sipcore] About SUBSCRIBE method's performanc… DRAGE, Keith (Keith)
- Re: [sipcore] About SUBSCRIBE method's performanc… Worley, Dale R (Dale)
- Re: [sipcore] About SUBSCRIBE method's performanc… Paul Kyzivat
- Re: [sipcore] About SUBSCRIBE method's performanc… Christer Holmberg
- Re: [sipcore] About SUBSCRIBE method's performanc… Paul Kyzivat
- Re: [sipcore] About SUBSCRIBE method's performanc… Adam Roach
- Re: [sipcore] About SUBSCRIBE method's performanc… gao.yang2
- Re: [sipcore] About SUBSCRIBE method's performanc… gao.yang2
- Re: [sipcore] About SUBSCRIBE method's performanc… gao.yang2
- Re: [sipcore] About SUBSCRIBE method's performanc… gao.yang2
- Re: [sipcore] About SUBSCRIBE method's performanc… Worley, Dale R (Dale)
- Re: [sipcore] About SUBSCRIBE method's performanc… gao.yang2