IETF
Click on the red underlined text to get to the source
... a. "IETF": In the context of this document, the IETF includes all
individuals who participate in meetings, working groups, mailing
lists ...
... IAB under the general
designation of the Internet Engineering Task Force or IETF, but
solely to the extent of such participation.
...
... solely to the extent of such participation.
b. "IETF Standards Process": the activities undertaken by the IETF in
any of the settings described in 1(c) below.
...
...
b. "IETF Standards Process": the activities undertaken by the IETF in
any of the settings described in 1(c) below.
...
... any of the settings described in 1(c) below.
c. "IETF Contribution": any submission to the IETF intended by the
Contributor for publication as all or part of an Internet-Draft ...
...
c. "IETF Contribution": any submission to the IETF intended by the
Contributor for publication as all or part of an Internet-Draft or
...
... RFC (except for RFC Editor Contributions described below) and any
statement made within the context of an IETF activity. Such
statements include oral statements in IETF sessions ...
... context of an IETF activity. Such
statements include oral statements in IETF sessions, as well as
written and electronic communications made at any time or place,
...
... IETF plenary session,
o any IETF working group or portion thereof,
o the IESG, or any member thereof on behalf of the IESG ...
... o any IETF mailing list, including the IETF list itself, any
working group or design team list, or any other list
...
... working group or design team list, or any other list
functioning under IETF auspices,
o the RFC Editor or the Internet-Drafts function (except for RFC
...
... Editor Contributions described below).
Statements made outside of an IETF session, mailing list or other
...
... session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF ...
... IETF
activity, group or function, are not IETF Contributions in the
context of this document.
...
...
d. "Internet-Draft": temporary documents used in the IETF and RFC
Editor processes. Internet-Drafts are posted on the IETF ...
... IETF and RFC
Editor processes. Internet-Drafts are posted on the IETF web site
by the IETF Secretariat ...
... IETF web site
by the IETF Secretariat and have a nominal maximum lifetime in the
Secretariat's public directory of 6 months, after which they are
...
... the expiration.
e. "RFC": the basic publication series for the IETF. RFCs are
published by the RFC Editor and once published are never modified.
(See [RFC2026 ...
... an Informational or Experimental RFC but not intended to be part
of the IETF Standards Process.
g. "IETF ...
... Internet-Drafts other than RFC Editor
Contributions. Note that under Section 3.3(a) the grant of rights
in regards to IETF Internet-Drafts as specified in this document
is perpetual and irrevocable and thus survives the Secretariat's
...
... RFC2026] Sections 2.2 and 8)
h. "IETF Documents": RFCs and Internet-Drafts except for Internet-
...
... Editor Contributions and the RFCs that may be published from them.
j. "Contribution": IETF Contributions and RFC Editor Contributions.
k. "Contributor": an individual submitting a Contribution.
...
... requirement. But this requirement should not be
interpreted as requiring the IETF Contributor or participant (or
his or her represented organization, if any) to perform a patent
search ...
... author retains them in all cases.)
This document details the rights that the IETF requires in IETF
Contributions and rights the IETF ...
...
This document details the rights that the IETF requires in IETF
Contributions and rights the IETF, as publisher ...
... Contributions.
In order for works to be used within the IETF Standards Process or to
be published as Internet-Drafts, certain limited rights in all
...
... be published as Internet-Drafts, certain limited rights in all
Contributions must be granted to the IETF and Internet Society
(ISOC ...
... Internet Society
(ISOC). In addition, Contributors must make representations to IETF
and ISOC regarding their ability to grant these rights. These
...
... there have been a number of times when the exact intent of Section 10
has been the subject of vigorous debate within the IETF community.
The aim of this document is to clarify various ambiguities in Section
10 of [RFC2026 ...
... 10 of [RFC2026] that led to these debates and to amplify the policy
in order to clarify what the IETF is currently doing.
Section 1 gives definitions used in describing these policies.
...
... Contributions previously covered by Section 10 of [RFC2026] and the
"Note Well" explanatory text presented at many IETF activities.
Sections 7 and 8 then explain the rationale for these provisions,
...
... RFC2026]. The rules and procedures set out in
this document are not intended to substantially modify or alter the
IETF's current policy toward Contributions.
A companion document [RFC3979 ...
... A companion document [RFC3979] deals with rights in technologies
developed or specified as part of the IETF Standards Process. This
document is not intended to address those issues.
...
...
o rights to make use of contributed material
o copyrights in IETF documents
o rights to produce derivative works
o rights to use trademarks
...
... to consult their own legal advisors if they would like a legal
interpretation of their rights or the rights of the IETF in any
Contributions they make.
...
... Rights in IETF Contributions ...
... confidentiality or any restriction on its dissemination may be
submitted as a Contribution or otherwise considered in any part of
the IETF Standards Process, and there must be no assumption of any
confidentiality obligation with respect to any Contribution. Each
...
... right and license to the ISOC and the IETF under all intellectual
property rights in the Contribution:
...
...
(A) to copy, publish, display, and distribute the Contribution as
part of the IETF Standards Process or in an Internet-Draft,
...
... works (other than translations) that are based on or
incorporate all or part of the Contribution, or comment upon
it, within the IETF Standards Process. The license to such
derivative works not granting the ISOC ...
... license to such
derivative works not granting the ISOC and the IETF any more
rights than the license to the original Contribution,
...
... with the reproduction, distribution or publication of the
Contribution and derivative works thereof as permitted by this
paragraph. When reproducing Contributions, the IETF will
preserve trademark and service mark identifiers ...
... (E) to extract, copy, publish, display, distribute, modify and
incorporate into other works, for any purpose (and not limited
to use within the IETF Standards Process) any executable code
or code fragments that are included in any IETF Document ...
... IETF Standards Process) any executable code
or code fragments that are included in any IETF Document (such
as MIB and PIB modules), subject ...
... RFC3979]).
b. The Contributor grants the IETF and ISOC permission to reference
the name(s) and address ...
... a. The Contribution properly acknowledges all major Contributors. A
major Contributor is any person who has materially or
substantially contributed to the IETF Contribution.
b. No information in the Contribution is confidential and the IETF ...
... IETF Contribution.
b. No information in the Contribution is confidential and the IETF,
ISOC, and its affiliated organizations may freely disclose any
...
...
The Contributor, and each named co-Contributor, acknowledges that the
IETF has no duty to publish or otherwise use or disseminate any
Contribution. The IETF reserves the right to withdraw or cease using
...
... IETF has no duty to publish or otherwise use or disseminate any
Contribution. The IETF reserves the right to withdraw or cease using
any Contribution that does not comply with the requirements of
...
...
Contributors, and each named co-Contributor, who claim trademark
rights in terms used in their IETF Contributions are requested to
state specifically what conditions apply to implementers ...
... world-wide right and license to the ISOC and the IETF under all
intellectual property rights in the RFC Editor Contribution for at
...
... license to such derivative works not
granting the ISOC and the IETF any more rights than the
license to the original RFC Editor Contribution, and
...
... of the RFC Editor Contribution and derivative works thereof as
permitted by this paragraph. When reproducing RFC Editor
Contributions, the IETF will preserve trademark and service
mark identifiers ...
... TM) and (R) where appropriate.
b. The Contributor grants the IETF and ISOC permission to reference
the name(s) and address ...
... Notices Required in IETF Documents ...
...
The IETF requires that certain notices and disclaimers described in
this Section 5 be reproduced verbatim in all IETF Documents
...
... The IETF requires that certain notices and disclaimers described in
this Section 5 be reproduced verbatim in all IETF Documents
(including copies, derivative works and translations of IETF
Documents, but subject ...
... this Section 5 be reproduced verbatim in all IETF Documents
(including copies, derivative works and translations of IETF
Documents, but subject to the limited exceptions noted in Section
5.2). This requirement ...
... subject to the limited exceptions noted in Section
5.2). This requirement protects IETF and its participants from
liabilities connected with these documents. The copyright notice
also alerts ...
... liabilities connected with these documents. The copyright notice
also alerts readers that the document is an IETF Document, and that
ISOC claims copyright rights to certain aspects of the document, such
...
... language of the document. This legend is not intended to imply that
ISOC has obtained ownership of the IETF Contribution itself, which is
retained by the author(s) or remains in the public domain, as
...
... applicable.
Each IETF Document must include the required notices described in
this Section 5. The required notices are the following:
...
... Internet-Drafts).
b. The Derivative Works Limitation described in Section 5.2 (for
specific IETF Documents only).
c. The Publication Limitation described in Section 5.3 (for specific
types of Internet-Drafts ...
... types of Internet-Drafts only).
d. The Copyright Notice described in Section 5.4 (for all IETF
Documents).
e. The Disclaimer described in Section 5.5 (for all IETF Documents).
...
... d. The Copyright Notice described in Section 5.4 (for all IETF
Documents).
e. The Disclaimer described in Section 5.5 (for all IETF Documents).
...
...
If the Contributor desires to eliminate the IETF's right to make
modifications and derivative works of an IETF Contribution (other
...
... If the Contributor desires to eliminate the IETF's right to make
modifications and derivative works of an IETF Contribution (other
than translations), one of the two of the following notices may be
included in the Status of Memo section of an Internet-Draft ...
... "other than to extract section XX as-is for separate use."
Notice 5.2(a) is used if the Contributor intends for the IETF
Contribution to be published as an RFC. Notice 5.2(b) is used along
with the Publication Limitation in Section 5.3 when the Contributor
...
... Contribution to be published as an RFC. Notice 5.2(b) is used along
with the Publication Limitation in Section 5.3 when the Contributor
does not intend for the IETF Contribution to be published as an RFC.
These notices may not be used with any standards-track document ...
... with most working group documents, except as discussed in Section 7.3
below, since the IETF must retain change control over its documents
and the ability to augment, clarify and enhance the original IETF ...
... IETF must retain change control over its documents
and the ability to augment, clarify and enhance the original IETF
Contribution in accordance with the IETF Standards Process.
...
... and the ability to augment, clarify and enhance the original IETF
Contribution in accordance with the IETF Standards Process.
Notice 5.2(a) may be appropriate when republishing standards produced
...
...
Notice 5.2(a) may be appropriate when republishing standards produced
by other (non-IETF) standards organizations, industry consortia or
companies. These are typically published as Informational RFCs, and
...
... companies. These are typically published as Informational RFCs, and
do not require that change control be ceded to the IETF. Basically,
documents of this type convey information for the Internet community.
...
...
If the Contributor only wants the IETF Contribution to be made
available in an Internet-Draft (i.e., does not want the IETF ...
... IETF Contribution to be made
available in an Internet-Draft (i.e., does not want the IETF
Contribution to be published as an RFC) then the Contributor may
include the following notice in the Status of Memo section of the
...
... Internet-Draft."
This notice can be used on IETF Contributions that are intended to
provide background information to educate and to facilitate
discussions ...
... provide background information to educate and to facilitate
discussions within IETF working groups but are not intended to be
published as an RFCs.
...
... Copyright Notice (required for all IETF Documents) ...
...
(Normally placed at the end of the IETF Document.)
"Copyright (C) The Internet Society ...
... retain all their rights."
Additional copyright notices are not permitted in IETF Documents
except in the case where such document is the product of a joint
development effort between the IETF ...
... IETF Documents
except in the case where such document is the product of a joint
development effort between the IETF and another standards development
organization or the document is a republication of the work of
another standards organization. Such exceptions must be approved on
...
... Disclaimer (required in all IETF Documents) ...
...
(Normally placed at the end of the IETF Document after the copyright
notice.)
...
... Notwithstanding the provisions of this Section 5, in certain limited
cases an abbreviated notice may be placed on certain types of
derivative works of IETF Documents in accordance with this Section
5.6.
...
... a. in MIB modules, PIB modules and similar material commonly
extracted from IETF Documents, except for material that is being
placed under IANA maintenance, the following abbreviated notice
...
... Variations of these abbreviated notices are not permitted except
in cases where the material to be extracted is the product of a
joint development effort between the IETF and another standards
development organization or is a republication of the work of
another standards organization. Such variations must be approved
...
... IAB.
b. short excerpts of IETF Documents presented in electronic help
systems, for example, the DESCRIPTION clauses for MIB variables,
...
... Internet Drafts that are not intended to become part of the Standards
Process, the following are required in all such drafts to protect the
IETF and its processes. The RFC Editor may require additional
notices.
...
... Rights Granted in IETF Contributions ...
... The IETF/ISOC must obtain the right to publish an IETF Contribution
as an RFC or an Internet-Draft from the Contributors.
...
... A primary objective of this policy is to obtain from the document
authors only the non-exclusive rights that are needed to develop and
publish IETF Documents and to use the IETF Contributions in the IETF
Standards Process while leaving all other rights with the authors.
...
... authors only the non-exclusive rights that are needed to develop and
publish IETF Documents and to use the IETF Contributions in the IETF
Standards Process while leaving all other rights with the authors.
...
... publish IETF Documents and to use the IETF Contributions in the IETF
Standards Process while leaving all other rights with the authors.
The non-exclusive rights that the IETF ...
... IETF
Standards Process while leaving all other rights with the authors.
The non-exclusive rights that the IETF needs are:
a. the right to publish the document
...
... a. the right to publish the document
b. the right to let the document be freely reproduced in the formats
that the IETF publishes it in
c. the right to let third parties translate it into languages other
...
... than English
d. except where explicitly excluded (see Section 5.2), the right to
make derivative works within the IETF process.
e. the right to let third parties extract some logical parts, for
example MIB modules ...
...
The authors retain all other rights, but cannot withdraw the above
rights from the IETF/ISOC.
...
... created (but see Section 8 below regarding
public domain documents), and IETF cannot make use of IETF
Contributions if it does not have sufficient rights with respect to
...
... public domain documents), and IETF cannot make use of IETF
Contributions if it does not have sufficient rights with respect to
these copyright rights, it is important that the IETF ...
... IETF
Contributions if it does not have sufficient rights with respect to
these copyright rights, it is important that the IETF receive
assurances from all Contributors that they have the authority to
...
... assurances from all Contributors that they have the authority to
grant the IETF the rights that they claim to grant. Without this
assurance, IETF and its participants would run a greater risk of
...
... grant the IETF the rights that they claim to grant. Without this
assurance, IETF and its participants would run a greater risk of
liability to the owners of these rights.
...
... liability to the owners of these rights.
To this end, IETF asks Contributors to give the assurances in Section
3.4 above. These assurances are requested, however, only to the
extent of the Contributor's reasonable and personal knowledge. (See
...
...
The IETF needs to be able to evolve IETF Documents in response to
experience gained in the deployment ...
...
The IETF needs to be able to evolve IETF Documents in response to
experience gained in the deployment of the technologies described in
...
... experience gained in the deployment of the technologies described in
such IETF Documents, to incorporate developments in research and to
react to changing conditions on the Internet and other IP networks ...
... Internet and other IP networks.
In order to do this the IETF must be able to produce derivatives of
its documents; thus the IETF must obtain the right from Contributors
...
... In order to do this the IETF must be able to produce derivatives of
its documents; thus the IETF must obtain the right from Contributors
to produce derivative works. Note though that the IETF only requires
...
... its documents; thus the IETF must obtain the right from Contributors
to produce derivative works. Note though that the IETF only requires
this right for the production of derivative works within the IETF
Standards Process. The IETF ...
... to produce derivative works. Note though that the IETF only requires
this right for the production of derivative works within the IETF
Standards Process. The IETF does not need, nor does it obtain, the
right to let derivative works be created ...
... IETF only requires
this right for the production of derivative works within the IETF
Standards Process. The IETF does not need, nor does it obtain, the
right to let derivative works be created outside of the IETF
Standards ...
... IETF does not need, nor does it obtain, the
right to let derivative works be created outside of the IETF
Standards Process other than as noted in Section 3.3 (E).
The right to produce derivative works is required for all IETF
standards ...
... IETF
Standards Process other than as noted in Section 3.3 (E).
The right to produce derivative works is required for all IETF
standards track documents and for most IETF non-standards track
documents. There are two exceptions to this requirement ...
...
The right to produce derivative works is required for all IETF
standards track documents and for most IETF non-standards track
documents. There are two exceptions to this requirement: documents
...
...
The right to produce derivative works must be granted in order for an
IETF working group to accept an IETF Contribution as a working group
...
... The right to produce derivative works must be granted in order for an
IETF working group to accept an IETF Contribution as a working group
document or otherwise work on it. For non-working group ...
... working group
document or otherwise work on it. For non-working group IETF
Contributions where the Contributor requests publication as a
standards track RFC the right to produce derivative works must be
...
... standards track RFC the right to produce derivative works must be
granted before the IESG will issue an IETF Last-Call and, for most
non-standards track non-working group IETF ...
... IETF Last-Call and, for most
non-standards track non-working group IETF Contributions, before the
IESG will consider the Internet-Draft ...
... Occasionally a Contributor may not want to grant publication rights
or the right to produce derivative works before finding out if an
IETF Contribution has been accepted for development in the IETF
Standards Process. In these cases the Contributor may include the
Derivative Works Limitation described in Section 5.2 and the
...
... or the right to produce derivative works before finding out if an
IETF Contribution has been accepted for development in the IETF
Standards Process. In these cases the Contributor may include the
Derivative Works Limitation described in Section 5.2 and the
Publication Limitation described in Section 5.3 in their IETF ...
... IETF
Standards Process. In these cases the Contributor may include the
Derivative Works Limitation described in Section 5.2 and the
Publication Limitation described in Section 5.3 in their IETF
Contribution. A working group can discuss the Internet-Draft ...
... the aim to decide if it should become a working group document, even
though the right to produce derivative works or to publish the IETF
Contribution as an RFC has not yet been granted. If the IETF
...
... though the right to produce derivative works or to publish the IETF
Contribution as an RFC has not yet been granted. If the IETF
Contribution is accepted for development the Contributor must then
resubmit the IETF ...
... IETF
Contribution is accepted for development the Contributor must then
resubmit the IETF Contribution without the limitation notices before
a working group can formally adopt the IETF ...
... IETF Contribution without the limitation notices before
a working group can formally adopt the IETF Contribution as a working
group document.
...
... working
group document.
The IETF has historically encouraged organizations to publish details
of their technologies, even when the technologies are proprietary,
because understanding how existing technology is being used helps
...
... when developing new technology. But organizations that publish
information about proprietary technologies are frequently not willing
to have the IETF produce revisions of the technologies and then claim
that the IETF version ...
... to have the IETF produce revisions of the technologies and then claim
that the IETF version is the "new version" of the organization's
...
... version" of the organization's
technology. Organizations that feel this way can specify that an
IETF Contribution can be published with the other rights granted
under this document but may withhold the right to produce derivative
works other than translations. The right to produce translations is
...
... under this document but may withhold the right to produce derivative
works other than translations. The right to produce translations is
required before any IETF Contribution can be published as an RFC to
ensure the widest possible distribution of the material in RFCs.
...
... ensure the widest possible distribution of the material in RFCs.
In addition, IETF Documents frequently make normative references to
standards or recommendations developed by other standards
organizations. Since the publications of some standards
...
... organizations. Since the publications of some standards
organizations are not public documents, it can be quite helpful to
the IETF to republish, with the permission of the other standards
organization, some of these documents as RFCs so that the IETF
community can have open access to them to better understand what they
...
... the IETF to republish, with the permission of the other standards
organization, some of these documents as RFCs so that the IETF
community can have open access to them to better understand what they
are referring to. In these cases the RFCs can be published without
the right for the IETF ...
... IETF
community can have open access to them to better understand what they
are referring to. In these cases the RFCs can be published without
the right for the IETF to produce derivative works.
In both of the above cases in which the production of derivative
...
... In both of the above cases in which the production of derivative
works is excluded, the Contributor must include a special legend in
the IETF Contribution, as specified in Section 5.2, in order to
notify IETF participants about this restriction.
...
... the IETF Contribution, as specified in Section 5.2, in order to
notify IETF participants about this restriction.
...
... Contributors may wish to seek trademark or service mark protection on
any terms that are coined or used in their IETF Contributions. IETF
makes no judgment about the validity ...
... service mark protection on
any terms that are coined or used in their IETF Contributions. IETF
makes no judgment about the validity of any such trademark rights.
...
... makes no judgment about the validity of any such trademark rights.
However, the IETF requires each Contributor, under the licenses
described in Section 3.3 above, to grant IETF a perpetual license ...
... However, the IETF requires each Contributor, under the licenses
described in Section 3.3 above, to grant IETF a perpetual license to
use any such trademarks or service ...
... use any such trademarks or service marks solely in exercising its
rights to reproduce, publish and modify the IETF Contribution. This
license does not authorize any IETF participant ...
... IETF Contribution. This
license does not authorize any IETF participant to use any trademark
or service mark in connection ...
...
Rights and licenses granted to the IETF under this document are
granted to all individuals noted in Section 1(a), irrespective of
their employment or institutional affiliation. However, these
...
... individuals to exercise any rights outside the specific context of
the IETF Standards Process.
...
... domain, may not be protected by the
same copyright and other legal rights as other documents.
Nevertheless, we ask each Contributor to grant to the IETF the same
rights as he or she would grant, and to make the same
representations, as though the IETF ...
... IETF the same
rights as he or she would grant, and to make the same
representations, as though the IETF Contribution were protected by
the same legal rights as other documents, and as though the
Contributor could be able to grant these rights. We ask for these
...
... may be protected. We believe they are necessary to protect the ISOC,
the IETF, the IETF Standards Process and all IETF participants, and
...
... ISOC,
the IETF, the IETF Standards Process and all IETF participants, and
also because the IETF ...
... the IETF, the IETF Standards Process and all IETF participants, and
also because the IETF does not have the resources or wherewithal to
...
... IETF Standards Process and all IETF participants, and
also because the IETF does not have the resources or wherewithal to
make any independent investigation as to the actual proprietary
status of any document submitted to it.
...
...
This memo relates to IETF process, not any particular technology.
There are security considerations when adopting any technology, but
...
... security considerations when adopting any technology, but
there are no known issues of security with IETF Contribution rights
policies.
...
... Hovey, R. and S. Bradner, "The Organizations Involved in the IETF Standards Process", BCP 11, RFC 2028, October 1996. ...
... Bradner, S., Ed, "Intellectual Property Rights in IETF Technology", BCP 79, RFC 3979, March 2005. ...
...
The editor would like to acknowledge the help of the IETF IPR Working
Group and, in particular the help of Jorge Contreras of Hale and Dorr
...
... IPR Working
Group and, in particular the help of Jorge Contreras of Hale and Dorr
for his careful legal reviews of this and other IETF IPR-related and
process documents. The editor would also like to acknowledge 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.
...