[Sipping] Security and privacy in <draft-schulzrinne-simple-rpids-01>

Henry Sinnreich <Henry.Sinnreich@mci.com> Mon, 02 June 2003 08:05 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27265 for <sipping-archive@odin.ietf.org>; Mon, 2 Jun 2003 04:05:01 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5284Xt20875 for sipping-archive@odin.ietf.org; Mon, 2 Jun 2003 04:04:33 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5284XB20872 for <sipping-web-archive@optimus.ietf.org>; Mon, 2 Jun 2003 04:04:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27206 for <sipping-web-archive@ietf.org>; Mon, 2 Jun 2003 04:04:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19MkHG-0000mE-00 for sipping-web-archive@ietf.org; Mon, 02 Jun 2003 04:02:46 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19MkHF-0000mB-00 for sipping-web-archive@ietf.org; Mon, 02 Jun 2003 04:02:45 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5283dB20740; Mon, 2 Jun 2003 04:03:39 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4RLFHB23655 for <sipping@optimus.ietf.org>; Tue, 27 May 2003 17:15:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02892 for <sipping@ietf.org>; Tue, 27 May 2003 17:15:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19KllL-0001gr-00 for sipping@ietf.org; Tue, 27 May 2003 17:13:39 -0400
Received: from dgesmtp01.wcom.com ([199.249.16.16]) by ietf-mx with esmtp (Exim 4.12) id 19KllK-0001gU-00 for sipping@ietf.org; Tue, 27 May 2003 17:13:38 -0400
Received: from dgismtp03.wcomnet.com ([166.38.58.143]) by firewall.wcom.com (Iplanet MTA) with ESMTP id <0HFK00GKHDOAA9@firewall.wcom.com> for sipping@ietf.org; Tue, 27 May 2003 21:14:35 +0000 (GMT)
Received: from dgismtp03.wcomnet.com by dgismtp03.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7 2002)) with SMTP id <0HFK00101DEW37@dgismtp03.wcomnet.com>; Tue, 27 May 2003 21:14:34 +0000 (GMT)
Received: from hsinnreich2 ([166.35.136.36]) by dgismtp03.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7 2002)) with ESMTP id <0HFK00LOWDMFIZ@dgismtp03.wcomnet.com>; Tue, 27 May 2003 21:13:36 +0000 (GMT)
Date: Tue, 27 May 2003 16:13:28 -0500
From: Henry Sinnreich <Henry.Sinnreich@mci.com>
In-reply-to: <5.2.0.9.2.20030525161330.0355dac8@pop.mcilink.com>
To: Henning Schulzrinne <hgs@cs.columbia.edu>, pkzivat@cisco.com, vkg@lucent.com, jdrosen@dynamicsoft.com, sipping@ietf.org
Message-id: <000601c32494$d72d3610$248823a6@hsinnreich2>
Organization: WorldCom, Inc.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Security and privacy in <draft-schulzrinne-simple-rpids-01>
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

The I-D <draft-schulzrinne-simple-rpids-01> provides excellent rich
presence information, but should expand on the required specifics for
matching security and privacy protection.

Section 9, Security Considerations says

"Compared to PIDF, this presence document format reveals additional
information that can be highly sensitive. Beyond traditional security
measures to protect confidentiality and integrity, systems should offer
a means to selectively reveal information to particular watchers and to
inspect the information that is being published, particularly if it is
generated automatically from other sources, such as calendars or
sensors."

I believe expanding on this and providing some criteria to differentiate
between types of watchers, with detailed examples would fill the gap.

Thanks, Henry

Henry Sinnreich
MCI
400 International Parkway
Richardson, Texas 75081
USA
 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP