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

Paul Kyzivat <> Mon, 20 June 2011 20:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 40E0311E80AB for <>; Mon, 20 Jun 2011 13:46:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -110.46
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id lzb0x-KD5O9t for <>; Mon, 20 Jun 2011 13:46:07 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 7612D11E80AF for <>; Mon, 20 Jun 2011 13:45:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; 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 ([]) by with ESMTP; 20 Jun 2011 20:45:42 +0000
Received: from [] ( []) by (8.14.3/8.14.3) with ESMTP id p5KKjf9p031073; Mon, 20 Jun 2011 20:45:42 GMT
Message-ID: <>
Date: Mon, 20 Jun 2011 16:45:41 -0400
From: Paul Kyzivat <>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Christer Holmberg <>
References: <> <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "" <>, "SIPCORE (Session Initiation Protocol Core) WG" <>, SIPCORE Chairs <>, Shida Schubert <>, Robert Sparks <>
Subject: Re: [sipcore] WGLC: draft-ietf-sipcore-rfc4244bis
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-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.