draft-ietf-ipr-3978-incoming-01.txt   draft-ietf-ipr-3978-incoming-02.txt 
Network Working Group S. Bradner Network Working Group S. Bradner
Internet-Draft Harvard University Internet-Draft Harvard University
Jorge Contreras Jorge Contreras
WilmerHale WilmerHale
Editors Editors
17 October 2007
Rights Contributors provide to the IETF Trust Rights Contributors provide to the IETF Trust
<draft-ietf-ipr-3978-incoming-01.txt> <draft-ietf-ipr-3978-incoming-02.txt>
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
skipping to change at page 1, line 34 skipping to change at page 1, line 36
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on December 26, 2007. This Internet-Draft will expire on April 17, 2008.
Copyright (C) IETF Trust (2007). Copyright (C) IETF Trust (2007).
Abstract Abstract
The IETF policies about rights in Contributions to the IETF are The IETF policies about rights in Contributions to the IETF are
designed to ensure that such Contributions can be made available to designed to ensure that such Contributions can be made available to
the IETF and Internet communities while permitting the authors to the IETF and Internet communities while permitting the authors to
retain as many rights as possible. This memo details the IETF retain as many rights as possible. This memo details the IETF
policies on rights in Contributions to the IETF. It also describes policies on rights in Contributions to the IETF. It also describes
the objectives that the policies are designed to meet. This memo the objectives that the policies are designed to meet. This memo
skipping to change at page 2, line 50 skipping to change at page 2, line 50
a. "Contribution": any submission to the IETF intended by the a. "Contribution": any submission to the IETF intended by the
Contributor for publication as all or part of an Internet-Draft or Contributor for publication as all or part of an Internet-Draft or
RFC (except for RFC Editor Contributions described in Section 4 RFC (except for RFC Editor Contributions described in Section 4
below) and any statement made within the context of an IETF below) and any statement made within the context of an IETF
activity. Such statements include oral statements in IETF activity. Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at sessions, as well as written and electronic communications made at
any time or place, which are addressed to: any time or place, which are addressed to:
o the IETF plenary session, o the IETF plenary session,
o any IETF working group or portion thereof, o any IETF working group or portion thereof,
o any Birds of a Feather (BOF) session,
o the IESG, or any member thereof on behalf of the IESG, o the IESG, or any member thereof on behalf of the IESG,
o the IAB or any member thereof on behalf of the IAB, o the IAB or any member thereof on behalf of the IAB,
o any IETF mailing list, including the IETF list itself, any 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, functioning under IETF auspices,
o the RFC Editor or the Internet-Drafts function (except for RFC o the RFC Editor or the Internet-Drafts function (except for RFC
Editor Contributions described in Section 4 below). Editor Contributions described in Section 4 below).
Statements made outside of an IETF session, mailing list or other Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF function, that are clearly not intended to be input to an IETF
skipping to change at page 3, line 42 skipping to change at page 3, line 43
Commonwealth of Virginia, USA, in order to hold and administer Commonwealth of Virginia, USA, in order to hold and administer
intellectual property rights for the benefit of the IETF. intellectual property rights for the benefit of the IETF.
h. "Internet-Draft": temporary documents used in the IETF Standards h. "Internet-Draft": temporary documents used in the IETF Standards
Process. Internet-Drafts are posted on the IETF web site by the Process. Internet-Drafts are posted on the IETF web site by the
IETF Secretariat. As noted in Section 2.2 of RFC 2026, Internet- IETF Secretariat. As noted in Section 2.2 of RFC 2026, Internet-
Drafts have a nominal maximum lifetime of six months in the IETF Drafts have a nominal maximum lifetime of six months in the IETF
Secretariat's public directory. Secretariat's public directory.
i. "Legend Instructions" means the standardized text that is i. "Legend Instructions" means the standardized text that is
included in IETF Documents and the instructions and requirements included in IETF Documents and the instructions and requirements
for including that standardized text in IETF Documents, each as for including that standardized text in IETF Documents, each as
posted from time to time at www.ietf.org/legends. posted from time to time at http://www.ietf.org/legends.
j. "RFC": the basic publication series for the IETF. RFCs are j. "RFC": the basic publication series for the IETF. RFCs are
published by the RFC Editor. Although RFCs may be superseded in published by the RFC Editor. Although RFCs may be superseded in
whole or in part by subsequent RFCs, the text of an RFC is not whole or in part by subsequent RFCs, the text of an RFC is not
altered once published in RFC form. (See [RFC2026] Section 2.1) altered once published in RFC form. (See [RFC2026] Section 2.1)
k. "Reasonably and personally known": means something an individual k. "Reasonably and personally known": means something an individual
knows personally or, because of the job the individual holds, knows personally or, because of the job the individual holds,
would reasonably be expected to know. This wording is used to would reasonably be expected to know. This wording is used to
indicate that an organization cannot purposely keep an individual indicate that an organization cannot purposely keep an individual
in the dark about patents or patent applications just to avoid the in the dark about patents or patent applications just to avoid the
disclosure requirement. But this requirement should not be disclosure requirement. But this requirement should not be
interpreted as requiring the IETF Contributor or participant (or interpreted as requiring the IETF Contributor or participant (or
his or her represented organization, if any) to perform a patent his or her represented organization, if any) to perform a patent
search in an attempt to find applicable IPR. search in an attempt to find applicable IPR.
l. "RFC Editor Documents": means Internet-Drafts that are submitted t
the RFC Editor independently of the IETF Standards Process. (See
section4.)
2. Introduction 2. Introduction
In all matters of copyright and document procedures, the intent is to In all matters of copyright and document procedures, the intent is to
benefit the Internet community and the public at large, while benefit the Internet community and the public at large, while
respecting the legitimate rights of others. respecting the legitimate rights of others.
Under the laws of most countries and current international treaties Under the laws of most countries and current international treaties
(for example the "Berne Convention for the Protection of Literary and (for example the "Berne Convention for the Protection of Literary and
Artistic Work" [Berne Convention]), authors obtain numerous rights in Artistic Work" [Berne Convention]), authors obtain numerous rights in
the works they produce automatically upon producing them. These the works they produce automatically upon producing them. These
skipping to change at page 4, line 29 skipping to change at page 4, line 33
cases, if the author produces a work within the scope of his or her cases, if the author produces a work within the scope of his or her
employment, most of those rights are usually assigned to the employment, most of those rights are usually assigned to the
employer, either by operation of law or, in many cases, under employer, either by operation of law or, in many cases, under
contract. (The Berne Convention names some rights as "inalienable", contract. (The Berne Convention names some rights as "inalienable",
which means that the author retains them in all cases.) which means that the author retains them in all cases.)
In order for Contributions to be used within the IETF Standards In order for Contributions to be used within the IETF Standards
Process, including when they are published as Internet-Drafts or Process, including when they are published as Internet-Drafts or
RFCs, certain limited rights must be granted to the IETF Trust, which RFCs, certain limited rights must be granted to the IETF Trust, which
then grants the necessary rights to the IETF. In addition, then grants the necessary rights to the IETF. In addition,
Contributors must make representations to IETF Trust and the IETF Contributors must make representations to the IETF Trust and the IETF
regarding their ability to grant these rights. regarding their ability to grant these rights.
Section 1 provides definitions used in these policies. Sections 3 Section 1 provides definitions used in these policies. Sections 3
and 4 of this document explain the rationale for these provisions. and 4 of this document explain the rationale for these provisions.
Only sections 5 and 6 of this document are normative, the other Only sections 5 and 6 of this document are normative, the other
sections are informative. A companion document RFC 3979 [RFC3979] sections are informative. A companion document RFC 3979 [RFC3979]
deals with rights, including possible patent rights, in technologies deals with rights, including possible patent rights, in technologies
developed or specified as part of the IETF Standards Process. This developed or specified as part of the IETF Standards Process. This
document is not intended to address those issues. This memo document is not intended to address those issues. This memo
obsoletes RFC 3978 and 4748 and, with RFC 3979 and RFC obsoletes RFC 3978 and 4748 and, with RFC 3979 and RFC
skipping to change at page 5, line 20 skipping to change at page 5, line 23
A primary objective of this policy is to obtain from the document A primary objective of this policy is to obtain from the document
authors only the non-exclusive rights that are needed to develop and authors only the non-exclusive rights that are needed to develop and
publish IETF Documents and to use IETF Contributions in the IETF publish IETF Documents and to use IETF Contributions in the IETF
Standards Process and potentially elsewhere. Standards Process and potentially elsewhere.
The authors retain all other rights, but cannot withdraw the above The authors retain all other rights, but cannot withdraw the above
rights from the IETF Trust and IETF. rights from the IETF Trust and IETF.
It is important to note that under this document Contributors are It is important to note that under this document Contributors are
required to grant certain rights to the IETF Trust, which holds all required to grant certain rights to the IETF Trust, (See Section
IETF-related intellectual property on behalf of the IETF community. 5.3.) which holds all IETF-related intellectual property on behalf of
The IETF Trust will, in turn, grant a sublicense of these rights to the IETF community. The IETF Trust will, in turn, grant a sublicense
all IETF participants for use in the IETF Standards Process. This of these rights to all IETF participants for use in the IETF
sublicense is necessary for the standards development work of the Standards Process. (See Section 5.4.) This sublicense is necessary
IETF to continue. In addition, the IETF Trust may grant certain for the standards development work of the IETF to continue. In
other sublicenses of the rights that it is granted under this addition, the IETF Trust may grant certain other sublicenses of the
document. In granting such other sublicenses, the IETF Trust will be rights that it is granted under this document. In granting such
guided [and bound] by documents such as [-outbound]. other sublicenses, the IETF Trust will be guided and bound by
documents such as [-outbound].
3.2. Rights to use Contributions 3.2. Rights to use Contributions
Because, under the laws of most countries and applicable It is important that the IETF receive assurances from all
international treaties, copyright rights come into existence when a Contributors that they have the authority to grant the IETF the
work of authorship is created (but see Section 3.5 below regarding rights that they claim to grant because, under the laws of most
public domain documents), and IETF cannot make use of IETF countries and applicable international treaties, copyright rights
Contributions if it does not have sufficient rights with respect to come into existence when a work of authorship is created (but see
these copyright rights, it is important that the IETF receive Section 3.5 below regarding public domain documents), and the IETF
assurances from all Contributors that they have the authority to cannot make use of IETF Contributions if it does not have sufficient
grant the IETF the rights that they claim to grant. Without this rights with respect to these copyright rights. IETF and its
assurance, IETF and its participants would run a greater risk of participants would run a greater risk of liability to the owners of
liability to the owners of these rights. To this end, IETF asks these rights without this assurance. To this end, IETF asks
Contributors to give the assurances in Section5.6 below. These Contributors to give the assurances in Section5.6 below. These
assurances are requested, however, only to the extent of the assurances are requested, however, only to the extent of the
Contributor's reasonable and personal knowledge. (See Section 1(l)) Contributor's reasonable and personal knowledge. (See Section 1(k))
3.3. Right to Produce Derivative Works 3.3. Right to Produce Derivative Works
The IETF needs to be able to evolve IETF Documents in response to 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 such IETF Documents, to incorporate developments in research and to
react to changing conditions on the Internet and other IP networks. react to changing conditions on the Internet and other IP networks.
The IETF may also decide to permit others to develop derivative works The IETF may also decide to permit others to develop derivative works
based on Contributions. In order to do this, the IETF must be able based on Contributions. In order to do this, the IETF must be able
to produce derivatives of its documents; thus the IETF must obtain to produce derivatives of its documents; thus the IETF must obtain
the right from Contributors to produce derivative works. The right the right from Contributors to produce derivative works. Note that
to produce derivative works is required for all IETF standards track the right to produce translations is required before any Contribution
can be published as an RFC to ensure the widest possible distribution
of the material in RFCs. The right to produce derivative works, in
addition to translations, is required for all IETF standards track
documents and for most IETF non-standards track documents. There are documents and for most IETF non-standards track documents. There are
two exceptions to this requirement: documents describing proprietary two exceptions to this requirement: documents describing proprietary
technologies and documents that are republications of the work of technologies and documents that are republications of the work of
other standards organizations. other standards organizations.
The right to produce derivative works must be granted in order for an The right to produce derivative works must be granted in order for an
IETF working group to accept a Contribution as a working group IETF working group to accept a Contribution as a working group
document or otherwise work on it. For non-working group Contributions document or otherwise work on it. For non-working group Contributions
where the Contributor requests publication as a standards track RFC, where the Contributor requests publication as a standards track RFC,
the right to produce derivative works must be granted before the IESG the right to produce derivative works must be granted before the IESG
skipping to change at page 6, line 36 skipping to change at page 6, line 44
produce derivative works or to publish the Contribution as an RFC has produce derivative works or to publish the Contribution as an RFC has
not yet been granted. However, if the Contribution is accepted for not yet been granted. However, if the Contribution is accepted for
development, the Contributor must resubmit the Contribution without development, the Contributor must resubmit the Contribution without
the limitation notices before a working group can formally adopt the the limitation notices before a working group can formally adopt the
Contribution as a working group document. The IETF Trust may Contribution as a working group document. The IETF Trust may
establish different policies for granting sublicenses with respect to establish different policies for granting sublicenses with respect to
different types of Contributions and content within Contributions different types of Contributions and content within Contributions
(such as executable code versus descriptive text or references to (such as executable code versus descriptive text or references to
third party materials). The IETF Trust's policies concerning the third party materials). The IETF Trust's policies concerning the
granting of sublicenses to make derivative works will be guided by granting of sublicenses to make derivative works will be guided by
RFC [-outbound. RFC [-outbound].
The IETF has historically encouraged organizations to publish details The IETF has historically encouraged organizations to publish details
of their technologies, even when the technologies are proprietary, of their technologies, even when the technologies are proprietary,
because understanding how existing technology is being used helps because understanding how existing technology is being used helps
when developing new technology. But organizations that publish when developing new technology. But organizations that publish
information about proprietary technologies are frequently not willing information about proprietary technologies are frequently not willing
to have the IETF produce revisions of the technologies and then to have the IETF produce revisions of the technologies and then
possibly claim that the IETF version is the "new version" of the possibly claim that the IETF version is the "new version" of the
organization's technology. Organizations that feel this way can organization's technology. Organizations that feel this way can
specify that a Contribution be published with the other rights specify that a Contribution be published with the other rights
granted under this document but may withhold the right to produce granted under this document but may withhold the right to produce
derivative works other than translations. The right to produce derivative works other than translations.
translations is required before any Contribution can be published as
an RFC to ensure the widest possible distribution of the material in
RFCs.
In addition, IETF Documents frequently make normative references to In addition, IETF Documents frequently make normative references to
standards or recommendations developed by other standards standards or recommendations developed by other standards
organizations. Since the publications of some standards organizations organizations. Since the publications of some standards organizations
are not public documents, it can be quite helpful to the IETF to are not public documents, it can be quite helpful to the IETF to
republish, with the permission of the other standards organization, republish, with the permission of the other standards organization,
some of these documents as RFCs so that the IETF community can have 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. 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 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 IETF to produce derivative works. In both of the above cases in
skipping to change at page 7, line 47 skipping to change at page 8, line 5
representations, as though the IETF Contribution were protected by representations, as though the IETF Contribution were protected by
the same legal rights as other documents, and as though the the same legal rights as other documents, and as though the
Contributor could be able to grant these rights. We ask for these Contributor could be able to grant these rights. We ask for these
grants and representations only to the extent that the Contribution grants and representations only to the extent that the Contribution
may be protected. We believe they are necessary to protect the ISOC, may be protected. We believe they are necessary to protect the ISOC,
the IETF Trust, the IETF, the IETF Standards Process and all IETF the IETF Trust, the IETF, the IETF Standards Process and all IETF
participants, and also because the IETF does not have the resources participants, and also because the IETF does not have the resources
or wherewithal to make any independent investigation as to the actual or wherewithal to make any independent investigation as to the actual
proprietary status of any document submitted to it. proprietary status of any document submitted to it.
3.6 Copyright in RFCs. 3.6. Copyright in RFCs.
As noted above, Contributors to the IETF (or their employers) retain As noted above, Contributors to the IETF (or their employers) retain
ownership of the copyright in their Contributions. This includes ownership of the copyright in their Contributions. This includes
Internet-Drafts and all other Contributions made within the IETF Internet-Drafts and all other Contributions made within the IETF
Standards Process (e.g., via e-mail, oral comment and otherwise). Standards Process (e.g., via e-mail, oral comment and otherwise).
However, it is important that the IETF (through the IETF Trust) own However, it is important that the IETF (through the IETF Trust) own
the copyright in documents that are published as RFCs (other than the copyright in documents that are published as RFCs (other than
Informational RFCs and RFCs that are submitted as RFC Editor Informational RFCs and RFCs that are submitted as RFC Editor
Contributions). Ownership of the copyright in an RFC does not Contributions). Ownership of the copyright in an RFC does not
diminish the Contributors' rights in their underlying contributions, diminish the Contributors' rights in their underlying contributions,
but it does prevent anyone other than the IETF Trust (and its but it does prevent anyone other than the IETF Trust (and its
skipping to change at page 9, line 16 skipping to change at page 9, line 22
generated automatically or otherwise, that states or implies that the generated automatically or otherwise, that states or implies that the
Contribution is confidential or subject to any privilege, can be Contribution is confidential or subject to any privilege, can be
disregarded for all purposes, and will be of no force or effect. disregarded for all purposes, and will be of no force or effect.
5.3. Rights Granted by Contributors to the IETF Trust 5.3. Rights Granted by Contributors to the IETF Trust
To the extent that a Contribution or any portion thereof is protected To the extent that a Contribution or any portion thereof is protected
by copyright or other rights of authorship, the Contributor, and each by copyright or other rights of authorship, the Contributor, and each
named co-Contributor, and the organization he or she represents or is named co-Contributor, and the organization he or she represents or is
sponsored by (if any) grant a perpetual, irrevocable, non-exclusive, sponsored by (if any) grant a perpetual, irrevocable, non-exclusive,
royalty-free, world-wide right and license to the IETF Trust under royalty-free, world-wide right and license to the IETF Trust under
all such copyrights and other rights in the Contribution. all such copyrights and other rights in the Contribution:
(A) to copy, publish, display, and distribute the Contribution, in (A) to copy, publish, display, and distribute the Contribution, in
whole or in part, whole or in part,
(B) to prepare translations of the Contribution into languages other (B) to prepare translations of the Contribution into languages other
than English, in whole or in part, and to copy, publish, display, than English, in whole or in part, and to copy, publish, display,
and distribute such translations or portions thereof, and distribute such translations or portions thereof,
(C) unless explicitly disallowed in the notices contained in a (C) to modify or prepare derivative works (in addition to
Contribution [in the form specified by the Legend Instructions],
to modify or prepare derivative works (in addition to
translations) that are based on or incorporate all or part of the translations) that are based on or incorporate all or part of the
Contribution, and to copy, publish, display, and distribute such Contribution, and to copy, publish, display, and distribute such
derivative works, or portions thereof, and derivative works, or portions thereof unless explicitly disallowed
in the notices contained in a Contribution [in the form specified
by the Legend Instructions], and
(D) to reproduce any trademarks, service marks or trade names which (D) to reproduce any trademarks, service marks or trade names which
are included in the Contribution solely in connection with the are included in the Contribution solely in connection with the
reproduction, distribution or publication of the Contribution and reproduction, distribution or publication of the Contribution and
derivative works thereof as permitted by this Section 5.3, derivative works thereof as permitted by this Section 5.3,
provided that when reproducing Contributions, trademark and provided that when reproducing Contributions, trademark and
service mark identifiers used in the Contribution, including TM service mark identifiers used in the Contribution, including TM
and (R) will be preserved. and (R), will be preserved.
5.4 Sublicenses by IETF Trust 5.4. Sublicenses by IETF Trust
The IETF Trust will sublicense the rights granted to it under Section The IETF Trust will sublicense the rights granted to it under Section
5.3 to all IETF participants for use within the IETF Standards 5.3 to all IETF participants for use within the IETF Standards
Process. This license is expressly granted under [TRUST LICENSE Process. This license is expressly granted under [TRUST LICENSE
DOCUMENT]. DOCUMENT].
In addition, the IETF Trust may grant additional sublicenses of the In addition, the IETF Trust may grant additional sublicenses of the
licenses granted to it hereunder. In doing so, the IETF Trust will licenses granted to it hereunder. In doing so, the IETF Trust will
comply with the guidance provided under RFC xxx [-outbound]. comply with the guidance provided under RFC xxx [-outbound].
5.5 No Patent License 5.5. No Patent License
The licenses granted in Section 5.3 shall not be deemed to grant any The licenses granted in Section 5.3 shall not be deemed to grant any
right under any patent, patent application or other similar right under any patent, patent application or other similar
intellectual property right disclosed by the Contributor under BCP 79 intellectual property right disclosed by the Contributor under BCP 79
or otherwise. or otherwise.
5.6. Representations and Warranties 5.6. Representations and Warranties
With respect to each Contribution, each Contributor represents that With respect to each Contribution, each Contributor represents that
to the best of his or her knowledge and ability: to the best of his or her knowledge and ability:
a. The Contribution properly acknowledges all major Contributors. A a. The Contribution properly acknowledges all major Contributors. A
skipping to change at page 10, line 42 skipping to change at page 10, line 48
Section 5.3 and Section 5.4 or 5.6. Section 5.3 and Section 5.4 or 5.6.
5.8. Trademarks 5.8. Trademarks
Contributors who claim trademark rights in terms used in their IETF Contributors who claim trademark rights in terms used in their IETF
Contributions are requested to state specifically what conditions Contributions are requested to state specifically what conditions
apply to implementers of the technology relative to the use of such apply to implementers of the technology relative to the use of such
trademarks. Such statements should be submitted in the same way as is trademarks. Such statements should be submitted in the same way as is
done for other intellectual property claims. (See [RFC3979] Section done for other intellectual property claims. (See [RFC3979] Section
6.) 6.)
5.9 Copyright in RFCs 5.9. Copyright in RFCs
Subject to each Contributor's (or its sponsor's) ownership of its Subject to each Contributor's (or its sponsor's) ownership of its
underlying Contributions (which ownership is qualified by the underlying Contributions (which ownership is qualified by the
irrevocable licenses granted under Section 5.3), each Contributor irrevocable licenses granted under Section 5.3), each Contributor
hereby acknowledges that the copyright in any RFC in which such hereby acknowledges that the copyright in any RFC in which such
Contribution is included, other than an Informational RFC or an RFC Contribution is included, other than an RFC that is an RFC Editor
that is an RFC Editor Contribution, shall be owned by the IETF Trust. Contribution, shall be owned by the IETF Trust. Such Contributor
shall be deemed to assign to the IETF Trust such Contributor's
copyright interest in the collective work constituting such RFC upon
the submission of such RFC for publication, and acknowledges that a
copyright notice acknowledging the IETF Trust's ownership of the
copyright in such RFC will be included in the published RFC.
5.10. Contributors retention of rights
[THIS SECTION IS STILL UNDER DISCUSSION] Notwithstanding any terms in
this document to the contrary, in addition to any rights under
copyright retained by Contributor and in addition to any rights
generally granted by the IETF trust, Contributor retains, and grants
to each Co-Contributor to an RFC in which such Contributor's
Contribution, or a derivative work thereof may appear, the right:
(A) to copy, publish, display, and distribute any RFC that includes
the Contribution, in whole or in part,
(B) to prepare translations of such RFCs into languages other than
English, in whole or in part, and to copy, publish, display, and
distribute such translations or portions thereof,
(C) to make derivative works from such RFCs, and to copy, publish,
display, and distribute such derivative works thereof, and
(D) to reproduce any trademarks, service marks or trade names which
are included in such RFCs solely in connection with the
reproduction, distribution or publication of the RFC thereof as
permitted by this Section 5.10, provided that when reproducing
RFCs, trademark and service mark identifiers used in the RFC,
including TM and (R), will be preserved.
Notwithstanding the above rights, the Contributor does not have the
right to represent any document as an RFC, or equivalent to an RFC,
if it is not a full and complete copy or translation of the published
RFC.
6. Legends, Notices and Other Standardized Text in IETF Documents 6. Legends, Notices and Other Standardized Text in IETF Documents
The IETF requires that certain standardized text be reproduced The IETF requires that certain standardized text be reproduced
verbatim in certain IETF Documents (including copies, derivative verbatim in certain IETF Documents (including copies, derivative
works and translations of IETF Documents). Some of this standardized works and translations of IETF Documents). Some of this standardized
text may be mandatory (e.g., copyright notices and disclaimers that text may be mandatory (e.g., copyright notices and disclaimers that
must be included in all RFCs) and some may be optional (e.g., must be included in all RFCs) and some may be optional (e.g.,
limitations on the right to make derivative works). The text itself, limitations on the right to make derivative works). The text itself,
as well as the rules that explain when and how it must be used, are as well as the rules that explain when and how it must be used, are
contained in the Legend Instructions. The Legend Instructions may be contained in the Legend Instructions. The Legend Instructions may be
updated from time to time, and the version of the standardized text updated from time to time, and the version of the standardized text
that must be included in IETF Documents is that which was posted in that must be included in IETF Documents is that which was posted in
the Legend Instructions on the date of publication. the Legend Instructions on the date of publication.
The IETF reserves the right to refuse to publish Contributions that The IETF reserves the right to refuse to publish Contributions that
do not include the legends required by the Legend Instructions. do not include the legends and notices required by the Legend
Instructions.
It is important to note that each Contributor grants the IETF Trust It is important to note that each Contributor grants the IETF Trust
rights pursuant to this document and the policies described herein. rights pursuant to this document and the policies described herein.
The legends and notices included in certain written Contributions The legends and notices included in certain written Contributions
such as Internet-Drafts do not themselves convey any rights. They such as Internet-Drafts do not themselves convey any rights. They
are simply included to inform the reader (whether or not part of the are simply included to inform the reader (whether or not part of the
IETF) about certain legal rights and limitations associated with such IETF) about certain legal rights and limitations associated with such
documents. documents.
It is also important to note that 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 and another standards development organization or the document
is a republication of the work of another standards organization.
Such exceptions must be approved on an individual basis by the IAB.
7. Security Considerations 7. Security Considerations
This memo relates to IETF process, not any particular technology. This memo relates to IETF process, not any particular technology.
There are security considerations when adopting any technology, but There are security considerations when adopting any technology, but
there are no known issues of security with IETF Contribution rights there are no known issues of security with IETF Contribution rights
policies. policies.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, October 1996. 3", BCP 9, RFC 2026, October 1996.
[RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in [RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in
the IETF Standards Process", BCP 11, RFC 2028, October 1996. the IETF Standards Process", BCP 11, RFC 2028, October 1996.
[RFC3979] Bradner, S., Ed, "Intellectual Property Rights in IETF [RFC3979] Bradner, S., Ed, "Intellectual Property Rights in IETF
Technology", BCP 79, RFC 3979, March 2005. Technology", BCP 79, RFC 3979, March 2005.
[Trust] IETF Trust Agreement - http://iaoc.ietf.org/docs/IETF-Trust- [Trust] IETF Trust Agreement - http://trustee.ietf.org/xxx
Agreement-Executed-12-15-05.pdf
8.2. Informative References 8.2. Informative References
[RFC3978] Bradner, S. Ed., "IETF Rights in Contributions", RFC 3978, [RFC3978] Bradner, S. Ed., "IETF Rights in Contributions", RFC 3978,
March 2005. March 2005.
[Berne] "Berne Convention for the Protection of Literary and Artistic [Berne] "Berne Convention for the Protection of Literary and Artistic
Work", http://www.wipo.int/treaties/en/ip/berne/trtdocs_wo001.html Work", http://www.wipo.int/treaties/en/ip/berne/trtdocs_wo001.html
9. Acknowledgements 9. Acknowledgements
The editors would like to acknowledge the help of the IETF IPR The editors would like to acknowledge the help of the IETF IPR
Working Group provided during the development of the document. Working Group provided during the development of the document.
skipping to change at page 12, line 21 skipping to change at page 13, line 19
EMail: sob@harvard.edu EMail: sob@harvard.edu
Jorge L. Contreras Jorge L. Contreras
WilmerHale WilmerHale
1875 Pennsylvania Avenue NW 1875 Pennsylvania Avenue NW
Washington, DC 20006 USA Washington, DC 20006 USA
Phone: +1 202 663 6872 Phone: +1 202 663 6872
Email: jorge.contreras@wilmerhale.com Email: jorge.contreras@wilmerhale.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). This document is subject to the Copyright (C) IETF Trust (2007). This document is subject to the
rights, licenses and restrictions contained in BCP 78, and except as rights, licenses and restrictions contained in BCP 78, and except as
set forth therein, the authors retain all their rights. This set forth therein, the authors retain all their rights. This
document and the information contained herein are provided on an "AS document and the information contained herein are provided on an "AS
IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTSOR IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTSOR
IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
EXPRESSOR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
USE OFTHE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
IMPLIEDWARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
PURPOSE.
Intellectual Property Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. Copies of IPR disclosures made to the found in BCP 78 and BCP 79. Copies of IPR disclosures made to the
skipping to change at page 13, line 7 skipping to change at page 14, line 4
permission for the use of such proprietary rights by implementers or permission for the use of such proprietary rights by implementers or
users of this specification can be obtained from the IETF on-line IPR users of this specification can be obtained from the IETF on-line IPR
repository at http://www.ietf.org/ipr. The IETF invites any repository at http://www.ietf.org/ipr. The IETF invites any
interested party to bring to its attention any copyrights, patents or interested party to bring to its attention any copyrights, patents or
patent applications, or other proprietary rights that may cover patent applications, or other proprietary rights that may cover
technology that may be required to implement this standard. Please technology that may be required to implement this standard. Please
address the information to the IETF at ietf-ipr@ietf.org. address the information to the IETF at ietf-ipr@ietf.org.
Acknowledgement Acknowledgement
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. ?? Internet Society.
changes
version 01 ->02
misc grammar fixes
added BOF to sec 1(a)
added 1(l)
reorder 3.2
moved sentence about translations within sec 3.3
reorder 5.3 (C)
added section 5.10
removed "an Informational RFC" from section 5.9
added text about assigning rights and acknowledging that a
copyright notice will be added to section 5.9
added 2nd pp to section 3.6 from RFC 3978
added pp on multiple copyright notices to sec 6
??
?? ??
?? ??
?? ??
US1DOCS 6241323v2 US1DOCS 6241323v2
 End of changes. 28 change blocks. 
53 lines changed or deleted 114 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/