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

"Abbott, Nadine B." <nabbott@telcordia.com> Thu, 21 October 2004 15:14 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 LAA11880 for <sipping-emergency-web-archive@ietf.org>; Thu, 21 Oct 2004 11:14:02 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKeqJ-0005hF-JQ for sipping-emergency-web-archive@ietf.org; Thu, 21 Oct 2004 11:27:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKeXt-0006G1-5t; Thu, 21 Oct 2004 11:08:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKeOS-0002OL-FD for sipping-emergency@megatron.ietf.org; Thu, 21 Oct 2004 10:58:20 -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 KAA10193 for <sipping-emergency@ietf.org>; Thu, 21 Oct 2004 10:58:13 -0400 (EDT)
Received: from dnsmx1pya.telcordia.com ([128.96.20.31]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKeb0-0005Gb-F9 for sipping-emergency@ietf.org; Thu, 21 Oct 2004 11:11:20 -0400
Received: from rrc-its-ieg02.cc.telcordia.com (rrc-its-ieg02.cc.telcordia.com [128.96.109.3]) by dnsmx1pya.telcordia.com (8.11.7+Sun/8.9.3) with SMTP id i9LEva220287; Thu, 21 Oct 2004 10:57:36 -0400 (EDT)
Received: from rrc-its-exig01.mail.saic.com ([128.96.103.57]) by rrc-its-ieg02.cc.telcordia.com (SAVSMTP 3.1.6.45) with SMTP id M2004102110573413908 ; Thu, 21 Oct 2004 10:57:34 -0400
Received: by rrc-its-exig01.mail.saic.com with Internet Mail Service (5.5.2657.72) id <VAFDFP4T>; Thu, 21 Oct 2004 10:57:35 -0400
Message-ID: <F0CB7F62D783BF40AD93882BB817F245015EC3C6@nvc-its-exs01.cc.telcordia.com>
From: "Abbott, Nadine B." <nabbott@telcordia.com>
To: "Peterson, Jon" <jon.peterson@neustar.biz>
Subject: RE: [Sipping-emergency] New revision of proposed ECRIT charter
Date: Thu, 21 Oct 2004 10:57:34 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: 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: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906

Jon,

In the North American National Emergency Number Association (NENA) VoIP
Location WG, we have been grappling with the problem of how additional
information relevant to an emergency call might be carried to the emergency
call taker.  For example, this might include information about the caller
(e.g., Customer Name, Class of Service--Residence, Business, Public, etc.)
and information about/from a VoIP/Communications Service Provider (e.g.,
contact information for that provider) that are relevant to an emergency
call.  We are not yet ready (before this next meeting) to provide a list of
proposed requirements.  
However, I wondered if you consider that the charter for ECRIT, as written,
covers the issue of how such information--caller supplied and/or service
provider supplied--might be carried in SIP?

Respectfully,
Nadine Abbott
NENA VoIP Location WG team leader

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