IETF
Click on the red underlined text to get to the source
...
This document specifies a middle-ground approach to the system of
making changes to IETF process, one that relies heavily on a "propose
and carry out an experiment, evaluate the experiment, and then
establish permanent procedures based on operational experience" model
...
...
Since the 1992 changes documented in [RFC1396], the IETF has used two
mechanisms for process changes.
...
... a lightweight mechanism for change, but the lightness came with a
cost: There was sometimes too little alignment with the larger
IETF community.
2. The IETF ...
... IETF community.
2. The IETF has also used the [RFC2026] protocol standards
development process to identify a community of interest, hold one
...
... or more BoFs, charter a working group, discuss proposed changes
within the community, develop IETF-wide consensus on the changes,
and publish (usually) Best Current Practice specifications. This
...
... Best Current Practice specifications. This
provided full community involvement but also came with a cost in
flexibility. The IETF does not change its formal processes often
(the IPR clarifications in [RFC3667 ...
... 2. If the IESG believes the proposal is plausible and plausibly
useful, a four-week IETF Last Call is initiated. The IESG can
institute whatever procedures it wishes to make this determination
...
... any experience to back it up.
Nothing above is to be construed as requiring an IETF-wide attempt
for any given process experiment. A proposal for such an experiment
may specify selected areas, selected working groups ...
...
This document specifies a mechanism for evolving IETF procedures. It
does not raise or consider any protocol-specific security issues ...
... Harald Alvestrand, and from discussions with the General Area
Directorate and at its open meeting during IETF 59. After mailing
list discussion, considerable explanatory material was removed ...
... Bradner, S., "Intellectual Property Rights in IETF Technology", BCP 79, RFC 3668(-> 3979), February 2004. ...
...
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.
...