IETF Logo Mail Archive

Re: [Ecrit] PhoneBCP

Randall Gellens <randy@qualcomm.com> Tue, 28 April 2009 21:10 UTC

Return-Path: <randy@qualcomm.com>
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 BC5D33A6D00 for <ecrit@core3.amsl.com>; Tue, 28 Apr 2009 14:10:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.876
X-Spam-Level:
X-Spam-Status: No, score=-104.876 tagged_above=-999 required=5 tests=[AWL=0.265, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 5lOcP4mQEOBp for <ecrit@core3.amsl.com>; Tue, 28 Apr 2009 14:10:34 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id A1E823A6C21 for <ecrit@ietf.org>; Tue, 28 Apr 2009 14:10:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=randy@qualcomm.com; q=dns/txt; s=qcdkim; t=1240953116; x=1272489116; 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<p06240615c61d1f6977b2@[172.28.171.53]> |In-Reply-To:=20<BLU137-W272F3CA08488458EDF988A936E0@phx. gbl>|References:=20<C6177BF4.147ED%mlinsner@cisco.com><p0 624080dc617d32a1604@[10.227.68.1=0D=0A=2032]>=09<49F27637 .7050201@bbn.com>=0D=0A=20<E51D5B15BFDEFD448F90BDD17D41CF F104A3430A@AHQEX1.andrew.com>=0D=0A=20<058701c9c5d0$53c5e f40$fb51cdc0$@net>=0D=0A=20<E51D5B15BFDEFD448F90BDD17D41C FF104A3430B@AHQEX1.andrew.com>=0D=0A=20<28B7C3AA2A7ABA4A8 41F11217ABE78D67590BD8E@FRMRSSXCHMBSB3.dc-m.alcatel-=0D =0A=20lucent.com>=09<p0624060ac61bfca58f3b@[172.28.171.53 ]>=0D=0A=20<49F6891E.7080706@bbn.com>=20<p06240612c61ce42 88752@[172.28.171.53]>=20=0D=0A=20<49F74082.2080804@bbn.c om>=0D=0A=20<BLU137-W272F3CA08488458EDF988A936E0@phx.gbl> |X-Mailer:=20Eudora=20for=20Mac=20OS=20X|X-message-Note: =20Warning:=20Outlook=20in=20use.=20=20Upgrade=20to=20Eud ora:=20<http://www.eudora.com>|Date:=20Tue,=2028=20Apr=20 2009=2014:08:44=20-0700|To:=20Bernard=20Aboba=20<bernard_ aboba@hotmail.com>,=20<rbarnes@bbn.com>|From:=20Randall =20Gellens=20<randy@qualcomm.com>|Subject:=20Re:=20[Ecrit ]=20PhoneBCP|CC:=20<ecrit@ietf.org>|MIME-Version:=201.0 |Content-Type:=20text/html=3B=20charset=3D"us-ascii" |X-Random-Sig-Tag:=201.0b28|X-IronPort-AV:=20E=3DMcAfee =3Bi=3D"5300,2777,5599"=3B=20a=3D"17562993"; bh=vEYl/a7yRgqtwl3EL6RNp8hV11VqTdjrH9q+dfawrWM=; b=YXDc/FX00LNxbOyDGpqQ2Abo3MALLJpJCK3RA0a34Ii0rzKzT+6JDsLP e0Y5Ez/QWihT8L4Glk/LGf6Iw55eV6AlWVmDxV0G2Plm69Ik4bvkViDem RsIMuE1dJFAJDir+wLE2PTxpPJ6K0W9ocoYLyMIK7H8QxK7KDA2Domj6J 0=;
X-IronPort-AV: E=McAfee;i="5300,2777,5599"; a="17562993"
Received: from pdmz-ns-mip.qualcomm.com (HELO numenor.qualcomm.com) ([199.106.114.10]) by wolverine01.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 28 Apr 2009 14:11:54 -0700
Received: from msgtransport05.qualcomm.com (msgtransport05.qualcomm.com [129.46.61.150]) by numenor.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n3SLBrMT019242 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 28 Apr 2009 14:11:54 -0700
Received: from nasanexhub03.na.qualcomm.com (nasanexhub03.na.qualcomm.com [10.46.93.98]) by msgtransport05.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n3SLBnHS002080 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 28 Apr 2009 14:11:49 -0700
Received: from nasanexmsp02.na.qualcomm.com (10.45.56.203) by nasanexhub03.na.qualcomm.com (10.46.93.98) with Microsoft SMTP Server (TLS) id 8.1.358.0; Tue, 28 Apr 2009 14:11:49 -0700
Received: from [172.28.171.53] (10.46.82.6) by qcmail1.qualcomm.com (10.45.56.203) with Microsoft SMTP Server (TLS) id 8.1.340.0; Tue, 28 Apr 2009 14:11:48 -0700
Message-ID: <p06240615c61d1f6977b2@[172.28.171.53]>
In-Reply-To: <BLU137-W272F3CA08488458EDF988A936E0@phx.gbl>
References: <C6177BF4.147ED%mlinsner@cisco.com><p0624080dc617d32a1604@[10.227.68.1 32]> <49F27637.7050201@bbn.com> <E51D5B15BFDEFD448F90BDD17D41CFF104A3430A@AHQEX1.andrew.com> <058701c9c5d0$53c5ef40$fb51cdc0$@net> <E51D5B15BFDEFD448F90BDD17D41CFF104A3430B@AHQEX1.andrew.com> <28B7C3AA2A7ABA4A841F11217ABE78D67590BD8E@FRMRSSXCHMBSB3.dc-m.alcatel- lucent.com> <p0624060ac61bfca58f3b@[172.28.171.53]> <49F6891E.7080706@bbn.com> <p06240612c61ce4288752@[172.28.171.53]> <49F74082.2080804@bbn.com> <BLU137-W272F3CA08488458EDF988A936E0@phx.gbl>
X-Mailer: Eudora for Mac OS X
X-message-Note: Warning: Outlook in use. Upgrade to Eudora: <http://www.eudora.com>
Date: Tue, 28 Apr 2009 14:08:44 -0700
To: Bernard Aboba <bernard_aboba@hotmail.com>, rbarnes@bbn.com
From: Randall Gellens <randy@qualcomm.com>
MIME-Version: 1.0
Content-Type: text/html; charset="us-ascii"
X-Random-Sig-Tag: 1.0b28
Cc: ecrit@ietf.org
Subject: Re: [Ecrit] PhoneBCP
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: Tue, 28 Apr 2009 21:10:35 -0000

Re: [Ecrit] PhoneBCP
At 11:55 AM -0700 4/28/09, Bernard Aboba wrote:

Rather, we need to figure out what the purpose of the statement is, and what problem it is trying to solve.

The phonebcp and framework documents are unusual in that they make very broad claims to cover all emergency calls over IP.  Since there are other mechanisms that are likely to be used in some environments,  it's important to clarify that while these documents describe a solution they do not describe these other environments nor interoperbility with solutions used in those environments.

Per the definition of an applicability statement, all of phonebcp can be considered to be one.

 RFC 2026 Section 3.2 describes the purpose of applicability statements as follows:
3.2  Applicability Statement (AS)

   An Applicability Statement specifies how, and under what
   circumstances, one or more TSs may be applied to support a particular
   Internet capability.  An AS may specify uses for TSs that are not
   Internet Standards, as discussed in Section 7.

   An AS identifies the relevant TSs and the specific way in which they
   are to be combined, and may also specify particular values or ranges
   of TS parameters or subfunctions of a TS protocol that must be
   implemented.  An AS also specifies the circumstances in which the use
   of a particular TS is required, recommended, or elective (see section
   3.3).


--
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Television is simply automated day-dreaming.
      --Lee Lovinger, _Quote_, July 30, 1967

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