Re: [Ecrit] PhoneBCP

[Richard Barnes <[e-mail]>]

If the proposal is for an Applicability Statement in the sense of RFC 
2026, then I certainly vote against the proposition, for the reasons 
listed in the prior email.

Not to speak for the chairs, but my impression is that the intent was 
not to take such a limited definition, but rather to discuss adding some 
text to address concerns that had been raised.

Could the chairs clarify?

--Richard




Bernard Aboba wrote:
>> So one should not draw from the additional text in the latest draft that 
>> there are assumptions underlying the solution in this document that 
>> would prevent its applicability in some IP networks.  If that's how it 
>> is being interpreted, then we need to revise it again.
> 
> In the consensus call, the paragraph in question was described as an "applicability statement".   If you are saying that the intent of the paragraph was not to provide an indication of the applicability of the solution described in the document, then we have an issue that cannot be solved merely by revising the text.   Rather, we need to figure out what the purpose of the statement is, and what problem it is trying to solve.  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).
> 
>    An AS may describe particular methods of using a TS in a restricted
>    "domain of applicability", such as Internet routers, terminal
>    servers, Internet systems that interface to Ethernets, or datagram-
>    based database servers.
> 
>    The broadest type of AS is a comprehensive conformance specification,
>    commonly called a "requirements document", for a particular class of
>    Internet systems, such as Internet routers or Internet hosts.
> 
>