IETF
Click on the red underlined text to get to the source
...
The Internet Engineering Task Force (IETF) is a loosely self-
organized group of people who make technical and other
...
... specifications, although it is not itself a part of the
Internet Society. The IETF is composed of individual Working
Groups, which are grouped into Areas, each of which is
coordinated by one or more Area Directors ...
... Internet Engineering
Steering Group are made by a nominating committee selected at
random from the ranks of regular IETF meeting attendees who
have volunteered to serve as nominating committee members.
...
... Internet
Architecture Board from among the nominees submitted by the
IETF nominating committee.
...
... IESG) is responsible
for technical management of IETF activities and the Internet
Standards process. As part of the Internet Society, it
...
... Internet Standards. The IESG
is composed of the IETF Area Directors and the chairperson of
the IETF ...
... IETF Area Directors and the chairperson of
the IETF, who also serves as the chairperson of the IESG.
...
... Any member of the Internet community with the time and interest is
urged to participate actively in one or more IETF Working Groups
and to attend IETF meetings. In many cases, active ...
... urged to participate actively in one or more IETF Working Groups
and to attend IETF meetings. In many cases, active Working Group
...
... remote participation. Participation is by individual technical
contributors rather than formal representatives of organizations.
The process works because the IETF Working Groups display a spirit
of cooperation as well as a high degree of technical maturity;
IETF participants ...
... IETF Working Groups display a spirit
of cooperation as well as a high degree of technical maturity;
IETF participants recognize that the greatest benefit for all
members of the Internet community results from cooperative
...
... committee that is drawn from the roll of recent participation in
the IETF and chartered by the ISOC Board of Trustees. The
appointment of IESG ...
... considered for Internet standardization, the specification is
processed through the IETF using the rules in this document.
...
... draft versions of
the document are made available for informal review and comment
by placing them in the IETF's "Internet Drafts" directory,
which is replicated on a number of Internet ...
... Internet grows, there is a growing amount of credible
technical work being submitted directly to the RFC Editor without
having been gone through the IETF. It is possible that such
outside submissions may overlap or even conflict with ongoing IETF
...
... having been gone through the IETF. It is possible that such
outside submissions may overlap or even conflict with ongoing IETF
activities. In order for the best technical result to emerge for
the community, we believe that the such outside submissions should
...
... activities. In order for the best technical result to emerge for
the community, we believe that the such outside submissions should
be given the opportunity to work within IETF to gain the broadest
possible consensus.
...
...
It is also possible that supporters of a view different from the
IETF may wish to publish their divergent view. For this reason,
it is important that, ultimately, authors should have the
opportunity to publish Informational and Experimental RFCs ...
... they wish to. However, it is also possible that this could open a
loophole in which developers could try to bypass the IETF
consensus process completely by publishing an Informational RFC
(and relying on the prestige of the RFC series to gain community
...
... Informational and Experimental submissions that the RFC
Editor feels may be related to, or of interest to, the IETF
community.
2. The IESG ...
... IESG will review all such referrals within a fixed length
of time and make a recommendation on whether to publish, or
to suggest that the author bring their work within the IETF.
3. If the IESG ...
... 3. If the IESG recommends that the work be brought within the
IETF, but the author declines the invitation, the IESG may
add disclaimer text into the standard boilerplate material
...
...
Typically, a standards action is initiated by a recommendation
to the appropriate IETF Area Director by the individual or
group ...
... group that is responsible for the specification, usually an
IETF Working Group.
After completion to the satisfaction of its author and the
...
...
The IESG shall communicate its findings to the IETF to permit a
final review by the general Internet community. This "last-
...
... call" notification shall be via electronic mail to the IETF
mailing list. In addition, for important specifications there
...
... shall be a presentation or statement by the appropriate Working
Group or Area Director during an IETF plenary meeting. Any
significant issues that have not been resolved satisfactorily
during the development of the specification may be raised at
...
... In a timely fashion, but no sooner than two weeks after issuing
the last-call notification to the IETF mailing list, the IESG
...
... IESG
shall make its final determination on whether or not to approve
the standards action, and shall notify the IETF of its decision
via email.
...
...
(a) an ISOC-sponsored effort (typically an IETF Working Group),
(b) independent activity by individuals, or
...
... Case (a) accounts for the great majority of specifications that
enter the standards track. In cases (b) and (c), the work might
be tightly integrated with the work of an existing IETF Working
Group, or it might be offered for standardization without prior
IETF involvement. In most cases, a specification resulting from
...
... be tightly integrated with the work of an existing IETF Working
Group, or it might be offered for standardization without prior
IETF involvement. In most cases, a specification resulting from
an effort that took place outside of an IETF Working Group will be
...
... IETF involvement. In most cases, a specification resulting from
an effort that took place outside of an IETF Working Group will be
submitted to an appropriate Working Group for evaluation and
...
... small to require the formality of Working Group creation. It is
the responsibility of the appropriate IETF Area Director to
determine what, if any, review of an external specification is
...
... A specification shall remain at the Draft Standard level for at
least four (4) months, or until at least one IETF meeting has
occurred, whichever comes later.
...
... IESG shall approve termination or
continuation of the development. This decision shall be
communicated to the IETF via electronic mail to the IETF mailing
list ...
... communicated to the IETF via electronic mail to the IETF mailing
list, to allow the Internet community an opportunity to comment.
...
...
IETF Working Groups are generally able to reach consensus, which
sometimes requires difficult compromises between differing
technical solutions. However, there are times when even
...
... IESG, with the relevant Area Director or the IETF Chair being
tasked with communicating results of the discussion.
...
... opportunities for explicit comment. (1) When appropriate, a
specification that is being suggested for advancement along the
standards track will be presented during an IETF plenary. At that
time, IETF participants may choose to raise issues with the
...
... standards track will be presented during an IETF plenary. At that
time, IETF participants may choose to raise issues with the
plenary or to pursue their issues privately, with any of the
relevant IETF ...
... IETF participants may choose to raise issues with the
plenary or to pursue their issues privately, with any of the
relevant IETF/IESG management personnel. (2) Specifications that
...
... are to be considered by the IESG are publicly announced to the
IETF mailing list, with a request for comments.
...
...
Many standards groups other than the IETF create and publish
standards documents for network protocols ...
... (c) Assumption
An IETF Working Group may start from an external specification
and develop it into an Internet ...
... requirements of section 5 below, and (2)
change control has been conveyed to IETF by the original
developer of the specification. Continued participation in the
IETF ...
... IETF by the original
developer of the specification. Continued participation in the
IETF work by the original owner is likely to be valuable, and is
encouraged.
...
... contribution as provided herein. Except as provided below, the
Executive Director of the IETF Secretariat, or a person
designated by the Executive Director, will be responsible for
...
... obtaining written confirmations.
In the case of IETF Working Groups, the responsibility for
identifying the principal contributor(s) for purposes of
...
... contributor(s) will generally be requested to provide written
confirmation, it is the responsibility of all contributors to
standards work to inform the IETF Secretariat of any
proprietary claims in any contributions and to furnish the
Secretariat with any required confirmation.
...
... standard. A copy of this assurance may be obtained from
the Executive Director of the IETF Secretariat. The
Internet Society takes no position on the validity ...
... resolution concerning a standards action under the rules of Section
3.1.2. If it were necessary to extend the time for some reason,
the IETF would have to be explicitly notified.
o Bug Reporting
...