Re: [Sip-implementors] [Sip] SIPit 20 survey summary

Hannes Tschofenig <Hannes.Tschofenig@gmx.net> Mon, 14 May 2007 10:33 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HnXry-0007PW-BV; Mon, 14 May 2007 06:33:34 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1HnXrv-0007PR-T5 for sip-confirm+ok@megatron.ietf.org; Mon, 14 May 2007 06:33:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HnXrv-0007PJ-JQ for sip@ietf.org; Mon, 14 May 2007 06:33:31 -0400
Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HnXru-0002Ng-66 for sip@ietf.org; Mon, 14 May 2007 06:33:31 -0400
Received: (qmail invoked by alias); 14 May 2007 10:33:28 -0000
Received: from socks1.netz.sbs.de (EHLO [192.35.17.26]) [192.35.17.26] by mail.gmx.net (mp002) with SMTP; 14 May 2007 12:33:28 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX197lo8oN/l7LulH44uRqCD+RC0CjV6ouNqo8BItrJ r5GxvEN39Cq90e
Message-ID: <46483AF6.9070702@gmx.net>
Date: Mon, 14 May 2007 12:33:26 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: Klaus Darilion <klaus.mailinglists@pernau.at>
Subject: Re: [Sip-implementors] [Sip] SIPit 20 survey summary
References: <075001c788fc$9f6a2be0$640fa8c0@cis.neustar.com> <001401c78976$5f8dc020$0601a8c0@BEMBUSTER> <2296E180-5F91-40B0-876A-7806949C7689@e-c-group.com> <46480E39.1010805@pernau.at>
In-Reply-To: <46480E39.1010805@pernau.at>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: discussion@sipforum.org, IETF SIP List <sip@ietf.org>, Robert Sparks <rjsparks@estacado.net>, Juha Heinanen <jh@tutpro.com>, sip-implementors@cs.columbia.edu
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

Hi Klaus,

no matter how you call it but there will always be a (VoIP) application 
service provider involved in the emergency services case.
I guess you refer to the SIM-less emergency services case (or 
unauthenticated emergency network access scenario) where the access 
network provider (ASP and/or ISP) also needs to be the (VoIP) 
application service provider.

Ciao
Hannes

Klaus Darilion wrote:
>
>
> Mark R. Lindsey wrote:
>> It is much more reasonable to expect the service-provider/enterprise 
>> to implement the location conveyance. They'd add the location in 
>> their proxies/B2BUAs/ALGs. For example, an enterprise building ALG 
>> could add its location before sending the call to an SP.
>
> What if there is no service provider at all? SIP phones may perform 
> emergency calls on there own - without the need of a service provider. 
> Otherwise - if your service provider is down - you can't make 
> emergency calls.
>
> regards
> klaus
>
>
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip



_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip