TS
Click on the red underlined text to get to the source
... Internet Standards Process fall into
one of two categories: Technical Specification (TS) and
Applicability Statement (AS ...
... Technical Specification (TS) ...
... the relevant aspects of its subject, or it may leave one or more
parameters or options unspecified. A TS may be completely self-
contained, or it may incorporate material from other specifications
by reference to other documents (which might or might not be Internet
Standards ...
...
A TS shall include a statement of its scope and the general intent
for its use (domain of applicability). Thus, a TS ...
... TS shall include a statement of its scope and the general intent
for its use (domain of applicability). Thus, a TS that is inherently
specific to a particular context shall contain a statement to that
...
... specific to a particular context shall contain a statement to that
effect. However, a TS does not specify requirements for its use
within the Internet ...
... requirements, which depend on the
particular context in which the TS is incorporated by different
system configurations, are defined by an Applicability Statement.
...
... 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 ...
... ranges
of TS parameters or subfunctions of a TS protocol that must be
implemented. An AS also specifies the circumstances in which the use
...
... 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 ...
... AS may not have a higher maturity level in the standards track
than any standards-track TS on which the AS relies (see section 4.1).
For example, a TS ...
... TS on which the AS relies (see section 4.1).
For example, a TS at Draft Standard level may be referenced by an AS
...
...
(a) Required: Implementation of the referenced TS, as specified by
the AS, is required to achieve minimal conformance. For example,
...
... TCP/IP Protocol Suite.
(b) Recommended: Implementation of the referenced TS is not
required for minimal conformance, but experience and/or generally
accepted technical wisdom suggest its desirability in the domain ...
... from remote access.
(c) Elective: Implementation of the referenced TS is optional
within the domain of applicability of the AS ...
... AS
creates no explicit necessity to apply the TS. However, a
particular vendor may decide to implement it, or a particular user
...
... these TSs:
(d) Limited Use: The TS is considered to be appropriate for use
only in limited or unique circumstances. For example, the usage
of a protocol with the "Experimental ...
... be limited to those actively involved with the experiment.
(e) Not Recommended: A TS that is considered to be inappropriate
for general use is labeled "Not Recommended". This may be because
of its limited functionality, specialized nature, or historic
...
... hosts, often contain within a
single specification all of the relevant AS and TS information. In
such cases, no useful purpose would be served by deliberately
distributing the information among several documents just to preserve
...
... distributing the information among several documents just to preserve
the formal AS/TS distinction. However, a TS that is likely to apply
to more than one domain ...
... the formal AS/TS distinction. However, a TS that is likely to apply
to more than one domain of applicability should be developed in a
...
...
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
detailed descriptions of the requirement levels ...
...
An Internet Standard TS or AS may incorporate an open external
standard by reference. For example, many Internet Standards ...
... TS ...