IETF Logo Mail Archive

Re: [Sip] New I-D on why From/To-URIs are changed at provider borders

Jonathan Rosenberg <jdrosen@cisco.com> Tue, 26 February 2008 02:27 UTC

Return-Path: <sip-bounces@ietf.org>
X-Original-To: ietfarch-sip-archive@core3.amsl.com
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F042B28C683; Mon, 25 Feb 2008 18:27:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.272
X-Spam-Level:
X-Spam-Status: No, score=-1.272 tagged_above=-999 required=5 tests=[AWL=-0.835, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BmkuPXtrQFDx; Mon, 25 Feb 2008 18:27:27 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 332CA28C681; Mon, 25 Feb 2008 18:20:52 -0800 (PST)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5FBEA28C47F for <sip@core3.amsl.com>; Mon, 25 Feb 2008 18:20:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0CE6q-zy45lC for <sip@core3.amsl.com>; Mon, 25 Feb 2008 18:20:49 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 532893A6E8E for <sip@ietf.org>; Mon, 25 Feb 2008 18:17:00 -0800 (PST)
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-1.cisco.com with ESMTP; 25 Feb 2008 18:16:54 -0800
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m1Q2GsTf019264; Mon, 25 Feb 2008 18:16:54 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id m1Q2Gohp010333; Tue, 26 Feb 2008 02:16:50 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 25 Feb 2008 18:16:50 -0800
Received: from [10.32.241.150] ([10.32.241.150]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 25 Feb 2008 18:16:49 -0800
Message-ID: <47C37686.8000602@cisco.com>
Date: Mon, 25 Feb 2008 21:16:38 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Hadriel Kaplan <HKaplan@acmepacket.com>
References: <47B9125B.2060104@cisco.com> <47B99B39.6040105@cisco.com> <47B9DE39.60608@cisco.com> <5FB585F183235B42A9E70095055136FB79857A@DEMUEXC012.nsn-intra.net> <E6C2E8958BA59A4FB960963D475F7AC30BC4774A78@mail.acmepacket.com>
In-Reply-To: <E6C2E8958BA59A4FB960963D475F7AC30BC4774A78@mail.acmepacket.com>
X-OriginalArrivalTime: 26 Feb 2008 02:16:49.0884 (UTC) FILETIME=[A511A1C0:01C8781D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1709; t=1203992214; x=1204856214; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jdrosen@cisco.com; z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com> |Subject:=20Re=3A=20[Sip]=20New=20I-D=20on=20why=20From/To- URIs=20are=20changed=20at=20provider=20borders |Sender:=20; bh=+uhQ4MUteFdq7bEN9E0UbkoxBIclvbEwMAzaY9If5Z8=; b=EPiAm5OJShJfH3Xuts1LcDNXAwI+vKQaXC56+Su8zbW9C8EvJP5raarRF7 uYM/mLbvnuID+ZkxvnDX6IdpgpsVjGDyvudVTA4Ralrk78CD+gC32UZx0TlS wtBkDYJ2YY;
Authentication-Results: sj-dkim-3; header.From=jdrosen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
Cc: IETF SIP List <sip@ietf.org>
Subject: Re: [Sip] New I-D on why From/To-URIs are changed at provider borders
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Thanks for putting this together.

I'll add another to your list. This is more of an enterprise thing, but 
oftentimes the From URI is changed because the caller identity needs to 
be set to the attendant number before going to another domain. For 
example, if anyone within example.com makes a call, and that call 
remains within example.com, the caller ID is unchanged. But if the 
request exits the domain, the display name is often changed (Example 
Org.) and the number is changed to the direct number for example.com. I 
personally think this practice is an artifact of days long gone but it 
remains common.

-Jonathan R.

Hadriel Kaplan wrote:
> As part of an off-line discussion regarding Kai Fischer's draft on e2e-security-media and whether his From-URI copying tactic would succeed or not at a policy level, if rfc4474 fails to do so, I gave my 2 cents on what some providers had been telling me.  Dan asked me to write up a draft on it, in case people are interested.  This is the draft:
> http://www.ietf.org/internet-drafts/draft-kaplan-sip-uris-change-00.txt
> 
> -hadriel
> 
> _______________________________________________
> Sip mailing list  http://www.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
> 

-- 
Jonathan D. Rosenberg, Ph.D.                   499 Thornall St.
Cisco Fellow                                   Edison, NJ 08837
Cisco, Voice Technology Group
jdrosen@cisco.com
http://www.jdrosen.net                         PHONE: (408) 902-3084
http://www.cisco.com
_______________________________________________
Sip mailing list  http://www.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

v2.23.0 | Report a Bug | By Email