[sipcore] Understanding Privacy: history invoked by UAS

"Elwell, John" <john.elwell@siemens-enterprise.com> Tue, 09 November 2010 02:32 UTC

Return-Path: <john.elwell@siemens-enterprise.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 54A003A6A1A for <sipcore@core3.amsl.com>; Mon, 8 Nov 2010 18:32:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.485
X-Spam-Level:
X-Spam-Status: No, score=-102.485 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599, 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 6NH9L1R-MwRY for <sipcore@core3.amsl.com>; Mon, 8 Nov 2010 18:32:36 -0800 (PST)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 89CD428C1C4 for <sipcore@ietf.org>; Mon, 8 Nov 2010 18:32:28 -0800 (PST)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-2223280 for sipcore@ietf.org; Tue, 9 Nov 2010 03:32:50 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx (Server) with ESMTP id 2B5BD23F0278 for <sipcore@ietf.org>; Tue, 9 Nov 2010 03:32:50 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Tue, 9 Nov 2010 03:32:50 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "sipcore@ietf.org" <sipcore@ietf.org>
Date: Tue, 9 Nov 2010 03:32:48 +0100
Thread-Topic: Understanding Privacy: history invoked by UAS
Thread-Index: Act/tmX64nFBhz6FSZe0YJ2Va+pn3Q==
Message-ID: <A444A0F8084434499206E78C106220CA02357ADA69@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [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 02:32:43 -0000

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