draft-ietf-ipr-rules-update-06.txt   draft-ietf-ipr-rules-update-07.txt 
Network Working Group S. Bradner Network Working Group S. Bradner
Internet-Draft Harvard University Internet-Draft Harvard University
Editor Jorge Contreras
WilmerHale
Editors
RFC 3978 Update RFC 3978 Update
<draft-ietf-ipr-rules-update-06.txt> <draft-ietf-ipr-rules-update-07.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
skipping to change at page 1, line 33 skipping to change at page 1, line 35
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 August 25, 2006. This Internet-Draft will expire on December 20, 2006.
Abstract Abstract
This document modifies RFC 3978 "IETF Rights in Contributions" as This document modifies RFC 3978 "IETF Rights in Contributions" by
follows: (1) recognizing that the IETF Trust is now the proper recognizing that the IETF Trust is now the proper custodian of all
custodian of all IETF-related intellectual property rights, (2) IETF-related intellectual property rights.
giving IETF Trust the right to permit extraction of material from
RFCs, and (3) giving IETF Trust the right to permit others to create
derivative works outside the IETF Standards Process.
This document does not constrain how the IETF Trust exercises those
rights.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society. (2006) Copyright (C) The Internet Society. (2006)
1. Introduction 1. Introduction
1.1 IETF Trust 1.1 IETF Trust
Currently the IETF requires that authors of Contributions to the IETF Currently the IETF requires that authors of Contributions to the IETF
grant to the IETF (meaning the full set of participants in the IETF grant to the IETF (meaning the full set of participants in the IETF
Standards Process) a limited set of non-exclusive rights and Standards Process) a limited set of non-exclusive rights and
permissions as part of the process of submitting such Contribution. permissions as part of the process of submitting such Contribution.
These rights and permissions are detailed in "IETF Rights in These rights and permissions are detailed in "IETF Rights in
Contributions" (RFC 3978 - BCP 78) [RFC3978]. Contributions" (RFC 3978 - BCP 78) [RFC3978].
The IETF Trust was recently formed to act as the administrative The IETF Trust was recently formed to act as the administrative
custodian of all copyrights and other intellectual property rights custodian of all copyrights and other intellectual property rights
relating to the IETF Standards Process that had previously been held relating to the IETF Standards Process that had previously been held
by ISOC and CNRI (See [reference to IETF Trust Agreement]). This by ISOC (See [reference to IETF Trust Agreement]). This document
document modifies RFC 3978 in order to implement this structure. modifies RFC 3978 in order to implement this structure. Most
Most importantly, it alters the license-grant path as follows: importantly, it alters the license-grant path as follows: whereas
whereas previously authors of Contributions to the IETF would grant a previously authors of Contributions to the IETF would grant a license
license both to ISOC and to all IETF participants, it is now proposed both to ISOC and to all IETF participants, it is now proposed that
that such authors grant a license to the IETF Trust (in Section 3.3). such authors grant a license to the IETF Trust (in Section 3.3), and
This document concerns itself only with "inbound" rights - those that the IETF Trust concurrently grant the necessary corresponding
rights to be granted to the IETF Trust by relevant Contributors. A licenses to all IETF participants (in a new Section 3.7).
separate document will deal with "outbound" rights - those rights
granted by the IETF Trust to others.
This introductory section is to provide context for the reader.
Sections 2 and 3 of this document are intended to be normative.
1.2. Extractions from RFCs
Many people have expressed a desire to extract material from IETF
RFCs for use in documentation, textbooks, on-line help systems, and
for similar uses. In addition, some IETF RFCs contain MIBs and other
types of program code that could be compiled.
1.3 Right to reprint RFCs
Since the start of the RFC series, third parties have been free to
reproduce RFCs as-is or as translations. The permission to do so was
not specifically noted in early RFCs (other than a note to say that
the distribution of the RFC was unlimited). The copyright notice
introduced with RFC 1602 specifically granted these permissions. But
an unintended byproduct of the attempt in BCP 78 to simplify the
copyright statement in published RFCs was the lack of any specific
statement of these permissions in the RFC copyright notice or in BCP
78. A new Section 3.3(F) should be added to RFC 3978 to clarify that
the Contributor permits the IETF Trust to grant this right to third
parties.
1.4 Derivative Works
Currently the IETF obtains from Contributors the right to prepare In addition, under new Section 3.8 the IETF Trust will be able to
derivative works of their Contributions within the IETF Standards grant limited rights to third parties consistent with current IETF
Process. This is done in RFC 3978 Section 3.3 (a) (C). That practice and rules under RFC 3978 (such as the right to reproduce
paragraph should be modified to grant the IETF Trust the ability to IETF documents in unmodified form and to extract and modify code from
authorize the preparation of derivative works without limiting such IETF Documents). This document is not intended to alter or expand
development to the IETF Standards Process. Such a paragraph would the rights that may be granted to third parties.
not, by itself, grant any additional permissions outside of the IETF,
but would empower the IETF Trust to authorize the development of
derivative works outside of the IETF Standards Process. One example
of where the IETF Trust might grant such a right is the case where
another standards development organization (SDO) wants to update or
extend an IETF technology (which would normally be done by the SDO
sending their requirements to the IETF) but the IETF no longer has a
working group focused on the particular technology and the IETF does
not have the interest to create a new working group.
1.5 No Retroactive Effect 1.5 No Retroactive Effect
The addition of these rights to those granted by Contributors under The rights granted under this memo starts with the publication of
RFC 3978 starts with the publication of this memo as a RFC. This this memo as an RFC. This memo does not retroactively obtain these
memo does not retroactively obtain these rights from Contributions rights from Contributions that predate the publication of this memo
that predate the publication of this memo as a RFC. Accordingly, the as a RFC. Accordingly, the legends and other text accompanying this
legends and other text accompanying this memo still reflect the memo still reflect the provisions of RFC 3978, even though those
provisions of RFC 3978, even though those provisions will be amended provisions will be amended once this memo is published as an RFC.
once this memo is published as an RFC. However, nothing prevents the
Contributors of such Contributions voluntarily granting these rights
retroactively.
2. General Statements
2.1 In order to clarify that Contributors are bound by all provisions
of RFC 3978 upon submission of a Contribution to the IETF, the
following paragraph is moved from Section 3.3 to the end of Section
3.1, with clarifying adjustments:
"By submission of a Contribution, each person actually submitting
the Contribution, and each named co-Contributor, is deemed to
agree to the terms and conditions set forth in this document, on
his or her own behalf and on behalf of the organization the
Contributor represents or is sponsored by (if any), when
submitting the Contribution."
2.2 Because it is necessary in this document to refer to individual
IETF participants, the following sentence is added at the end of the
definition of "IETF" in Section 1(a) of RFC 3978:
"An "IETF Participant" shall mean any such individual
participant."
2.3 To make it easier to change the ID boilerplate when needed Sections
5.1 to 5.6 are replaced with the following:
"5.1. IPR Disclosure Acknowledgement (required in all Internet-
Drafts but not in RFCs)
All I-Ds MUST include the exact text for an IPR Disclosure
Acknowledgement from http://www.ietf.org/ipr-boilerplate-
derivworks
5.2. Derivative Works Limitation
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 Derivative Works Limitation
notices from http://www.ietf.org/ipr-boilerplate-derivworks may be
included in the Status of Memo section of an Internet-Draft and
included in a published RFC.
In the cases of MIB or PIB modules and in other cases where the
Contribution includes material that is meant to be extracted in
order to be used, the text of the MIB extraction notice from
http://www.ietf.org/ipr-boilerplate-derivworks should be appended
to the Derivative Works Limitation.
These notices may not be used with any standards-track document or
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 Contribution in accordance with the IETF Standards
Process. A fuller discussion of the rationale behind these
requirements is contained in Section 7.3 below.
5.3. Publication Limitation
If the Contributor only wants the 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 Publication Limitation notice from
http://www.ietf.org/ipr-boilerplate-derivworks 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 within IETF working groups but are not intended to be
published as an RFCs.
5.4. Copyright Notice (required for all IETF Documents)
(Normally placed at the end of the IETF Document.)
The Copyright notice from http://www.ietf.org/ipr-boilerplate-
derivworks must be included in all Internet-Drafts.
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.
5.5. Disclaimer (required in all IETF Documents)
(Normally placed at the end of the IETF Document after the
copyright notice.)
The Disclaimer notice from http://www.ietf.org/ipr-boilerplate-
derivworks must be included in all Internet-Drafts.
5.6. Exceptions
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 abbreviated MIB notice
from http://www.ietf.org/ipr-boilerplate-derivworks shall be
included in the body of the material that will be extracted in
lieu of the notices otherwise required by Section 5.
When the MIB or PIB module is the initial version of a module 1.6 Normative versus Informative references
that is to be maintained by the IANA, the abbreviated MIB
Copyright Notice from http://www.ietf.org/ipr-boilerplate-
derivworks notice shall be included:
Variations of these abbreviated notices are not permitted Section 1 of this memo is intended to be informative only. Section 2
except in cases where the material to be extracted is the of this memo is normative.
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 on an individual basis by the
IAB.
b. short excerpts of IETF Documents presented in electronic help 2. UPDATES TO RFC 3978
systems, for example, the DESCRIPTION clauses for MIB
variables, do not need to include a copyright notice.
3. Rights Granted By Contributors to IETF Trust - New Section 3.3 2.1 RIGHTS GRANTED BY CONTRIBUTORS TO IETF TRUST - UPDATE TO SECTION
3.3
The following text describes the rights that are granted by each The following text describes the rights that are granted by each
Contributor to the IETF Trust and replaces Section 3.3 of RFC 3978 in Contributor to the IETF Trust and replaces Section 3.3 of RFC 3978 in
full: full:
"3.3. Rights Granted by Contributors to IETF Trust "3.3. Rights Granted by Contributors to IETF Trust
To the extent that a Contribution or any portion thereof is To the extent that a Contribution or any portion thereof is
protected by copyright or other rights of authorship, the protected by copyright or other rights of authorship, the
Contributor, and each named co-Contributor, and the organization Contributor, and each named co-Contributor, and the organization
he or she represents or is sponsored by (if any) grants a he or she represents or is sponsored by (if any) grant a
perpetual, irrevocable, non-exclusive, royalty-free, world-wide perpetual, irrevocable, non-exclusive, royalty-free, world-wide
right and license to the IETF Trust under all such copyrights and right and license to the IETF Trust under all such copyrights and
other rights in the Contribution: other rights in the Contribution, provided that the IETF Trust
shall have the right to sublicense these rights solely to the
extent described in Section 3.7 and 3.8 below:
(A) to copy, publish, display, and distribute the Contribution as (A) to copy, publish, display, and distribute the Contribution,
part of the IETF Standards Process or in an Internet-Draft, in whole or in part,
(B) to prepare or allow the preparation of translations of the (B) to prepare translations of the Contribution into languages
Contribution into languages other than English, other than English, and to copy, publish, display, and
distribute such translations or portions thereof,
(C) unless explicitly disallowed in the notices contained in a (C) unless explicitly disallowed in the notices contained in a
Contribution [as per Section 5.2 below], Contribution [as per Section 5.2 below], to modify or prepare
derivative works (in addition to translations) that are based
(1) to modify or prepare derivative works (in addition to on or incorporate all or part of the Contribution, and to copy,
translations) that are based on or incorporate all or part publish, display, and distribute such derivative works, and
of the Contribution or comment upon it, within the IETF
Standards Process, and
(2) as determined by the IETF Trust, to grant third parties the
right to modify or prepare derivative works of the
Contribution outside of the IETF Standards Process, and to
copy, publish, display and distribute such modifications or
derivative works outside the IETF Standards Process, subject
to a requirement to properly acknowledge the IETF (it being
understood that neither consent of, nor notice to, the
Contributor shall be required for any such grant),
provided that in each case the license to such modification or
derivative works does not grant any more rights than the
license to the original Contribution, and
(D) to reproduce any trademarks, service marks or trade names (D) to reproduce any trademarks, service marks or trade names
which are included in the Contribution solely in connection which are included in the Contribution solely in connection
with the reproduction, distribution or publication of the with the reproduction, distribution or publication of the
Contribution and derivative works thereof as permitted by this Contribution and derivative works thereof as permitted by this
Section 3.3, provided that when reproducing Contributions, Section 3.3, provided that when reproducing Contributions,
trademark and service mark identifiers used in the trademark and service mark identifiers used in the
Contribution, including (TM) and (R) will be preserved, and Contribution, including TM and (r) will be preserved.
(E) to extract, copy, publish, display, distribute and incorporate
into other works, for any purpose (and not limited to use
within the IETF Standards Process), all or any portion of the
Contribution without modification (other than non-substantive
modifications such as reformatting, translation into languages
other than English or compilation of source code statements
into executable code), and further provided that the notices
required by Sections 5.4 or 5.6 below, as applicable, are
included, and
(F) to permit third parties to copy, publish, display and
distribute the Contribution without modification, as part of a
full, unmodified RFC and to permit third parties to translate
the Contribution as part of a full, unmodified RFC into
languages other than English, for any purpose, whether or not
within the IETF Standards Process.
(G) to permit the IETF Trust to sublicense these rights to the
extent of the original grant of right and license, including
its use in a working collection or collective work.
The licenses granted in this Section 3.3 shall not be deemed to The licenses granted in this Section 3.3 shall not be deemed to
grant any right under any patent, patent application or other grant any right under any patent, patent application or other
similar intellectual property right disclosed by the similar intellectual property right disclosed by the Contributor
Contributor under BCP 79." under BCP 79 or otherwise."
4. Instruct IETF Trust to grant rights to IETF participants 2.2 RIGHTS GRANTED BY IETF TRUST TO IETF PARTICIPANTS - NEW SECTION 3.7
[ NOTE: this section has been added at the request of the General Now that Contributors are granting rights to the IETF Trust, the IETF
Area AD. This direction may be better placed in another document.] Trust must state what rights are being granted to IETF Participants
to enable the IETF to accomplish its work. Accordingly, the
following Section 3.7 is added. This section simply repeats the
license grants from Section 3.3 that are intended to be granted to
all IETF Participants within the IETF Standards Process.
The following to be inserted between sections 8 and 9 of RFC 3978. The following new Section 3.7 is hereby added to RFC 3978:
"The IETF Trust is hereby instructed to grant the rights granted "3.7 Rights granted by IETF Trust to IETF Participants within the
in section 3.3 above to all participants in the IETF process as IETF Standards Process
needed for the operation of the IETF standards process."
5. Legends and Notifications The IETF Trust hereby grants to each IETF Participant, to the
greatest extent that it is permitted to do so under the licenses
granted to it under Section 3.3 above, the following perpetual,
irrevocable, non-exclusive, royalty-free, world-wide rights and
licenses under all copyrights and other rights of authors, which
rights may be exercised solely within the IETF Standards Process:
The legends and notifications required by RFC 3978 are hereby updated (A) to copy, publish, display, and distribute each IETF Document
as set forth below to reflect the other provisions of this document. (including all Contributions and other portions thereof) in
unmodified form,
5.1 The first paragraph of Section 5 of RFC 3978 explains the (B) to prepare translations of IETF Documents (including all
requirement for applying certain notices and legends to IETF Contributions and other portion thereof) into languages other
documents. There has been considerable confusion in the past than English, and to copy, publish, display, and distribute
regarding the meaning of the copyright notice on these documents. such translations,
Accordingly, the first paragraph of Section 5 is hereby amended as
follows to explain the purpose and meaning of this copyright notice
requirement, as well as to substitute "IETF Trust" for "ISOC":
"The IETF requires that certain notices and disclaimers described (C) unless explicitly disallowed in the notices contained in an
in this Section 5 be reproduced verbatim in all IETF Documents IETF Document [as per Section 5.2 below], to modify or prepare
(including copies, derivative works and translations of IETF derivative works (in addition to translations) that are based
Documents, but subject to the limited exceptions noted in Section on or incorporate all or part of the IETF Document (including
5.2). This requirement protects the IETF Trust, IETF and IETF any Contribution included therein), and to copy, publish,
Participants from liabilities connected with these documents. display, and distribute such derivative works or portions
thereof, and
The copyright notice also alerts readers that the document is an (D) to reproduce any trademarks, service marks or trade names
IETF Document, and that the IETF Trust owns certain aspects of the which are included in a Contribution solely in connection with
document, such as its layout, the RFC numbering convention and the the reproduction, distribution or publication of the
prefatory language of the document. This legend is not, however, Contribution and derivative works thereof as permitted by this
intended to imply that IETF or the IETF Trust owns the text of any Section 3.7, provided that when reproducing Contributions,
Contribution included in an IETF Document. Rather, ownership of trademark and service mark identifiers used in the
such Contributions is retained by the author(s) or remains in the Contribution, including (TM) and (r) will be preserved."
public domain, as applicable, subject only to the licenses granted
to IETF and the IETF Trust under Section 3.3 above."
5.2 Update copyright statement and clarify text about additional 2.3 RIGHTS GRANTED BY IETF TRUST TO THIRD PARTIES - NEW SECTION 3.8
copyright statements
The creation of the IETF Trust to hold IETF-related IPR requires that Under the licenses granted by Contributors in Section 3.3, the IETF
the copyright statement in Section 5.4 be changed. Since it has been Trust has the ability to grant rights in Contributions and other
established practice to include a one-line copyright statement near portions of IETF Documents to third parties for use outside the IETF
the beginning of IETF Documents this should be mentioned. Standards Process. One such right is the right to copy and
republish IETF Documents without modification. Another right is to
use and modify code extracts from IETF Documents. These rights are
not new, and they currently exist in RFC 3978. They are included in
this new section only due to the introduction of the IETF Trust to
this structure. Other rights may be granted by the IETF Trust to
third parties as and when authorized by future documents approved by
the IETF community.
The text in Section 5.4 about multiple copyright statements has The following new Section 3.8 is hereby added to RFC 3978:
occasionally been misinterpreted so should be clarified.
5.2.1 Revised Section 5.4 "3.8 Rights Granted by the IETF Trust to Third Parties
5.4. Copyright Notices (required for all IETF Documents)
(Normally placed at the end of the IETF Document.) The IETF Trust hereby grants to any person wishing to obtain such
rights, to the greatest extent it is permitted to do so, the
following perpetual, irrevocable, non-exclusive, royalty-free,
world-wide rights and licenses under all copyrights and other
rights of authors, which rights may be exercised within or outside
the IETF Standards Process:
"Portions Copyright (C) The IETF Trust (year). (A) to copy, publish, display, and distribute each IETF Document
(including all Contributions and other portions thereof) in
unmodified form,
This document is subject to the rights, licenses and (B) to prepare translations of IETF Documents (including all
restrictions contained in BCP 78, and except as set forth Contributions and other portions thereof) into languages other
therein, the authors retain all their rights." than English, and to copy, publish, display, and distribute such
translations,
Only copyright notices for the IETF Trust are permitted in IETF (C) to extract, modify, incorporate into other works, copy, publish,
Documents except in the case where such a document is the product display, and distribute executable code or code fragments that are
of a joint development effort between the IETF and another included in any IETF Document (such as MIB and PIB modules),
standards development organization or the document is a subject to the notification requirements of Section 5."
republication of the work of another standards organization. Such
exceptions must be approved on an individual basis by the IAB.
5.3 In Section 5.6 of RFC 3978, all occurrences of "Internet Society" 2.4 LEGENDS, NOTIFICATIONS AND ERRATA
or "ISOC" are replaced by "IETF Trust".
to reduce confusion the note about multiple copyright notices The following provisions of RFC 3978 are hereby updated as set forth
below to reflect the introduction of the IETF Trust to this
structure.
5.4 In Section 5.5 of RFC 3978, ", THE IETF TRUST" is inserted after 1) In Sections 5.4 and 5.6 of RFC 3978, all occurrences of
"Internet Society" or "ISOC" are replaced by "IETF Trust".
2) In Section 5.5 of RFC 3978, ", THE IETF TRUST" is inserted after
"INTERNET SOCIETY". "INTERNET SOCIETY".
6. Errata 3) The two sentences of Section 4.2(a)(C) are combined into a
single sentence separated by a comma.
6.1 The two sentences of Section 4.2(a)(C) are combined into a single 4) In Section 7.1, all occurrences of "Internet Society" or "ISOC"
sentence separated by a comma. are replaced by "IETF Trust".
6.2 In Section 7.1, all occurrences of "Internet Society" or "ISOC" are 5) The section reference at the end of the first paragraph of
replaced by "IETF Trust". Section 7.3 is changed from 3.3(E) to 3.3(C).
6.3 The section reference at the end of the first paragraph of Section 6) In Section 8, ", the IETF Trust" is inserted after "ISOC".
7.3 is changed from 3.3(E) to 3.3(C).
6.4. In Section 8, ", the IETF Trust" is inserted after "ISOC". 7) In order to clarify that Contributors are bound by all
provisions of RFC 3978 upon submission of a Contribution to the
IETF, the following paragraph is moved from Section 3.3 to the end
of Section 3.1, with clarifying adjustments:
"By submission of a Contribution, each person actually
submitting the Contribution, and each named co-Contributor, is
deemed to agree to the terms and conditions set forth in this
document, on his or her own behalf and on behalf of the
organization the Contributor represents or is sponsored by (if
any), when submitting the Contribution."
8) Because it is necessary in this document to refer to individual
IETF participants, the following sentence is added at the end of
the definition of "IETF" in Section 1(a) of RFC 3978:
"An "IETF Participant" shall mean any such individual
participant."
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC 3978] Bradner, S., Ed., "IETF Rights in Contributions", BCP 78, [RFC 3978] Bradner, S., Ed., "IETF Rights in Contributions", BCP 78,
RFC 3978, March 2005. RFC 3978, March 2005.
[BCP 101] Austein, R., and B. Wijnen, "Structure of the IETF [BCP 101] Austein, R., and B. Wijnen, "Structure of the IETF
Administrative Support Activity (IASA)," BCP 101, RFC 4071, April Administrative Support Activity (IASA)," BCP 101, RFC 4071, April
2005. 2005.
[IETF Trust Agreement?] [IETF Trust Agreement?]
8. Acknowledgements 8. Editors's Addresses
Thanks to Jorge Contreras from Wilmer, Cutler, Pickering, Hale and
Dorr LLP who provided a significant rewrite of my material.
9. Editor's Address
Scott Bradner Scott Bradner
Harvard University Harvard University
29 Oxford St. 29 Oxford St.
Cambridge MA, 02138 Cambridge MA, 02138
Phone: +1 617 495 3864 Phone: +1 617 495 3864
EMail: sob@harvard.edu EMail: sob@harvard.edu
Jorge L. Contreras
WilmerHale
1875 Pennsylvania Avenue NW
Washington, DC 20006 USA
10. Full copyright statement Phone: +1 202 663 6872
Email: jorge.contreras@wilmerhale.com
9. Full copyright statement
Copyright (C) The Internet Society (2006). This document is subject Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
skipping to change at line 501 skipping to change at page 8, line 21
version 3 to version 4 version 3 to version 4
major rewrite based on input from Jorge major rewrite based on input from Jorge
version 4 to version 5 version 4 to version 5
various places cleaned up removal of outbound rights various places cleaned up removal of outbound rights
version 5 to version 6 version 5 to version 6
added section 2.3 added section 2.3
added a new section 4 and renumbered the old section 4 and the added a new section 4 and renumbered the old section 4 and the
sections following sections following
version 6 to version 7
many changes - redo to focus only on enabling the IETF Trust
 End of changes. 47 change blocks. 
312 lines changed or deleted 160 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/