Internet
Click on the red underlined text to get to the source
...
This memo documents the process currently used by the Internet
community for the standardization of protocols and procedures. The
Internet Standards process is an activity of the Internet Society ...
... This memo documents the process currently used by the Internet
community for the standardization of protocols and procedures. The
Internet Standards process is an activity of the Internet Society
that is organized and managed on behalf of the Internet community ...
... Internet
community for the standardization of protocols and procedures. The
Internet Standards process is an activity of the Internet Society
that is organized and managed on behalf of the Internet community by
...
... Internet Standards process is an activity of the Internet Society
that is organized and managed on behalf of the Internet community by
the Internet Architecture Board (IAB ...
... that is organized and managed on behalf of the Internet community by
the Internet Architecture Board (IAB) and the Internet Engineering
Steering Group (IESG ...
... Internet Standards ...
...
The Internet, a loosely-organized international collaboration of
autonomous, interconnected networks, supports host-to-host ...
... host-to-host
communication through voluntary adherence to open protocols and
procedures defined by Internet Standards. There are also many
isolated interconnected networks, which are not connected to the
...
... isolated interconnected networks, which are not connected to the
global Internet but use the Internet Standards.
...
...
The Internet Standards Process described in this document is
concerned with all protocols, procedures, and conventions that are
used in or by the Internet ...
... Internet Standards Process described in this document is
concerned with all protocols, procedures, and conventions that are
used in or by the Internet, whether or not they are part of the
TCP/IP protocol suite. In the case of protocols developed and/or
...
... TCP/IP protocol suite. In the case of protocols developed and/or
standardized by non-Internet organizations, however, the Internet
Standards Process normally applies to the application of the protocol
or procedure in the Internet ...
... TCP/IP protocol suite. In the case of protocols developed and/or
standardized by non-Internet organizations, however, the Internet
Standards Process normally applies to the application of the protocol
or procedure in the Internet context ...
... Internet organizations, however, the Internet
Standards Process normally applies to the application of the protocol
or procedure in the Internet context, not to the specification of the
protocol itself.
...
...
In general, an Internet Standard is a specification that is stable
and well-understood, is technically competent, has multiple,
...
... independent, and interoperable implementations with substantial
operational experience, enjoys significant public support, and is
recognizably useful in some or all parts of the Internet.
...
... The Internet Standards Process ...
...
In outline, the process of creating an Internet Standard is
straightforward: a specification undergoes a period of development
and several iterations of review by the Internet community ...
... Internet Standard is
straightforward: a specification undergoes a period of development
and several iterations of review by the Internet community and
revision based upon experience, is adopted as a Standard by the
appropriate body (see below), and is published. In practice, the
...
... establishing widespread community consensus; and (4) the difficulty
of evaluating the utility of a particular specification for the
Internet community.
...
...
The goals of the Internet Standards Process are:
...
... These procedures are intended to provide a fair, open, and
objective basis for developing, evaluating, and adopting Internet
Standards. They provide ample opportunity for participation and
comment by all interested parties. At each stage of the
standardization process, a specification is repeatedly discussed
...
... interoperability by multiple independent parties and utilized in
increasingly demanding environments, before it can be adopted as
an Internet Standard.
...
... parties to comment all require significant time and effort. On the
other hand, today's rapid development of networking technology
demands timely development of standards. The Internet Standards
Process is intended to balance these conflicting goals. The process
is believed to be as short and simple as possible without sacrificing
technical excellence, thorough testing before adoption of a standard,
...
...
From its inception, the Internet has been, and is expected to remain,
an evolving system whose participants regularly factor new
requirements ...
... requirements and technology into its design and implementation. Users
of the Internet and providers of the equipment, software, and
services that support it should anticipate and embrace this evolution
...
... services that support it should anticipate and embrace this evolution
as a major tenet of Internet philosophy.
...
... The procedures described in this document are the result of a number
of years of evolution, driven both by the needs of the growing and
increasingly diverse Internet community, and by experience.
...
...
Section 2 describes the publications and archives of the Internet
Standards Process. Section 3 describes the types of Internet
standard specifications. Section 4 describes the Internet standards
...
... Section 2 describes the publications and archives of the Internet
Standards Process. Section 3 describes the types of Internet
standard specifications. Section 4 describes the Internet standards
specifications track. Section 5 describes Best Current Practice ...
... archives of the Internet
Standards Process. Section 3 describes the types of Internet
standard specifications. Section 4 describes the Internet standards
specifications track. Section 5 describes Best Current Practice
...
... specifications track. Section 5 describes Best Current Practice
RFCs. Section 6 describes the process and rules for Internet
standardization. Section 7 specifies the way in which externally-
sponsored specifications and practices, developed and controlled by
...
... standardization. Section 7 specifies the way in which externally-
sponsored specifications and practices, developed and controlled by
other standards bodies or by others, are handled within the Internet
Standards Process. Section 8 describes the requirements for notices
and record keeping Section 9 defines a variance process to allow
...
... intellectual property rights in the context of the development and
use of Internet Standards. Section 11 includes acknowledgments of
some of the people involved in creation of this document. Section 12
notes that security issues ...
... INTERNET STANDARDS-RELATED PUBLICATIONS ...
...
Each distinct version of an Internet standards-related specification
is published as part of the "Request for Comments" (RFC) document
series. This archival series is the official publication channel ...
... series. This archival series is the official publication channel for
Internet standards documents and other publications of the IESG, IAB,
...
... and Internet community. RFCs can be obtained from a number of
Internet hosts using anonymous FTP, gopher ...
... acronyms). RFCs cover a wide range of
topics in addition to Internet Standards, from early discussion of
new research concepts to status memos about the Internet ...
... Internet Standards, from early discussion of
new research concepts to status memos about the Internet. RFC
publication is the direct responsibility of the RFC Editor, under the
general direction of the IAB ...
...
The status of Internet protocol and service specifications is
summarized periodically in an RFC entitled "Internet Official
Protocol Standards ...
... Internet protocol and service specifications is
summarized periodically in an RFC entitled "Internet Official
Protocol Standards" [1]. This RFC shows the level of maturity and
other helpful information for each Internet protocol ...
... Internet Official
Protocol Standards" [1]. This RFC shows the level of maturity and
other helpful information for each Internet protocol or service
specification (see section 3).
...
...
Some RFCs document Internet Standards. These RFCs form the 'STD'
subseries of the RFC series [4 ...
... subseries of the RFC series [4]. When a specification has been
adopted as an Internet Standard, it is given the additional label
"STDxxx", but it keeps its RFC number and its place in the RFC
series. (see section 4.1.3)
...
...
Not all specifications of protocols or services for the Internet
should or will become Internet Standards or BCPs ...
... services for the Internet
should or will become Internet Standards or BCPs. Such non-standards
track specifications are not subject ...
... BCPs. Such non-standards
track specifications are not subject to the rules for Internet
standardization. Non-standards track specifications may be published
directly as "Experimental ...
... * are standards track documents, and that not all *
* standards track documents reach the level of *
* Internet Standard. In the same way, not all RFCs *
* which describe current practices have been given *
* the review and approval to become BCPs ...
... Internet-Drafts ...
... 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 hosts ...
... IETF's "Internet-Drafts" directory, which is
replicated on a number of Internet hosts. This makes an evolving
working document readily available to a wide audience, facilitating
...
...
An Internet-Draft that is published as an RFC, or that has remained
unchanged in the Internet-Drafts directory for more than six months
...
... An Internet-Draft that is published as an RFC, or that has remained
unchanged in the Internet-Drafts directory for more than six months
without being recommended by the IESG for publication as an RFC, is
...
... IESG for publication as an RFC, is
simply removed from the Internet-Drafts directory. At any time, an
Internet-Draft may be replaced by a more recent version ...
... removed from the Internet-Drafts directory. At any time, an
Internet-Draft may be replaced by a more recent version of the same
specification, restarting ...
...
An Internet-Draft is NOT a means of "publishing" a specification;
specifications are published through the RFC mechanism described in
the previous section. Internet-Drafts ...
... Internet-Draft is NOT a means of "publishing" a specification;
specifications are published through the RFC mechanism described in
the previous section. Internet-Drafts have no formal status, and are
subject to change or removal at any time.
...
... ********************************************************
* *
* Under no circumstances should an Internet-Draft *
* be referenced by any paper, report, or Request- *
* for-Proposal, nor should a vendor ...
... * for-Proposal, nor should a vendor claim compliance *
* with an Internet-Draft. *
* *
********************************************************
...
... that may reasonably be expected to be published as an RFC using the
phrase "Work in Progress" without referencing an Internet-Draft.
This may also be done in a standards track document itself as long
as the specification in which the reference is made would stand as a
...
... INTERNET STANDARD SPECIFICATIONS ...
...
Specifications subject to the Internet Standards Process fall into
one of two categories: Technical Specification (TS ...
... TS may be completely self-
contained, or it may incorporate material from other specifications
by reference to other documents (which might or might not be Internet
Standards).
...
... TS does not specify requirements for its use
within the Internet; these requirements, which depend on the
particular context ...
... Applicability Statement specifies how, and under what
circumstances, one or more TSs may be applied to support a particular
Internet capability. An AS may specify uses for TSs that are not
Internet Standards ...
... Internet capability. An AS may specify uses for TSs that are not
Internet Standards, as discussed in Section 7.
...
... requirements document", for a particular class of
Internet systems, such as Internet routers or Internet ...
... THE INTERNET STANDARDS TRACK ...
...
Specifications that are intended to become Internet Standards evolve
through a set of maturity levels known as the "standards track".
These maturity levels -- "Proposed Standard ...
...
Even after a specification has been adopted as an Internet Standard,
further evolution often occurs based on experience and the
recognition of new requirements ...
... recognition of new requirements. The nomenclature and procedures of
Internet standardization provide for the replacement of old Internet
...
... requirements. The nomenclature and procedures of
Internet standardization provide for the replacement of old Internet
...
...
Standards with new ones, and the assignment of descriptive labels to
indicate the status of "retired" Internet Standards. A set of
maturity levels is defined in section 4.2 to cover these and other
specifications that are not considered to be on the standards track.
...
...
Internet specifications go through stages of development, testing,
and acceptance. Within the Internet Standards Process, these stages
...
... Internet specifications go through stages of development, testing,
and acceptance. Within the Internet Standards Process, these stages
are formally labeled "maturity levels".
...
... prior to granting Proposed Standard status to a specification that
materially affects the core Internet protocols or that specifies
behavior that may have significant operational impact on the
Internet ...
... Internet protocols or that specifies
behavior that may have significant operational impact on the
Internet.
...
... Working Group chair is responsible for documenting the specific
implementations which qualify the specification for Draft or Internet
Standard status along with documentation about testing of the
interoperation of these implementations. The documentation must
include information about the support of each of the individual
...
... Internet Standard ...
... A specification for which significant implementation and successful
operational experience has been obtained may be elevated to the
Internet Standard level. An Internet Standard (which may simply be
referred to as a Standard) is characterized by a high degree of
...
... operational experience has been obtained may be elevated to the
Internet Standard level. An Internet Standard (which may simply be
referred to as a Standard) is characterized by a high degree of
technical maturity and by a generally held belief that the specified
...
... technical maturity and by a generally held belief that the specified
protocol or service provides significant benefit to the Internet
community.
...
...
Not every specification is on the standards track. A specification
may not be intended to be an Internet Standard, or it may be intended
for eventual standardization but not yet ready to enter the standards
track. A specification may have been superseded by a more recent
...
... for eventual standardization but not yet ready to enter the standards
track. A specification may have been superseded by a more recent
Internet Standard, or have otherwise fallen into disuse or disfavor.
...
... Experimental",
"Informational", or "Historic". The documents bearing these labels
are not Internet Standards in any sense.
...
... Experimental" designation typically denotes a specification that
is part of some research or development effort. Such a specification
is published for the general information of the Internet technical
community and as an archival record of the work, subject only to
...
... adequate coordination with the standards process (see below). An
Experimental specification may be the output of an organized Internet
research effort (e.g., a Research Group of the IRTF ...
...
An "Informational" specification is published for the general
information of the Internet community, and does not represent an
Internet community consensus or recommendation. The Informational
...
... information of the Internet community, and does not represent an
Internet community consensus or recommendation. The Informational
designation is intended to provide for the timely publication of a
very broad range ...
...
Specifications that have been prepared outside of the Internet
community and are not incorporated into the Internet Standards
Process by any of the provisions of section 10 may be published as
Informational RFCs, with the permission of the owner and the
...
...
Specifications that have been prepared outside of the Internet
community and are not incorporated into the Internet Standards
Process by any of the provisions of section 10 may be published as
Informational RFCs, with the permission of the owner and the
concurrence of the RFC Editor.
...
... Experimental or Informational status
should be submitted directly to the RFC Editor. The RFC Editor will
publish any such documents as Internet-Drafts which have not already
been so published. In order to differentiate these Internet-Drafts
...
... publish any such documents as Internet-Drafts which have not already
been so published. In order to differentiate these Internet-Drafts
they will be labeled or grouped in the I-D directory so they are
easily recognizable. The RFC Editor will wait two weeks after this
...
... Experimental or
Informational status, and may refuse to publish a document which, in
the expert opinion of the RFC Editor, is unrelated to Internet
activity or falls below the technical and/or editorial standard for
RFCs.
...
... To ensure that the non-standards track Experimental and Informational
designations are not misused to circumvent the Internet Standards
Process, the IESG and the RFC Editor have agreed that the RFC Editor
will refer to the IESG ...
... published as originally submitted or referred to the IETF as a
contribution to the Internet Standards Process.
...
...
Historically Internet standards have generally been concerned with
the technical specifications for hardware ...
... computer communication across interconnected networks. However,
since the Internet itself is composed of networks operated by a great
variety of organizations, with diverse goals and rules, good user
...
... service requires that the operators and administrators of the
Internet follow some common guidelines for policies and operations.
While these guidelines are generally different in scope and style
from protocol standards, their establishment needs a similar process
...
... IETF, it is also recognized that the entities
themselves have an existence as leaders in the community. As leaders
in the Internet technical community, these entities should have an
outlet to propose ideas to stimulate work in a particular area, to
raise the community's sensitivity to a certain issue, to make a
...
... THE INTERNET STANDARDS PROCESS ...
...
The mechanics of the Internet Standards Process involve decisions of
the IESG concerning the elevation of a specification onto the
...
...
A specification that is intended to enter or advance in the Internet
standards track shall first be posted as an Internet-Draft (see
section 2.2) unless it has not changed since publication as an RFC.
...
...
A specification that is intended to enter or advance in the Internet
standards track shall first be posted as an Internet-Draft (see
section 2.2) unless it has not changed since publication as an RFC.
It shall remain as an Internet-Draft ...
... Internet-Draft (see
section 2.2) unless it has not changed since publication as an RFC.
It shall remain as an Internet-Draft for a period of time, not less
than two weeks, that permits useful community review, after which a
recommendation for action may be initiated.
...
... the IESG to be extremely important in terms of its potential impact
on the Internet or on the suite of Internet protocols, the IESG may,
...
... IESG to be extremely important in terms of its potential impact
on the Internet or on the suite of Internet protocols, the IESG may,
at its discretion, commission an independent technical review of the
...
... IESG
consideration of the document(s) to permit a final review by the
general Internet community. This "Last-Call" notification shall be
via electronic mail ...
... specification as an RFC. The specification shall at that point be
removed from the Internet-Drafts directory.
...
...
An official summary of standards actions completed and pending shall
appear in each issue of the Internet Society's newsletter. This
shall constitute the "publication of record" for Internet standards
...
... appear in each issue of the Internet Society's newsletter. This
shall constitute the "publication of record" for Internet standards
actions.
...
...
The RFC Editor shall publish periodically an "Internet Official
Protocol Standards" RFC [1], summarizing the status of all Internet
protocol and service ...
... The RFC Editor shall publish periodically an "Internet Official
Protocol Standards" RFC [1], summarizing the status of all Internet
protocol and service specifications.
...
...
When a standards-track specification has not reached the Internet
Standard level but has remained at the same maturity level for
twenty-four (24) months, and every twelve (12) months thereafter
until the status is changed, the IESG ...
... IETF Announce mailing list to allow the Internet community an
opportunity to comment. This provision is not intended to threaten a
legitimate and active ...
...
A new version of an established Internet Standard must progress
through the full Internet standardization process as if it were a
...
... version of an established Internet Standard must progress
through the full Internet standardization process as if it were a
completely new specification. Once the new version has reached the
...
... will be moved to Historic status. However, in some cases both
versions may remain as Internet Standards to honor the requirements
of an installed base. In this situation, the relationship between
...
... discussion. This
section specifies the procedures that shall be followed to deal with
Internet standards issues that cannot be resolved through the normal
processes whereby IETF Working Groups and other Internet Standards
Process ...
... Internet standards issues that cannot be resolved through the normal
processes whereby IETF Working Groups and other Internet Standards
Process participants ordinarily reach consensus.
...
... The IAB decision is final with respect to the question of whether or
not the Internet standards procedures have been followed and with
respect to all questions of technical merit.
...
... This document sets forward procedures required to be followed to
ensure openness and fairness of the Internet Standards Process, and
the technical viability of the standards created. The IESG ...
... The IAB decision is final with respect to the question of whether or
not the Internet standards procedures have been followed.
...
... themselves (i.e., the procedures described in this document) are
claimed to be inadequate or insufficient to the protection of the
rights of all parties in a fair and open Internet Standards Process.
Claims on this basis may be made to the Internet Society Board of
Trustees ...
... rights of all parties in a fair and open Internet Standards Process.
Claims on this basis may be made to the Internet Society Board of
Trustees. The President of the Internet Society shall acknowledge
...
... Claims on this basis may be made to the Internet Society Board of
Trustees. The President of the Internet Society shall acknowledge
such an appeal within two weeks, and shall at the time of
acknowledgment advise the petitioner of the expected duration of the
...
... [NOTE: These procedures intentionally and explicitly do not
establish a fixed maximum time period that shall be considered
"reasonable" in all cases. The Internet Standards Process places a
premium on consensus and efforts to achieve it, and deliberately
foregoes deterministically swift execution of procedures in favor of
...
... services. When these
external specifications play an important role in the Internet, it is
desirable to reach common agreements on their usage -- i.e., to
...
... desirable to reach common agreements on their usage -- i.e., to
establish Internet Standards relating to these external
specifications.
...
... concerned with the practical application of their standards. All
of these are considered to be "open external standards" for the
purposes of the Internet Standards Process.
(2) Other Specifications
...
...
Other proprietary specifications that have come to be widely used
in the Internet may be treated by the Internet community as if
they were a "standards". Such a specification is not generally
...
... Other proprietary specifications that have come to be widely used
in the Internet may be treated by the Internet community as if
they were a "standards". Such a specification is not generally
developed in an open fashion, is typically proprietary, and is
...
... To avoid conflict between competing versions of a specification, the
Internet community will not standardize a specification that is
simply an "Internet version ...
... Internet community will not standardize a specification that is
simply an "Internet version" of an existing external specification
unless an explicit cooperative arrangement to do so has been made.
...
... unless an explicit cooperative arrangement to do so has been made.
However, there are several ways in which an external specification
that is important for the operation and/or evolution of the Internet
may be adopted for Internet use.
...
... that is important for the operation and/or evolution of the Internet
may be adopted for Internet use.
...
... TS or AS may incorporate an open external
standard by reference. For example, many Internet Standards
incorporate by reference the ANSI standard character set ...
... IETF Working Group may start from an external specification and
develop it into an Internet specification. This is acceptable if (1)
the specification is provided to the Working Group in compliance with
...
...
Each of the organizations involved in the development and approval of
Internet Standards shall publicly announce, and shall maintain a
publicly accessible record of, every activity in which it engages, to
the extent that the activity represents the prosecution of any part
...
... publicly accessible record of, every activity in which it engages, to
the extent that the activity represents the prosecution of any part
of the Internet Standards Process. For purposes of this section, the
organizations involved in the development and approval of Internet
Standards includes the IETF ...
... of the Internet Standards Process. For purposes of this section, the
organizations involved in the development and approval of Internet
Standards includes the IETF, the IESG, the IAB ...
...
As a practical matter, the formal record of all Internet Standards
Process activities is maintained by the IETF Secretariat, and is the
responsibility of the IETF Secretariat ...
... IETF Secretariat with complete and
accurate minutes of all Working Group meetings. Internet-Drafts that
have been removed (for any reason) from the Internet-Drafts ...
... Internet-Drafts that
have been removed (for any reason) from the Internet-Drafts
directories shall be archived by the IETF Secretariat for the sole
...
... directories shall be archived by the IETF Secretariat for the sole
purpose of preserving an historical record of Internet standards
activity and thus are not retrievable except in special
circumstances.
...
...
This document, which sets out the rules and procedures by which
Internet Standards and related documents are made is itself a product
of the Internet Standards Process (as a BCP ...
... Internet Standards and related documents are made is itself a product
of the Internet Standards Process (as a BCP, as described in section
5). It replaces a previous version ...
... of the proper and correct process to follow, and requirements to be
met, to allow for the best possible Internet Standards and BCPs, it
cannot be assumed that this will always remain the case. From time to
...
... IESG
may approve such a variance, however, only if it first determines
that the likely benefits to the Internet community are likely to
outweigh any costs to the Internet community that result from
...
... that the likely benefits to the Internet community are likely to
outweigh any costs to the Internet community that result from
noncompliance with the requirements in this document. In exercising
...
... IESG shall at least consider (a) the technical
merit of the specification, (b) the possibility of achieving the
goals of the Internet Standards Process without granting a variance,
(c) alternatives to the granting of a variance, (d) the collateral
and precedential effects of granting a variance, and (e) the IESG's ...
... limit the scope of the variance to particular parts of this document
and to impose such additional restrictions or limitations as it
determines appropriate to protect the interests of the Internet
community.
...
... IESG's considerations including
consideration of points (a) through (d) in the previous paragraph.
The proposed variance shall be issued as an Internet Draft. The IESG
shall then issue an extended Last-Call, of no less than 4 weeks, to
...
... In all matters of intellectual property rights and procedures, the
intention is to benefit the Internet community and the public at
large, while respecting the legitimate rights of others.
...
... confidentiality
or any restriction on its dissemination may be considered in any part
of the Internet Standards Process, and there must be no assumption of
any confidentiality obligation with respect to any such contribution.
...
...
By ratifying this description of the IETF process the Internet
Society warrants that it will not inhibit the traditional open and
free access to IETF documents for which license ...
... license and right have
been assigned according to the procedures set forth in this
section, including Internet-Drafts and RFCs. This warrant is
perpetual and will not be revoked by the Internet Society or its
...
... section, including Internet-Drafts and RFCs. This warrant is
perpetual and will not be revoked by the Internet Society or its
successors or assigns.
...
... of such rights, a written assurance that upon approval by the IESG
of the relevant Internet standards track specification(s), any
party will be able to obtain the right to implement, use and
distribute the technology or works when implementing, using or
...
... technology has been fulfilled in practice. It will instead use the
normal requirements for the advancement of Internet Standards to
verify that the terms for use are reasonable. If the two unrelated
implementations of the specification that are required to advance
...
... attention, at the earliest possible time, the existence of any
intellectual property rights pertaining to Internet Standards.
For this purpose, each standards document shall include the
following invitation:
...
... ISOC standards-related documentation:
"Copyright (C) The Internet Society (date). All Rights
Reserved.
...
... not be modified in any way, such as by removing the copyright
notice or references to the Internet Society or other Internet
organizations, except as needed for the purpose of developing
...
... removing the copyright
notice or references to the Internet Society or other Internet
organizations, except as needed for the purpose of developing
Internet standards ...
... Internet
organizations, except as needed for the purpose of developing
Internet standards in which case the procedures for copyrights
defined in the Internet Standards process must be followed, or
...
... Internet standards in which case the procedures for copyrights
defined in the Internet Standards process must be followed, or
as required to translate it into languages other than English.
...
...
The limited permissions granted above are perpetual and will
not be revoked by the Internet Society or its successors or
assigns.
...
... This document and the information contained herein is provided
on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR
...
... on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE
OF THE INFORMATION ...
... Postel, J., "Internet Official Protocol Standards", STD 1, USC/Information Sciences Institute, March 1996. ...
... Area Directors
along with the IETF Chair comprise the Internet Engineering
Steering Group (IESG). ...
... Internet Architecture Board (IAB) ...
... Internet Engineering Steering Group (IESG) ...
... Relating to information made available over the Internet.
When referenced in this document material is said to be online
when it is retrievable without restriction or undue fee using
...
... When referenced in this document material is said to be online
when it is retrievable without restriction or undue fee using
standard Internet applications such as anonymous FTP, gopher or
...
... Internet Architecture Board ...
... Internet Engineering Task Force ...
... Internet Protocol ...
... Internet Research Steering Group ...
... Internet Research Task Force ...
... Internet Society ...