Message-ID: <BLU137-W9848D2C6D7F5A86A39250936F0@phx.gbl>
Content-Type: multipart/alternative;
 boundary="_766509c7-c942-41a7-88f8-77d168f65240_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: <randy@qualcomm.com>
Date: Tue, 28 Apr 2009 19:31:57 -0700
Importance: Normal
In-Reply-To: <p06240615c61d1f6977b2@[172.28.171.53]>
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>
 <p06240615c61d1f6977b2@[172.28.171.53]>
MIME-Version: 1.0
Cc: ecrit@ietf.org
Subject: Re: [Ecrit] PhoneBCP
Precedence: list

--_766509c7-c942-41a7-88f8-77d168f65240_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


>Per the definition of an applicability statement=2C all of phonebcp can be=
 considered to be one.

=20

I think that is correct with respect to the "how" -- the document is all ab=
out how TSs may be applied.=20

=20

I'm not so sure about the "under what circumstances" part of it=2C though. =
 That seems to be the point under discussion. =20

=20

BTW=2C it is not only the cellular community that may have a point of view =
on that issue.  IEEE 802 has recently debated an Emergency Services PAR (se=
e http://www.ieee802.org/21/email21/msg02957.html) that has been somewhat c=
ontroversial. =20

=20

3.2  Applicability Statement (AS)

   An Applicability Statement specifies how=2C and under what
   circumstances=2C 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=2C as discussed in Section 7.

   An AS identifies the relevant TSs and the specific way in which they
   are to be combined=2C 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=2C recommended=2C or elective (see sectio=
n
   3.3).


 =

--_766509c7-c942-41a7-88f8-77d168f65240_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
</style>
</head>
<body class=3D'hmmessage'>
&gt=3BPer the definition of an applicability statement=2C all of phonebcp c=
an be considered to be one.<BR>
&nbsp=3B<BR>
I think that is correct with respect to the "how" -- the document is all ab=
out how TSs&nbsp=3Bmay be&nbsp=3Bapplied. <BR>
&nbsp=3B<BR>
I'm not so sure about the "under what circumstances" part of it=2C though.&=
nbsp=3B That seems to be the point under discussion.&nbsp=3B <BR>
&nbsp=3B<BR>
BTW=2C&nbsp=3Bit is not only the cellular community that may have a point o=
f view on that issue.&nbsp=3B IEEE 802 has recently&nbsp=3Bdebated an Emerg=
ency Services PAR (see <A href=3D"http://www.ieee802.org/21/email21/msg0295=
7.html">http://www.ieee802.org/21/email21/msg02957.html</A>) that has been =
somewhat controversial.&nbsp=3B <BR>
&nbsp=3B<BR>
<BLOCKQUOTE><TT>3.2&nbsp=3B Applicability Statement (AS)<BR><BR>&nbsp=3B&nb=
sp=3B An Applicability Statement specifies how=2C and under what<BR>&nbsp=
=3B&nbsp=3B circumstances=2C one or more TSs may be applied to support a pa=
rticular<BR>&nbsp=3B&nbsp=3B Internet capability.&nbsp=3B An AS may specify=
 uses for TSs that are not<BR>&nbsp=3B&nbsp=3B Internet Standards=2C as dis=
cussed in Section 7.<BR><BR>&nbsp=3B&nbsp=3B An AS identifies the relevant =
TSs and the specific way in which they<BR>&nbsp=3B&nbsp=3B are to be combin=
ed=2C and may also specify particular values or ranges<BR>&nbsp=3B&nbsp=3B =
of TS parameters or subfunctions of a TS protocol that must be<BR>&nbsp=3B&=
nbsp=3B implemented.&nbsp=3B An AS also specifies the circumstances in whic=
h the use<BR>&nbsp=3B&nbsp=3B of a particular TS is required=2C recommended=
=2C or elective (see section</TT></BLOCKQUOTE>
<BLOCKQUOTE><TT>&nbsp=3B&nbsp=3B 3.3).</TT></BLOCKQUOTE>
<DIV><BR></DIV>
<DIV><FONT color=3D#444444></FONT>&nbsp=3B</DIV></body>
</html>=

--_766509c7-c942-41a7-88f8-77d168f65240_--