vendor
Click on the red underlined text to get to the source
... Internet-Draft *
* be referenced by any paper, report, or Request- *
* for-Proposal, nor should a vendor claim compliance *
* with an Internet-Draft. *
...
... domain
of applicability of the AS. Vendors are strongly encouraged to
include the functions, features, and protocols of Recommended TSs
in their products, and should omit them only if the omission is
...
... creates no explicit necessity to apply the TS. However, a
particular vendor may decide to implement it, or a particular user
may decide that it is a necessity in a specific environment. For
example, the DECNET ...
... Draft Standard is normally considered to be a final specification,
and changes are likely to be made only to solve specific problems
encountered. In most circumstances, it is reasonable for vendors to
deploy implementations of Draft Standards into a disruption sensitive
environment.
...
... they were a "standards". Such a specification is not generally
developed in an open fashion, is typically proprietary, and is
controlled by the vendor, vendors, or organization that produced
it.
...
... developed in an open fashion, is typically proprietary, and is
controlled by the vendor, vendors, or organization that produced
it.
...
... IESG generally should not favor a particular proprietary
specification over technically equivalent and competing
specification(s) by making any incorporated vendor specification
"required" or "recommended".
...