IETF Logo Mail Archive

[Sipping-emergency] General Question about Scope of this list

"James M. Polk" <jmpolk@cisco.com> Mon, 17 February 2003 22:27 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02882 for <sipping-emergency-archive@odin.ietf.org>; Mon, 17 Feb 2003 17:27:44 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1HMX2d28618 for sipping-emergency-archive@odin.ietf.org; Mon, 17 Feb 2003 17:33:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1HMX2p28615 for <sipping-emergency-web-archive@optimus.ietf.org>; Mon, 17 Feb 2003 17:33:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02865 for <sipping-emergency-web-archive@ietf.org>; Mon, 17 Feb 2003 17:27:14 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1HMX1p28607 for <sipping-emergency-web-archive@ietf.org>; Mon, 17 Feb 2003 17:33:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1HMWMp28575 for <sipping-emergency@optimus.ietf.org>; Mon, 17 Feb 2003 17:32:22 -0500
Received: from halt-in.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02843 for <sipping-emergency@ietf.org>; Mon, 17 Feb 2003 17:26:34 -0500 (EST)
Received: from cisco.com (171.71.177.223) by halt-in.cisco.com with ESMTP; 17 Feb 2003 14:30:40 -0800
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 OAA14032 for <sipping-emergency@ietf.org>; Mon, 17 Feb 2003 14:30:21 -0800 (PST)
Message-Id: <4.3.2.7.2.20030217161831.047e6110@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 17 Feb 2003 16:29:07 -0600
To: sipping-emergency@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Sipping-emergency] General Question about Scope of this list
Sender: sipping-emergency-admin@ietf.org
Errors-To: sipping-emergency-admin@ietf.org
X-BeenThere: sipping-emergency@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping-emergency>, <mailto:sipping-emergency-request@ietf.org?subject=unsubscribe>
List-Id: <sipping-emergency.ietf.org>
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>

All

Since I wasn't in the initial concall for this list's creation, can I ask 
what the general scope is of this design team?

Is it SIP for e911/112 (sos@)?

Is it SIP for all Emergency Services (GETS, IEPREP, GTPS, FEMA, etc)?

Is it SIP for Gov/Military Preferential Emergency Communications (MLPP)?

Any combination of the 3 listed above?

The first 3 of the above qualify as "emergency", but in reading Henning's 
draft, that ID seems much skewed towards only the 1st case above, yet it is 
similar to this new list's name.

I'm just looking for guidance and boundaries, folks

cheers,
James

               *************************************
"People generally demand more respect for their own rights than
                          they are willing to allow for others"

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

v2.8.7 | Report a Bug | By Email