[email protected]
[Top] [All Lists]

Re: [Ecrit]EmergencyContextRoutingofInternetTechnologies-ArchitectureCon

Subject: Re: [Ecrit]EmergencyContextRoutingofInternetTechnologies-ArchitectureConsiderations
From: Henning Schulzrinne
Date: Fri, 09 Sep 2005 20:44:55 -0400
Abbott, Nadine B wrote:

However, this IS a very complex problem, and the comments below seem to
be a pragmatic recognition that it may be a lot simpler for the
enterprise to supply its roaming members with IP devices that are
capable of automatically acquiring and passing location, than to support
the mechanisms necessary to acquire location information remotely on
their behalf. (Not to mention how much simpler it would also make life
for the Internet access providers.)

Not to mention issues of privacy - the Internet service provider has no clue that this is an emergency call and it seems rather difficult for some random hotel 802.11 provider to recognize hundreds of thousands of businesses, many of them in a different country than that provider, to make sure that this is indeed a legitimate request.

If the requirement is that emergency calls should be able to be
originated remotely via VPNs through an enterprise and that accurate
location information must be available to route the call, then there are
various solutions that can meet this requirement and these solutions
place varying degrees of responsibility on the enterprise and its IP
devices (with only a few possible examples sketched above).  It seems to
me that the enterprise that supports the VPN is the entity in the best
position to take ownership of the problem.  I think that maybe this is
not so much tailoring the requirement as it is an acknowledgment that
some solutions may be better than others in meeting the requirement?

At least some of the VPN software can be configured not to route "random" (non-corporate) Internet addresses via the VPN at all. This makes some sense - there is little benefit of visiting the web page of some outfit by tromboning or hairpinning (to use the PSTN equivalents) via the corporate campus. Maybe such configurations will become more common, given these difficulties (or OS will support the ability to select the non-VPN interface explicitly when opening a socket.)

I might suggest a clarification to the requirement, e.g.,
If an emergency call is originated remotely via a VPN through an
enterprise network, the enterprise shall ensure that accurate location
information for the caller is made available to route the call.

I do not think that this tailors the requirement to a particular
solution, but it does identify responsibility for the solution and makes
use of a VPN for this purpose conditional upon implementation of a

Ecrit mailing list
[email protected]

<Prev in Thread] Current Thread [Next in Thread>