[Sip] draft-ietf-sip-refer-02 - SHOULD strength when sending NOTIFY
"JF Rey" <jfr@post.com> Thu, 13 December 2001 15:15 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 KAA22015 for <sip-archive@odin.ietf.org>; Thu, 13 Dec 2001 10:15:34 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id KAA01328 for sip-archive@odin.ietf.org; Thu, 13 Dec 2001 10:15:35 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00301; Thu, 13 Dec 2001 09:55:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00266 for <sip@optimus.ietf.org>; Thu, 13 Dec 2001 09:55:13 -0500 (EST)
Received: from ws1-7.us4.outblaze.com (205-158-62-57.outblaze.com [205.158.62.57]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA21763 for <sip@ietf.org>; Thu, 13 Dec 2001 09:55:10 -0500 (EST)
Received: (qmail 17511 invoked by uid 1001); 13 Dec 2001 14:54:42 -0000
Message-ID: <20011213145442.17510.qmail@mail.com>
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-Mailer: MIME-tools 5.41 (Entity 5.404)
Received: from ws1-7.us4.outblaze.com for [212.208.74.200] via web-mailer on Thu, 13 Dec 2001 22:54:41 +0800
From: JF Rey <jfr@post.com>
To: sip@ietf.org
Date: Thu, 13 Dec 2001 22:54:41 +0800
Content-Transfer-Encoding: 7bit
Subject: [Sip] draft-ietf-sip-refer-02 - SHOULD strength when sending NOTIFY
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, I'm a bit confused about the way NOTIFY are used by the "referee" party. referer referee |====== SIP session ===| |--------REFER-------> | |<--------202--------- |----INVITE --> | |<---180------ ... quite a long time ... |<------NOTIFY ------ |<---200------ |----------200-------->| |---------- BYE ------>| draft-ietf-sip-refer-02 states : "3.5.3.1 Using NOTIFY Once it is known whether the reference succeeded or failed, the UA receiving the REFER SHOULD notify the agent sending the refer using the NOTIFY mechanism [...]" All the example flows I've seen around use the NOTIFY mechanism whenever a REFER is accepted. If I understand the "SHOULD" strength correctly, the referer can't know whether the referee will send a NOTIFY. So it can't know when to stop waiting for a NOTIFY and when to send a BYE. I think that's quite awkward. Besides, I understand that nothing prevents a referee to send NOTIFY on provisional responses (and not only on final responses). But the way the sentence is written : "whether the reference succeeded or failed" does not really take provisional responses into account. No example in draft-ietf-sip-cc-transfer-05.txt shows NOTIFY triggered by 1xx. If the referee INVITEs a human, the referer may have a very long time to wait before receiving a NOTIFY triggered by the 200 response to the INVITE. Do people implement REFER without the NOTIFY mechanism ? If we can't change the SHOULD strength, could we have a way for the referee to indicate that it will send NOTIFY ? Could the wording in 3.5.3.1 include NOTIFY on provisional responses ? Jean-Francois. -- _______________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup 1 cent a minute calls anywhere in the U.S.! http://www.getpennytalk.com/cgi-bin/adforward.cgi?p_key=RG9853KJ&url=http://www.getpennytalk.com _______________________________________________ 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
- [Sip] draft-ietf-sip-refer-02 - SHOULD strength w… JF Rey
- RE: [Sip] draft-ietf-sip-refer-02 - SHOULD streng… Robert Sparks
- RE: [Sip] draft-ietf-sip-refer-02 - SHOULD streng… Ranjit Avasarala
- RE: [Sip] draft-ietf-sip-refer-02 - SHOULD streng… Sriram Parameswar
- RE: [Sip] draft-ietf-sip-refer-02 - SHOULD streng… Ranjit Avasarala
- RE: [Sip] draft-ietf-sip-refer-02 - SHOULD streng… Sriram Parameswar