requirement
Click on the red underlined text to get to the source
...
The goal of technical competence, the requirement for prior
implementation and testing, and the need to allow all interested
parties to comment all require significant time and effort. On the
...
... Internet has been, and is expected to remain,
an evolving system whose participants regularly factor new
requirements and technology into its design and implementation. Users
of the Internet and providers of the equipment, software, and
...
... sponsored specifications and practices, developed and controlled by
other standards bodies or by others, are handled within the Internet
Standards Process. Section 8 describes the requirements for notices
and record keeping Section 9 defines a variance process to allow
one-time exceptions to some of the requirements ...
... requirements for notices
and record keeping Section 9 defines a variance process to allow
one-time exceptions to some of the requirements in this document
Section 10 presents the rules that are required to protect
intellectual property rights ...
... *********************************************************
* *
* A stricter requirement applies to standards-track *
* specifications: the ASCII ...
... context shall contain a statement to that
effect. However, a TS does not specify requirements for its use
within the Internet; these requirements ...
... requirements for its use
within the Internet; these requirements, which depend on the
particular context in which the TS ...
... The broadest type of AS is a comprehensive conformance specification,
commonly called a "requirements document", for a particular class of
Internet ...
... Requirement Levels ...
...
An AS shall apply one of the following "requirement levels" to each
of the TSs to which it refers:
...
... standards track or that have been retired from the standards
track, and are therefore not required, recommended, or elective.
Two additional "requirement level" designations are available for
these TSs:
...
...
The "Official Protocol Standards" RFC (STD1) lists a general
requirement level for each TS, using the nomenclature defined in this
section. This RFC is updated periodically. In many cases, more
...
... TS, using the nomenclature defined in this
section. This RFC is updated periodically. In many cases, more
detailed descriptions of the requirement levels of particular
protocols and of individual features of the protocols will be found
in appropriate ASs.
...
... Internet Standard,
further evolution often occurs based on experience and the
recognition of new requirements. The nomenclature and procedures of
Internet standardization provide for the replacement of old Internet ...
... A Proposed Standard should have no known technical omissions with
respect to the requirements placed upon it. However, the IESG may
waive this requirement ...
... requirements placed upon it. However, the IESG may
waive this requirement in order to allow a specification to advance
to the Proposed Standard state ...
...
The requirement for at least two independent and interoperable
implementations applies to all of the options and features of the
specification. In cases in which one or more options or features
...
... versions may remain as Internet Standards to honor the requirements
of an installed base. In this situation, the relationship between
the previous and the new versions ...
... a version of the specification as long as the proprietor meets the
requirements of section 10. If the other proprietary specification
is not widely and readily available, the IESG may request that it be
...
... the specification is provided to the Working Group in compliance with
the requirements of section 10, and (2) change control has been
conveyed to IETF ...
...
While, when published, this document represents the community's view
of the proper and correct process to follow, and requirements to be
met, to allow for the best possible Internet Standards and BCPs ...
... IESG may enter a particular specification into, or
advance it within, the standards track even though some of the
requirements of this document have not or will not be met. The IESG
may approve such a variance, however, only if it first determines
...
... outweigh any costs to the Internet community that result from
noncompliance with the requirements in this document. In exercising
this discretion, the IESG shall at least consider (a) the technical
...
...
No use of this procedure may lower any specified delays, nor exempt
any proposal from the requirements of openness, fairness, or
consensus, nor from the need to keep proper records of the meetings
...
...
No contribution that is subject to any requirement of confidentiality
or any restriction on its dissemination may be considered in any part
...
... of reasonable and non-discriminatory terms for the use of a
technology has been fulfilled in practice. It will instead use the
normal requirements for the advancement of Internet Standards to
verify that the terms for use are reasonable. If the two unrelated
...