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

Tschofenig Hannes <hannes.tschofenig@siemens.com> Thu, 28 October 2004 09:24 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 FAA22985 for <sipping-emergency-web-archive@ietf.org>; Thu, 28 Oct 2004 05:24:57 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CN6kj-0004XJ-Ea for sipping-emergency-web-archive@ietf.org; Thu, 28 Oct 2004 05:39:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CN6VW-0002Kw-Ei; Thu, 28 Oct 2004 05:23:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CN6SQ-0001j7-90 for sipping-emergency@megatron.ietf.org; Thu, 28 Oct 2004 05:20:34 -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 FAA22706 for <sipping-emergency@ietf.org>; Thu, 28 Oct 2004 05:20:32 -0400 (EDT)
Received: from goliath.siemens.de ([192.35.17.28]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CN6gS-0004ST-N5 for sipping-emergency@ietf.org; Thu, 28 Oct 2004 05:35:05 -0400
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by goliath.siemens.de (8.12.6/8.12.6) with ESMTP id i9S9KUP6011718; Thu, 28 Oct 2004 11:20:30 +0200
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99]) by mail3.siemens.de (8.12.6/8.12.6) with ESMTP id i9S9KTBO026793; Thu, 28 Oct 2004 11:20:29 +0200
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2657.72) id <4BVR7K5C>; Thu, 28 Oct 2004 11:20:29 +0200
Message-ID: <2A8DB02E3018D411901B009027FD3A3F051C88C0@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "James M. Polk" <jmpolk@cisco.com>, "Abbott, Nadine B." <nabbott@telcordia.com>, "Peterson, Jon" <jon.peterson@neustar.biz>
Subject: RE: [Sipping-emergency] New revision of proposed ECRIT charter
Date: Thu, 28 Oct 2004 11:20:25 +0200
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: cd26b070c2577ac175cd3a6d878c6248
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: b7b9551d71acde901886cc48bfc088a6

hi james, 
 
some data items seem to be part of the pidf-lo work. however, as nadine
mentioned there are additional fields:
- Customer Name, 
- Class of Service--Residence, Business, Public, etc.
- information about/from a VoIP/Communications Service Provider

this information is not included in the pidf-lo.

is this use case for saml you are often talking about? 

ciao
hannes

> -----Original Message-----
> From: James M. Polk [mailto:jmpolk@cisco.com] 
> Sent: Donnerstag, 21. Oktober 2004 17:33
> To: Abbott, Nadine B.; Peterson, Jon
> Cc: sipping-emergency@ietf.org
> Subject: RE: [Sipping-emergency] New revision of proposed 
> ECRIT charter
> 
> 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
> 

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