IETF
Click on the red underlined text to get to the source
... some of which include review in the Internet Engineering Task Force
(IETF), and some of which include approval by the Internet
Engineering Steering Group (IESG):
...
... WG) to Standards Track: Includes WG consensus,
review in the IETF, IETF Last Call, and IESG approval
...
... Area Director (AD) sponsored to Standards Track: Includes review
in the IETF, IETF Last Call, and IESG approval
...
... AD) sponsored to Standards Track: Includes review
in the IETF, IETF Last Call, and IESG approval
...
... AD Sponsored Individual to Experimental/Informational: Includes
some form of review in the IETF and IESG approval
...
... model. The new review model will have the IESG take responsibility
ONLY for checking for conflicts between the work of the IETF and the
documents submitted; soliciting technical review is deemed to be the
responsibility of the RFC Editor. If an individual IESG member ...
... AD may suggest that an author submit a document as input for work
within the IETF rather than to the RFC Editor, or the IESG may
suggest that a document submitted to the IETF ...
... IETF rather than to the RFC Editor, or the IESG may
suggest that a document submitted to the IETF is better suited for
submission to the RFC Editor but these interactions are not described
in this memo.
...
... publication, the RFC Editor asks the IESG to review the documents for
conflicts with the IETF standards process or work done in the IETF
community.
...
... IESG to review the documents for
conflicts with the IETF standards process or work done in the IETF
community.
The review is initiated by a note from the RFC Editor specifying the
...
...
2. The IESG thinks that this work is related to IETF work done in WG
<X>, but this does not prevent publishing.
...
...
3. The IESG thinks that publication is harmful to the IETF work done
in WG <X> and recommends not publishing the document at this time.
...
...
4. The IESG thinks that this document violates IETF procedures for
<X> and should therefore not be published without IETF review and
...
... IESG thinks that this document violates IETF procedures for
<X> and should therefore not be published without IETF review and
IESG approval.
...
...
5. The IESG thinks that this document extends an IETF protocol in a
way that requires IETF review and should therefore not be
...
... IESG thinks that this document extends an IETF protocol in a
way that requires IETF review and should therefore not be
published without IETF review and IESG approval ...
... way that requires IETF review and should therefore not be
published without IETF review and IESG approval.
...
... The last two responses are included respectively, for the case where
a document attempts to take actions (such as registering a new URI
scheme) that require IETF consensus or IESG approval (as these terms
are defined in RFC 2434 ...
... are defined in RFC 2434 [2]), and for the case where an IETF protocol
is proposed to be changed or extended in an unanticipated way that
may be harmful to the normal usage of the protocol, but where the
...
... protocol documents do not explicitly say that this type of extension
requires IETF review.
If a document requires IETF ...
... IETF review.
If a document requires IETF review, the IESG will offer the author
the opportunity to ask for publication as an AD ...
... Note that if the IESG has not found any conflict between a submission
and IETF work, then judging its technical merits, including
considerations of possible harm to the Internet, will become the
...
...
1. For documents that specify a protocol or other technology, and
that have been considered in the IETF at one time:
The content of this RFC was at one time considered by the IETF ...
... IETF at one time:
The content of this RFC was at one time considered by the IETF,
and therefore it may resemble a current IETF work in progress ...
... The content of this RFC was at one time considered by the IETF,
and therefore it may resemble a current IETF work in progress or a
published IETF ...
... IETF work in progress or a
published IETF work. This RFC is not a candidate for any level of
Internet Standard ...
... candidate for any level of
Internet Standard. The IETF disclaims any knowledge of the
fitness of this RFC for any purpose and in particular notes that
the decision to publish is not based on IETF ...
... IETF disclaims any knowledge of the
fitness of this RFC for any purpose and in particular notes that
the decision to publish is not based on IETF review for such
things as security, congestion control ...
...
2. For documents that specify a protocol or similar technology and
are independent of the IETF process:
This RFC is not a candidate ...
... candidate for any level of Internet Standard.
The IETF disclaims any knowledge of the fitness of this RFC for
any purpose and in particular notes that the decision to publish
is not based on IETF ...
... IETF disclaims any knowledge of the fitness of this RFC for
any purpose and in particular notes that the decision to publish
is not based on IETF review for such things as security,
congestion control ...
... candidate for any level of Internet Standard.
The IETF disclaims any knowledge of the fitness of this RFC for
any purpose and notes that the decision to publish is not based on
IETF ...
... IETF disclaims any knowledge of the fitness of this RFC for
any purpose and notes that the decision to publish is not based on
IETF review apart from IESG review for conflict with IETF work.
...
... IETF review apart from IESG review for conflict with IETF work.
The RFC Editor has chosen to publish this document at its
discretion. See RFC 3932 ...
... This section gives a couple of examples where delaying or preventing
publication of a document might be appropriate due to conflict with
IETF work. It forms part of the background material, not a part of
the procedure.
...
... WG product published first,
and have the non-adopted document published later, with a clear
disclaimer note saying that "the IETF technology for this function is
X".
...
... series is appropriate for. That is a matter for discussion in the
IETF community.
...
... range of organized discussions within the
IETF about potential adjustments to the IETF document publication
processes (e.g., NEWTRK working group ...
... discussions within the
IETF about potential adjustments to the IETF document publication
processes (e.g., NEWTRK working group) and recognizes that the
...
... processes (e.g., NEWTRK working group) and recognizes that the
process described in this document, as well as other general IETF
publication processes, may need to be adjusted in the light of the
outcome of those discussions ...
... thanks for their contributions.
This document has been reviewed in the IETF and by the RFC Editor and
the IAB; the IAB ...
... to John Klensin, Keith Moore, Pete Resnick, Scott Bradner, Kurt
Zeilenga, Eliot Lear, Paul Hoffman, Brian Carpenter, and all other
IETF community members who provided valuable feedback on the
document.
...
...
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights ...
... might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the IETF's procedures with respect to rights in IETF Documents can
be found in BCP 78 ...
... made any independent effort to identify any such rights. Information
on the IETF's procedures with respect to rights in IETF Documents can
be found in BCP 78 and BCP 79 ...
...
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.
...