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

Henning Schulzrinne <hgs@cs.columbia.edu> Fri, 29 October 2004 13:03 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 JAA26606 for <sipping-emergency-web-archive@ietf.org>; Fri, 29 Oct 2004 09:03:06 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNWdd-0006UN-3g for sipping-emergency-web-archive@ietf.org; Fri, 29 Oct 2004 09:17:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNWID-0000wS-BE; Fri, 29 Oct 2004 08:55:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNWAG-0003bv-HY for sipping-emergency@megatron.ietf.org; Fri, 29 Oct 2004 08:47:32 -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 IAA25327 for <sipping-emergency@ietf.org>; Fri, 29 Oct 2004 08:47:31 -0400 (EDT)
Received: from cs.columbia.edu ([128.59.16.20]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNWOX-00066n-5f for sipping-emergency@ietf.org; Fri, 29 Oct 2004 09:02:18 -0400
Received: from razor.cs.columbia.edu (IDENT:f7wK6sC/2kWzdoZGERCliq2y4Qf4F2LK@razor.cs.columbia.edu [128.59.16.8]) by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id i9TCkERX014857; Fri, 29 Oct 2004 08:46:14 -0400 (EDT)
Received: from [127.0.0.1] (IDENT:EyiQ4l4Nl1DuNHNbAMmahahLOFH39k6W@localhost [127.0.0.1]) by razor.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id i9TCk9XH006687; Fri, 29 Oct 2004 08:46:10 -0400
Message-ID: <41823B32.80606@cs.columbia.edu>
Date: Fri, 29 Oct 2004 08:44:34 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tschofenig Hannes <hannes.tschofenig@siemens.com>
Subject: Re: [Sipping-emergency] New revision of proposed ECRIT charter
References: <2A8DB02E3018D411901B009027FD3A3F0468693E@mchp905a.mch.sbs.de>
In-Reply-To: <2A8DB02E3018D411901B009027FD3A3F0468693E@mchp905a.mch.sbs.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.2.0, Antispam-Data: 2004.10.29.0
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0'
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit
Cc: "'James M. Polk'" <jmpolk@cisco.com>, 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: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit

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



_______________________________________________
Sipping-emergency mailing list
Sipping-emergency@ietf.org
https://www1.ietf.org/mailman/listinfo/sipping-emergency