Re: [sipcore] Understanding Privacy: history invoked by UAS

Shida Schubert <shida@ntt-at.com> Tue, 09 November 2010 06:23 UTC

Return-Path: <shida@ntt-at.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BFA193A6894 for <sipcore@core3.amsl.com>; Mon, 8 Nov 2010 22:23:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.115
X-Spam-Level:
X-Spam-Status: No, score=-102.115 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 F+2h3E+lGzAd for <sipcore@core3.amsl.com>; Mon, 8 Nov 2010 22:23:37 -0800 (PST)
Received: from gateway14.websitewelcome.com (gateway14.websitewelcome.com [69.93.154.35]) by core3.amsl.com (Postfix) with SMTP id 753363A6810 for <sipcore@ietf.org>; Mon, 8 Nov 2010 22:23:28 -0800 (PST)
Received: (qmail 19123 invoked from network); 9 Nov 2010 06:24:48 -0000
Received: from gator465.hostgator.com (69.56.174.130) by gateway14.websitewelcome.com with SMTP; 9 Nov 2010 06:24:48 -0000
Received: from [130.129.116.143] (port=52871 helo=dhcp-748f.meeting.ietf.org) by gator465.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <shida@ntt-at.com>) id 1PFhcP-0001Li-Ae; Tue, 09 Nov 2010 00:23:46 -0600
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Shida Schubert <shida@ntt-at.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA02357ADA69@MCHP058A.global-ad.net>
Date: Tue, 9 Nov 2010 15:23:47 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <A78B9020-EB78-477E-8B2A-22F8F27B1032@ntt-at.com>
References: <A444A0F8084434499206E78C106220CA02357ADA69@MCHP058A.global-ad.net>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
X-Mailer: Apple Mail (2.1081)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator465.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ntt-at.com
Cc: "sipcore@ietf.org" <sipcore@ietf.org>
Subject: Re: [sipcore] Understanding Privacy: history invoked by UAS
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 09 Nov 2010 06:23:40 -0000

Hi John;

 In practice, if C cares about its privacy, there should be 
a priori arrangement with the service provider or 
configuration in proxy to withhold its identity.

 This will allow the proxy sending the 4xx which sets the hi-entry 
to ensure privacy is applied by setting escaped privacy header 
or Privacy:header. 

 Regards
  Shida 

On Nov 9, 2010, at 11:32 AM, Elwell, John wrote:

> Suppose a request from A is targeted initially at B, this is mapped to C, and then to registered contact D. The UAS (D) puts Privacy: history in the response, and therefore prevents A learning about C and D. Fine.
> 
> Now, supposing D is not registered at the time, i.e., there is no registered contact for C. This results in a 4xx response to A. How do we ensure that the identity of C is not disclosed to A, in line with what is achieved when D is registered?
> 
> John
> 
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore