Privacy Concerns (was Re: [Sipping-emergency] RE: Civil location syntax validation - wa s RE: How to handle Validation failures)
"James M. Polk" <jmpolk@cisco.com> Wed, 29 September 2004 03:56 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22670 for <sipping-emergency-web-archive@ietf.org>; Tue, 28 Sep 2004 23:56:53 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CCViI-0003Ol-3L for sipping-emergency-web-archive@ietf.org; Wed, 29 Sep 2004 00:05:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CCVYF-0003MI-PD; Tue, 28 Sep 2004 23:54:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CCVWK-0002QJ-WF for sipping-emergency@megatron.ietf.org; Tue, 28 Sep 2004 23:52:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22526 for <sipping-emergency@ietf.org>; Tue, 28 Sep 2004 23:52:46 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CCVeF-0003Ap-Kh for sipping-emergency@ietf.org; Wed, 29 Sep 2004 00:01:02 -0400
Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-3.cisco.com with ESMTP; 28 Sep 2004 21:05:41 +0000
X-BrightmailFiltered: true
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i8T3q9wp023360; Tue, 28 Sep 2004 20:52:09 -0700 (PDT)
Received: from jmpolk-w2k01.diablo.cisco.com (ssh-sjc-1.cisco.com [171.68.225.134]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id UAA28705; Tue, 28 Sep 2004 20:52:09 -0700 (PDT)
Message-Id: <4.3.2.7.2.20040928223925.03466028@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 28 Sep 2004 22:52:10 -0500
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>, "Peterson, Jon" <jon.peterson@neustar.biz>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Privacy Concerns (was Re: [Sipping-emergency] RE: Civil location syntax validation - wa s RE: How to handle Validation failures)
In-Reply-To: <415A262C.60904@dynamicsoft.com>
References: <7927C67249E4AD43BC05B539AF0D129801AF41E8@stntexch04.cis.neustar.com> <7927C67249E4AD43BC05B539AF0D129801AF41E8@stntexch04.cis.neustar.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: 'Marc Linsner' <mlinsner@cisco.com>, John Morris <jmorris-lists@cdt.org>, sipping-emergency@ietf.org
X-BeenThere: sipping-emergency@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: sipping-emergency.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping-emergency>, <mailto:sipping-emergency-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping-emergency@ietf.org>
List-Help: <mailto:sipping-emergency-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping-emergency>, <mailto:sipping-emergency-request@ietf.org?subject=subscribe>
Sender: sipping-emergency-bounces@ietf.org
Errors-To: sipping-emergency-bounces@ietf.org
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
At 11:04 PM 9/28/2004 -0400, Jonathan Rosenberg wrote: >Along those lines, I think it might be a good idea to sprinkle some nice >words into the charter about taking into consideration privacy concerns, >and properly balancing them with the needs of emergency call routing. this is what I was referring to when I made the quip about being steered. I see this being a tracking capability. The phone (or multimedia device in general) has to obtain an address given by the network and test its deliverability to a government service before that device will potentially ever be used for any service (not just 911). This means to me that "the system" always knows where the device is (because it always delivers an accurate and valid address to it, and that device test pings for reachability and accuracy of the location it is given, on an ongoing basis). The periodic test ping/no-op packets ensuring a PSAP can be reached if a 911-type session is attempted has to reveal the return addressing, including each user's URI. This has huge hijacking and misuse potential written all over it, as Jonathan pointed out; not only in the database, but in the gleaning of packets to and from targets. >-Jonathan R. > >-- >Jonathan D. Rosenberg, Ph.D. 600 Lanidex Plaza >Chief Technology Officer Parsippany, NJ 07054-2711 >dynamicsoft >jdrosen@dynamicsoft.com FAX: (973) 952-5050 >http://www.jdrosen.net PHONE: (973) 952-5000 >http://www.dynamicsoft.com > >_______________________________________________ >Sipping-emergency mailing list >Sipping-emergency@ietf.org >https://www1.ietf.org/mailman/listinfo/sipping-emergency cheers, James ******************* Truth is not to be argued... it is to be presented _______________________________________________ Sipping-emergency mailing list Sipping-emergency@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-emergency
- RE: [Sipping-emergency] RE: Civil location syntax… Peterson, Jon
- Re: [Sipping-emergency] RE: Civil location syntax… Jonathan Rosenberg
- Privacy Concerns (was Re: [Sipping-emergency] RE:… James M. Polk
- RE: [Sipping-emergency] RE: Civil location syntax… Peterson, Jon
- RE: [Sipping-emergency] RE: Civil location syntax… Marc Linsner