[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Ecrit] Proposal to add "applicability" statementto -framework/-phonebcp
- To: Richard Barnes <rbarnes at bbn.com>, "Dawson, Martin" <Martin.Dawson at andrew.com>
- Subject: Re: [Ecrit] Proposal to add "applicability" statementto -framework/-phonebcp
- From: Randall Gellens <randy at qualcomm.com>
- Date: Tue, 24 Mar 2009 10:44:29 -0700
- Cc: "Rosen, Brian" <Brian.Rosen at neustar.biz>, ecrit at ietf.org
- Delivered-to: ecrit at core3.amsl.com
- Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=randy at qualcomm.com; q=dns/txt; s=qcdkim; t=1237916875; x=1269452875; h=message-id:in-reply-to:references:x-mailer: x-message-note:date:to:from:subject:cc:mime-version: content-type:x-random-sig-tag:x-ironport-av; z=Message-ID:=20<p06240613c5eecbc4f0b3 at [172.28.176.165]> |In-Reply-To:=20<49C91795.9030208 at bbn.com>|References:=20 <C80ADC57CB3BB64B94A9954A816306C5014FE6D7 at STNTEXCH11.cis. neustar.com>=0D=0A=20<EB921991A86A974C80EAFA46AD428E1E055 D7F05 at aopex4.andrew.com>=0D=0A=20<49C91795.9030208 at bbn.co m>|X-Mailer:=20Eudora=20for=20Mac=20OS=20X |X-message-Note:=20Warning:=20Outlook=20in=20use.=20=20Up grade=20to=20Eudora:=20<http://www.eudora.com>|Date:=20Tu e,=2024=20Mar=202009=2010:44:29=20-0700|To:=20Richard=20B arnes=20<rbarnes at bbn.com>,=0D=0A=20=20=20=20=20=20=20=20" Dawson,=20Martin"=0D=0A=09<Martin.Dawson at andrew.com> |From:=20Randall=20Gellens=20<randy at qualcomm.com> |Subject:=20Re:=20[Ecrit]=20Proposal=20to=20add=20"applic ability"=20=09statementto=0D=0A=20-framework/-phonebcp |CC:=20"Rosen,=20Brian"=20<Brian.Rosen at neustar.biz>,=20<e crit at ietf.org>,=0D=0A=20=20=20=20=20=20=20=20<drage at alcat el-lucent.com>|MIME-Version:=201.0|Content-Type:=20text/p lain=3B=20charset=3D"us-ascii"=3B=20format=3Dflowed |X-Random-Sig-Tag:=201.0b28|X-IronPort-AV:=20E=3DMcAfee =3Bi=3D"5300,2777,5563"=3B=20a=3D"16542488"; bh=ser0mEN9qYKE2biPmqvATebvcJWnaVDPvXQBtgb/B0Y=; b=D8mdX+VRDwwz5BgRP9vGlmwT/wqOqm1fdVcL4V1xG4AIgBPAm8yJVeNR B/ohTUvddIHfWzjI0slpYaPs/uib0U8eU5Lrd40dcLsNWWck9A6Y71ZmN xiFUWbGJSfnDpdP33LAXwPiVWVaT7o+8tQ6nhX8dF1Q1uY7Ono4HajNeC g=;
- In-reply-to: <49C91795.9030208 at bbn.com>
- List-archive: <http://www.ietf.org/mail-archive/web/ecrit>
- List-help: <mailto:ecrit-request@ietf.org?subject=help>
- List-id: <ecrit.ietf.org>
- List-post: <mailto:ecrit@ietf.org>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
- References: <C80ADC57CB3BB64B94A9954A816306C5014FE6D7 at STNTEXCH11.cis.neustar.com> <EB921991A86A974C80EAFA46AD428E1E055D7F05 at aopex4.andrew.com> <49C91795.9030208 at bbn.com>
At 10:25 AM -0700 3/24/09, Richard Barnes wrote:
This document describes an architecture for emergency calling in
the typical Internet environment, in which the calling device bears
most of the burden of implementing emergency calls, and the
caller's Internet Service Provider has a supporting role. The
underlying specifications allow for the network to take a more
expansive role in emergency calls, but such cases (and any
associated issues) are not covered extensively in this document;
rather, they are left for future study in other documents.
How about adding a sentence along the lines of what Keith proposed
during the meeting, which, if I understood correctly, would be
something like: "Note that this is one framework for placing
emergency calls. Other frameworks may exist, and there is no
guarantee that an entity implementing this framework will be able to
interoperate with an entity using a different framework."
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly selected tag: ---------------
There is something fascinating about science. One gets such
wholesale returns of conjecture out of such a trifling investment
of fact. --Mark Twain