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

"James M. Polk" <jmpolk@cisco.com> Thu, 21 October 2004 15:49 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 LAA15337 for <sipping-emergency-web-archive@ietf.org>; Thu, 21 Oct 2004 11:49:25 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKfOZ-0006Tk-Th for sipping-emergency-web-archive@ietf.org; Thu, 21 Oct 2004 12:02:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKf4D-0004bZ-2z; Thu, 21 Oct 2004 11:41:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKewv-0001cM-Vb for sipping-emergency@megatron.ietf.org; Thu, 21 Oct 2004 11:33:58 -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 LAA13795 for <sipping-emergency@ietf.org>; Thu, 21 Oct 2004 11:33:55 -0400 (EDT)
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKf9Y-00067X-P6 for sipping-emergency@ietf.org; Thu, 21 Oct 2004 11:47:02 -0400
Received: from sj-core-3.cisco.com (171.68.223.137) by sj-iport-4.cisco.com with ESMTP; 21 Oct 2004 08:34:04 -0700
X-BrightmailFiltered: true
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id i9LFXN9b003882; Thu, 21 Oct 2004 08:33:23 -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 IAA27103; Thu, 21 Oct 2004 08:33:22 -0700 (PDT)
Message-Id: <4.3.2.7.2.20041021103008.02915808@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 21 Oct 2004 10:33:21 -0500
To: "Abbott, Nadine B." <nabbott@telcordia.com>, "Peterson, Jon" <jon.peterson@neustar.biz>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: RE: [Sipping-emergency] New revision of proposed ECRIT charter
In-Reply-To: <F0CB7F62D783BF40AD93882BB817F245015EC3C6@nvc-its-exs01.cc. telcordia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
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: 1.1 (+)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352

Isn't most of this an extension to the PIDF-LO effort in Geopriv, and not 
part of ECRIT?

The portion that I believe is part of SIP/PING would be the addition of a 
body part by the VSP (in add the contact info you want) - which has so far 
been frowned upon (to say the least) in these WGs

At 10:57 AM 10/21/2004 -0400, Abbott, Nadine B. wrote:
>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


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