IETF
Click on the red underlined text to get to the source
... IESG and MUST correspond to a formal publication by a
recognized standards body. In the case of registration for the IETF
itself, the registration proposal MUST be published as an RFC.
...
... specifically permitted. However, the restrictions set forth in
[RFC2026] on the use of patented technology in IETF standards-track
protocols must be respected when the specification of a media type is
...
... media types registered in the standards tree by the
IETF itself MUST be published as RFCs. RFC publication of vendor and
personal media type ...
... data type does not imply endorsement, approval, or
recommendation by the IANA or the IETF or even certification that the
specification is adequate. To become Internet Standards ...
... Internet Standards, a protocol
or data object must go through the IETF standards process. This is
too difficult and too lengthy a process for the convenient
registration ...
... applicability
statements for particular applications will be published from time to
time in the IETF, recommending implementation of, and support for,
media types that have proven particularly useful in those contexts ...
... community comment and sanity checking without excessive time delay.
The normal IETF processes should be followed for all IETF
registrations ...
...
The normal IETF processes should be followed for all IETF
registrations in the standards tree ...
... media
types reviewer. The media types reviewer, who is appointed by the
IETF Applications Area Director(s), will review the registration to
...
... standards tree MUST satisfy the additional
requirement that they originate from the IETF itself or from another
standards body recognized as such by the IETF.
...
... requirement that they originate from the IETF itself or from another
standards body recognized as such by the IETF.
...
... operational experience with these procedures.
o The unfaceted IETF tree is now called the standards tree, and the
...
...
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights ...
...
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license ...
... such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
...
... http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
...
... rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
...