Re: AW: [Sip] From and To-header confusion in draft-ietf-sip-replaces-04.txt

Cullen Jennings <fluffy@cisco.com> Sat, 29 November 2003 17:20 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20948 for <sip-archive@odin.ietf.org>; Sat, 29 Nov 2003 12:20:48 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AQ8lk-0001BM-7c for sip-archive@odin.ietf.org; Sat, 29 Nov 2003 12:20:33 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hATHKWEb004541 for sip-archive@odin.ietf.org; Sat, 29 Nov 2003 12:20:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AQ8lI-0001AE-Nj; Sat, 29 Nov 2003 12:20:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AQ8kj-00019C-UJ for sip@optimus.ietf.org; Sat, 29 Nov 2003 12:19:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20896 for <sip@ietf.org>; Sat, 29 Nov 2003 12:19:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AQ8ki-0007e3-00 for sip@ietf.org; Sat, 29 Nov 2003 12:19:28 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AQ8kh-0007du-00 for sip@ietf.org; Sat, 29 Nov 2003 12:19:27 -0500
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 29 Nov 2003 09:21:17 +0000
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15]) by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hATHIsAt020755; Sat, 29 Nov 2003 09:18:55 -0800 (PST)
Received: from [192.168.1.100] (sjc-vpn3-511.cisco.com [10.21.65.255]) by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AKI10527; Sat, 29 Nov 2003 09:18:53 -0800 (PST)
User-Agent: Microsoft-Entourage/10.1.4.030702.0
Date: Sat, 29 Nov 2003 09:18:51 -0800
Subject: Re: AW: [Sip] From and To-header confusion in draft-ietf-sip-replaces-04.txt
From: Cullen Jennings <fluffy@cisco.com>
To: Christian Stredicke <stredicke@snom.de>, "'Paul D.Smith'" <Paul.D.Smith@dataconnection.com>
CC: sip@ietf.org
Message-ID: <BBEE14FB.27243%fluffy@cisco.com>
In-Reply-To: <062f01c3b599$2a085a00$3900a8c0@sip>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3152942332_167840"
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>

Sounds like we need to fix the draft.

On 11/28/03 2:19 AM, "Christian Stredicke" <stredicke@snom.de> wrote:

> Hi Paul,
>  
> correct. The problem is that users get angry if the pickup does not work just
> because of standards confusion.
>  
> Our current workaround is to relax the requirement a little bit and accept to-
> and from-tags exchanged. That works fine, however there is some risk that this
> can lead to some false pickups. However, I don¹t know a scenario where this
> can be an issue.
>  
> Christian
>  
> 
> -----Ursprüngliche Nachricht-----
> Von: Paul D.Smith [mailto:Paul.D.Smith@dataconnection.com]
> Gesendet: Freitag, 28. November 2003 11:05
> An: 'Christian Stredicke'
> Cc: 'sip@ietf.org'
> Betreff: RE: [Sip] From and To-header confusion in
> draft-ietf-sip-replaces-04.txt
>  
> 
> Christian,
> 
>  
> 
> If I understand you correctly, you are pointing out the following.
> 
>  
> 
> If a target receives an INVITE with Replaces headers, it has to somehow use
> the Replaces To/From fields to identify a dialog.  If this dialog were
> originally started by the target then there may be a mapping of:
> 
>  
> 
> To field of original INVITE ==> target's idea of remote tag
> 
> From field of original INVITE ==> target's idea of local tag.
> 
>  
> 
> However if the target did not start the dialog, the mapping is reversed.
> 
>  
> 
> To field of original INVITE ==> target's idea of local tag
> 
> From field of original INVITE ==> target's idea of remote tag.
> 
>  
> 
> And your question is... how does the Replaces To/From get mapped to the
> targets idea of local/remote tags?
> 
>  
> 
> Unfortunately, this can't be resolved into a simple mapping.  A third party
> REFER modifying an INVITE may not know who started the dialog and so renaming
> the Replaces fields makes no difference since the referrer still doesn't know
> which tag to place in which field.  The target has to perform a lookup using
> both mappings - often one will find a dialog and the other will not.
> 
>  
> 
> There is a possible issue with "loopback" type dialogs where a UA, with
> multiple personalities (i.e. a gateway) may have two dialogs, one in each
> direction.  In this case, it may be impossible to map to a single dialog,
> which is where the following sentence from page 5 of the draft is headed...
> 
>  
> 
>   "If the Replaces header field matches more than one dialog, the UA MUST act
> as if no match is found."
> 
>  
> 
> Is this a correct understanding of your posting?
> 
>  
> 
> Regards,
> 
> Paul DS.
> 
> Paul D.Smith 
> Network Protocols Group
> Data Connection Ltd (DCL)
> Tel: +44 20 8366 1177  Email: paul.d.smith@dataconnection.com
> Fax: +44 20 8363 1039  Web:   http://www.dataconnection.com
> <http://www.dataconnection.com/>
> -----Original Message-----
> From: Christian Stredicke [mailto:stredicke@snom.de]
> Sent: 27 November 2003 17:45
> To: SIP (E-mail)
> Subject: [Sip] From and To-header confusion in draft-ietf-sip-replaces-04.txt
>> 
>> Hi!
>>  
>> I think there is some from and to-header confusion in the Replaces header.
>>  
>> Depending on who initiates the call, the to and from must be exchanged. Maybe
>> it would be better to use the term local and remote-tag instead or to allow
>> mixing from and to.
>>  
>> Christian
>> --
>> Christian Stredicke
>> tel:+49.30.39833.401 (ENUM & PSTN)
>