IETF Logo Mail Archive

Re: [Ecrit] Emergency Call Framework for Canada; Questions on draft-ietf-ecrit-framework-09

Patrik Fältström <patrik@frobbit.se> Wed, 03 June 2009 05:09 UTC

Return-Path: <patrik@frobbit.se>
X-Original-To: ecrit@core3.amsl.com
Delivered-To: ecrit@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BC8883A6ED5 for <ecrit@core3.amsl.com>; Tue, 2 Jun 2009 22:09:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.118
X-Spam-Level:
X-Spam-Status: No, score=0.118 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jRW-ngTb9Rva for <ecrit@core3.amsl.com>; Tue, 2 Jun 2009 22:09:36 -0700 (PDT)
Received: from srv01.frobbit.se (srv01.frobbit.se [85.30.129.39]) by core3.amsl.com (Postfix) with ESMTP id AB4713A6E9E for <ecrit@ietf.org>; Tue, 2 Jun 2009 22:09:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by srv01.frobbit.se (Postfix) with ESMTP id 3C565566EE53; Wed, 3 Jun 2009 07:09:36 +0200 (CEST)
X-Virus-Scanned: amavisd-new at frobbit.se
Received: from srv01.frobbit.se ([127.0.0.1]) by localhost (srv01.frobbit.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Jz-fTOC3mBh; Wed, 3 Jun 2009 07:09:36 +0200 (CEST)
Received: from 79.138.146.123.bredband.tre.se (79.138.146.123.bredband.tre.se [79.138.146.123]) by srv01.frobbit.se (Postfix) with ESMTP id F1014566EE4C; Wed, 3 Jun 2009 07:09:34 +0200 (CEST)
Message-Id: <E89A2A58-D7C6-4AE5-BDD7-CD6A8A61171B@frobbit.se>
From: Patrik Fältström <patrik@frobbit.se>
To: John Lange <john@johnlange.ca>
In-Reply-To: <1243966386.4449.676.camel@vandium.darkcore.net>
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Apple-Mail-20--589398378"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 03 Jun 2009 07:09:33 +0200
References: <1243884311.17673.212.camel@vandium.darkcore.net> <XFE-SJC-212NPPzQT450000bbad@xfe-sjc-212.amer.cisco.com> <1243966386.4449.676.camel@vandium.darkcore.net>
X-Pgp-Agent: GPGMail d55 (v55, Leopard)
X-Mailer: Apple Mail (2.935.3)
Cc: ecrit <ecrit@ietf.org>
Subject: Re: [Ecrit] Emergency Call Framework for Canada; Questions on draft-ietf-ecrit-framework-09
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jun 2009 05:09:38 -0000

On 2 jun 2009, at 20.13, John Lange wrote:

> 1) Endpoint location discovery via DHCP is not going to work for
> residential so some other mechanism will need to be employed (and I
> think it should be STUN + DNS).

I think people should be careful with statements of the form "will not  
work for X". Much better to say "will not work in all situations" or  
"will not work if Y". Even "will not work for MANY deployments" is  
dangerous as I claim noone actually know what "many" implies in  
statements like that.

I know network deployments where location by DHCP will work extremely  
well.

I know location by DHCP will not work in some cases, and work in some.

    Patrik

v2.46.0 | Report a Bug | By Email | System Status