Re: [Ecrit] Emergency calling without endpoint/VSP location support

[Marc Linsner <mlinsner at cisco.com>]

I agree with Ted on this, why is this an IETF/ECRIT problem?

The IETF has offered a solution, the sooner it's deployed the faster this
problem goes away.

Let's concentrate on phonebcp, framework, and location conveyance.

-Marc-


On 11/21/08 2:57 PM, "Ted Hardie" <hardie at qualcomm.com> wrote:

> At 5:20 PM -0800 11/20/08, Richard Barnes wrote:
>> 
>> The solution above is *obviously* a hack, because step 2 involves a lot
>> of uncertainty on any reasonable scale.  However, the problem it
>> addresses is real, especially in the short term: How should a VSP route
>> a call if endpoints don't support location?  (Likewise, how should a
>> PSAP get location if VSPs and endpoints don't support location?)
>> 
>> In order to address this problem, some sort of IP-to-location mapping
>> will be required.
> 
> Is there a reason this requires an IETF standard, though?  There are
> existing solutions for this, many of the commercial.  Without standardized
> access
> to the *data* mapping IP to Location, a protocol developed here looks
> to be a complete no-op, as it runs parallel to the providers' own
> access protocol into the proprietary database.
> 
> Is there anyone suggesting that the folks actually doing this work
> want to have access to multiple data sources in some standardized
> way?  Maybe more to the point, is there anybody claiming that the
> people who develop databases in this arena are willing to support this?
> 
> I know I was pretty blunt at the mic about this, and I don't want to
> appear rude.  But I really don't see the need for this to be an ECRIT/IETF
> effort, even if these interim systems are being deployed.
> regards,
> Ted
> _______________________________________________
> Ecrit mailing list
> Ecrit at ietf.org
> https://www.ietf.org/mailman/listinfo/ecrit


_______________________________________________
Ecrit mailing list
Ecrit at ietf.org
https://www.ietf.org/mailman/listinfo/ecrit