Re: [Sipping-emergency] Re: Emergency-req: remarks 1-4

"James M. Polk" <jmpolk@cisco.com> Mon, 24 February 2003 02:53 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 VAA18981 for <sipping-emergency-archive@odin.ietf.org>; Sun, 23 Feb 2003 21:53:10 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1O31Ts09728 for sipping-emergency-archive@odin.ietf.org; Sun, 23 Feb 2003 22:01:29 -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 h1O31Tp09725 for <sipping-emergency-web-archive@optimus.ietf.org>; Sun, 23 Feb 2003 22:01:29 -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 VAA18952 for <sipping-emergency-web-archive@ietf.org>; Sun, 23 Feb 2003 21:52:38 -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 h1O31Sp09717 for <sipping-emergency-web-archive@ietf.org>; Sun, 23 Feb 2003 22:01:28 -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 h1O2wcp09583 for <sipping-emergency@optimus.ietf.org>; Sun, 23 Feb 2003 21:58:38 -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 VAA18903 for <sipping-emergency@ietf.org>; Sun, 23 Feb 2003 21:49:47 -0500 (EST)
Received: from cisco.com (171.71.177.223) by halt-in.cisco.com with ESMTP; 23 Feb 2003 18:54:02 -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 SAA10976; Sun, 23 Feb 2003 18:53:37 -0800 (PST)
Message-Id: <4.3.2.7.2.20030223205206.0215a410@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sun, 23 Feb 2003 20:53:44 -0600
To: Henning Schulzrinne <hgs@cs.columbia.edu>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [Sipping-emergency] Re: Emergency-req: remarks 1-4
Cc: sipping-emergency@ietf.org
In-Reply-To: <3E5912B3.40301@cs.columbia.edu>
References: <4.3.2.7.2.20030223114348.022b5640@localhost> <4.3.2.7.2.20030222120157.024467d0@localhost> <3E55EA9F.FB3489BB@lmf.ericsson.se> <4.3.2.7.2.20030217161831.047e6110@localhost> <3E516A89.90901@cs.columbia.edu> <3E55EA9F.FB3489BB@lmf.ericsson.se> <4.3.2.7.2.20030222120157.024467d0@localhost> <4.3.2.7.2.20030223114348.022b5640@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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>

At 01:28 PM 2/23/2003 -0500, Henning Schulzrinne wrote:
>>There are several installations that use HFC as primary line. They are
>
>We're still not connecting. HFC might well be used for regular 
>telecommunications subscribers, but the 'last-mile' model is constrained 
>to the case that the PSAP uses IP access, while the emergency callers only 
>use regular PSTN, however they get there.

now I understand your direction....


>>installed in most of the largest cities in the US. The products are from 
>>Arris (co-owned by Nortel at one time, I use to work on the Nortel team 
>>of that partnership several years ago). Dallas/Fort Worth (where I am) 
>>has had the opportunity to convert over to HFC and off wire-pairs for 
>>more than a year for my primary phone service. The provider is a little 
>>company called AT&T. The business goal of AT&T is to penetrate all the 32 
>>NFL cities (their term).
>>At the MSO Headend, there is connectivity to a Class 5 switch (either 
>>co-located, or feed to it). Thus, this MSO might be quite a ways outside 
>>of the PSAP jurisdiction (likely not 100 miles in AT&T's case in the near 
>>term - but we are talking about years from now also)
>
>That's all true and important for the end-to-end model, but completely 
>irrelevant to the last-mile model.

noted (knowing now the direction you are referring to).

BTW - I'm fine with all your other responses to the listed comments and 
questions.



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


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