Re: [SIP] Replaces header and REFER

Rohan Mahy <rohan@cisco.com> Tue, 22 July 2003 18:46 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 OAA22284 for <sip-archive@odin.ietf.org>; Tue, 22 Jul 2003 14:46:46 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f29U-0003EM-HX for sip-archive@odin.ietf.org; Tue, 22 Jul 2003 14:46:20 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6MIkKtl012413 for sip-archive@odin.ietf.org; Tue, 22 Jul 2003 14:46:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f29B-0003DH-Sn; Tue, 22 Jul 2003 14:46:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f28d-0003Ci-PV for sip@optimus.ietf.org; Tue, 22 Jul 2003 14:45:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22265 for <sip@ietf.org>; Tue, 22 Jul 2003 14:45:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19f28b-0006cU-00 for sip@ietf.org; Tue, 22 Jul 2003 14:45:25 -0400
Received: from sj-core-4.cisco.com ([171.68.223.138]) by ietf-mx with esmtp (Exim 4.12) id 19f28Q-0006c0-00 for sip@ietf.org; Tue, 22 Jul 2003 14:45:14 -0400
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id h6MIiMpp013715; Tue, 22 Jul 2003 11:44:22 -0700 (PDT)
Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134]) by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AJL79388; Tue, 22 Jul 2003 11:40:27 -0700 (PDT)
Date: Tue, 22 Jul 2003 20:46:28 +0200
Subject: Re: [SIP] Replaces header and REFER
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "'sip@ietf.org'" <sip@ietf.org>
To: Werkstudent8 SAL <werkstudent8.sal@mch.siemens.de>
From: Rohan Mahy <rohan@cisco.com>
In-Reply-To: <B3028CA9D0B8D511874E0002A53F24D571DBC0@mchh9mla.mchh.siemens.de>
Message-Id: <CDFC005A-BC74-11D7-B1E0-0003938AF740@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
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

On Wednesday, July 16, 2003, at 03:38 PM, Werkstudent8 SAL wrote:

> From: "Stefan Mecke" <werkstudent8.sal@mch.siemens.de>
>
> Hi all,
>
> I have a question about draft-ietf-sip-replaces-03.txt:
> Section 2 says:
>    ... the Replaces header is
>    frequently used in combination with the REFER [4] method ...

it is frequently used in combination with the REFER method, by 
embedding the Replaces header in the Refer-To URI.   The Replaces 
header NEVER appears in the header section of a REFER request.

> but section 3 contains:
>    ... if
>    a Replaces header field is present in a request other than INVITE,
>    the UAS MUST reject the request ..
>
> I think it makes a lot of sense to allow replaces with REFER; e.g. in 
> the
> call park scenario you could have a web page with all call and make a 
> "click
> to retrieve from park" to have it on your desk phone.
> And that is similar to what's described in
> draft-ietf-sipping-cc-transfer-01.txt, although I have a notion that 
> there
> is some difference but I don't manage to get it out of the draft.

check out draft-ietf-sipping-service-examples

this draft describes several solutions including call park/retrieve.

thanks,
-rohan

> Thanks
>
> _______________________________________________
> 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