Re: [Sipping-emergency] New revision of proposed ECRIT charter

"James M. Polk" <jmpolk@cisco.com> Fri, 29 October 2004 17:36 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 NAA18044 for <sipping-emergency-web-archive@ietf.org>; Fri, 29 Oct 2004 13:36:17 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNau5-0004By-0l for sipping-emergency-web-archive@ietf.org; Fri, 29 Oct 2004 13:51:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNaZe-0000kD-0h; Fri, 29 Oct 2004 13:30:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNaO7-00035R-Mg for sipping-emergency@megatron.ietf.org; Fri, 29 Oct 2004 13:18:10 -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 NAA16850 for <sipping-emergency@ietf.org>; Fri, 29 Oct 2004 13:18:04 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNacO-0003oY-F0 for sipping-emergency@ietf.org; Fri, 29 Oct 2004 13:32:55 -0400
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-2.cisco.com with ESMTP; 29 Oct 2004 10:27:02 -0700
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i9THHRQ0014339; Fri, 29 Oct 2004 10:17:28 -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 KAA23314; Fri, 29 Oct 2004 10:17:28 -0700 (PDT)
Message-Id: <4.3.2.7.2.20041029120929.0264bee8@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 29 Oct 2004 12:17:30 -0500
To: Henning Schulzrinne <hgs@cs.columbia.edu>, Tschofenig Hannes <hannes.tschofenig@siemens.com>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [Sipping-emergency] New revision of proposed ECRIT charter
In-Reply-To: <41823B32.80606@cs.columbia.edu>
References: <2A8DB02E3018D411901B009027FD3A3F0468693E@mchp905a.mch.sbs.de> <2A8DB02E3018D411901B009027FD3A3F0468693E@mchp905a.mch.sbs.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: sipping-emergency@ietf.org, "Abbott, Nadine B." <nabbott@telcordia.com>
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: a7d6aff76b15f3f56fcb94490e1052e4

What Nadine wants is the name of the organization that provided the 
location to the endpoint. This is not a decoupled action between the CIPID 
and the PIDF-LO, their are in association with each other. Revealing who 
asserts my location information (Fort_worth_VPC.org) reveals fairly 
specifically where I am in most contexts. This is a revelation of location 
information I as a user might not want in my location policy. If you 
mandate it is outside of the rules of PIDF-LO, we must generate a duplicate 
set of privacy and security requirements in this WG

At 08:44 AM 10/29/2004 -0400, Henning Schulzrinne wrote:
>Tschofenig Hannes wrote:
>>hi james, nadine, henning,
>>henning pointed us to some work in the simple wg. maybe you, nadine, want to
>>check whether the nena requirements match the currently offered
>>functionality.
>
>To amplify: vCard currently provides the name (and other information), but 
>doesn't provide the service provider name and other details. However, it 
>would seem trivial to add either to CIPID or vCard, as they may well be 
>useful outside the emergency services context. From a data type 
>perspective, these pieces of information aren't really location 
>information, so stuffing them into PIDF-LO or an extension thereof seems a 
>bit of a stretch.
>
>My general inclination is to avoid emergency-only protocol features.
>
>Henning
>
>


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