Re: [sipcore] WGLC: draft-ietf-sipcore-rfc4244bis

Paul Kyzivat <pkyzivat@cisco.com> Mon, 20 June 2011 20:46 UTC

Return-Path: <pkyzivat@cisco.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40E0311E80AB for <sipcore@ietfa.amsl.com>; Mon, 20 Jun 2011 13:46:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.46
X-Spam-Level:
X-Spam-Status: No, score=-110.46 tagged_above=-999 required=5 tests=[AWL=0.139, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lzb0x-KD5O9t for <sipcore@ietfa.amsl.com>; Mon, 20 Jun 2011 13:46:07 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by ietfa.amsl.com (Postfix) with ESMTP id 7612D11E80AF for <sipcore@ietf.org>; Mon, 20 Jun 2011 13:45:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=1414; q=dns/txt; s=iport; t=1308602743; x=1309812343; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=yHNkadddula0gyVw/ScOsfx94B0LWnEObCKbyicfz2k=; b=gSvy9jBVKcLIvMVNMkIpqPIUDc79aTPcDzF+3ZSzCkN2uFpZM5qhYo8B 2vr3gkqpcRtX18P78dVWUuyGGu4a81pE9imJJ3afDOK7Y2vTRVBqxCtrG Ho1D5t8fCLAWZYuEGsJK6OAQkotyAe1JaOWgj5ORLSw63Mkv6cTV05E6c 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAEyw/02tJXG9/2dsb2JhbABTpmV3iHOhc54chioEkV6EYIs9
X-IronPort-AV: E=Sophos;i="4.65,396,1304294400"; d="scan'208";a="717731585"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by sj-iport-6.cisco.com with ESMTP; 20 Jun 2011 20:45:42 +0000
Received: from [161.44.174.125] (dhcp-161-44-174-125.cisco.com [161.44.174.125]) by rcdn-core2-2.cisco.com (8.14.3/8.14.3) with ESMTP id p5KKjf9p031073; Mon, 20 Jun 2011 20:45:42 GMT
Message-ID: <4DFFB175.5080507@cisco.com>
Date: Mon, 20 Jun 2011 16:45:41 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <4DEC205A.5040503@cisco.com> <7F2072F1E0DE894DA4B517B93C6A0585194E36022D@ESESSCMS0356.eemea.ericsson.se> <2FDD10D8-6DF3-4D77-B300-C05C2AB5D3A2@agnada.com> <7F2072F1E0DE894DA4B517B93C6A0585194E3E71BA@ESESSCMS0356.eemea.ericsson.se>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A0585194E3E71BA@ESESSCMS0356.eemea.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "draft-ietf-sipcore-rfc4244bis@tools.ietf.org" <draft-ietf-sipcore-rfc4244bis@tools.ietf.org>, "SIPCORE \(Session Initiation Protocol Core\) WG" <sipcore@ietf.org>, SIPCORE Chairs <sipcore-chairs@tools.ietf.org>, Shida Schubert <shida@agnada.com>, Robert Sparks <RjS@nostrum.com>
Subject: Re: [sipcore] WGLC: draft-ietf-sipcore-rfc4244bis
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 20 Jun 2011 20:46:08 -0000

(as individual)

On 6/17/2011 3:25 AM, Christer Holmberg wrote:

>>> 3. Tel to Sip transformation: History-Info (technical)
>>> 		
>>> Related to the previous question, the text doesn't indicate whether the transformation from Tel to Sip should be recorded in an History-Info header field. The Request-URI is, after all,
>>> changed.
>> 		
>>
>> I don't know if we need to add anything specific for this. The draft doesn't limit the
>> behavior of the entity recording H-I to only record SIP-URI, it just says to record the
>> R-URI.
>
> Based on the comments I get, the text seems to indicate that you shouldn't insert a Tel in a History-Info in the first place. Instead you should transform it to a SIP-URI before inserting it.

I agree with Christer (!!!) that the transformation from tel: to sip: 
*is* a change, and if you care about H-I then this ought to be recorded.

(This is not just a superficial change in representation - it is a 
*semantic* change, because different processing rules apply to sip URIs 
that tel URIs.)

There isn't even a guarantee that a proxy will have a suitable way to 
re-represent a tel uri as a sip URI.

So I think this calls for some sort of explanation. I guess its lucky 
that if you do create H-I entries for this, that its the translated 
(sip) URI that gets the parameters added. So its at least *possible* to 
do this.

	Thanks,
	Paul