The phonebcp and framework documents are unusual in that they make very broad claims to cover all emergency calls over IP.
I don't think that's true. From the Abstract and Introduction: "The IETF has standardized various aspects of placing emergency calls. This document describes how all of those component parts are used to support emergency calls from citizens and visitors to authorities.
...This document focuses on how devices using the Internet can place emergency calls and how PSAPs can handle Internet multimedia emergency calls natively.
"Note the use of the word "can" (and we can switch the "are" in the abstract to "can" if that makes things better). Could you provide a pointer to the text that leads you to a different interpretation?
Per the definition of an applicability statement, all of phonebcp can be considered to be one.
Technically speaking, that seems to be accurate, but irrelevant to the current discussion.
--Richard
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