5745
INFORMATIONAL
Procedures for Rights Handling in the RFC IAB Stream
Authors: A. Malis, IAB
Date: December 2009
Stream: IAB
Abstract
This document specifies the procedures by which authors of RFC IAB stream documents grant the community "incoming" rights for copying and using the text. It also specifies the "outgoing" rights the community grants to readers and users of those documents, and it requests that the IETF Trust manage the outgoing rights to effect this result. This memo provides information for the Internet community.
RFC 5745
INFORMATIONAL
Network Working Group A. Malis, Ed.
Request for Comments: 5745 For the IAB
Updates: <a href="./rfc4846">4846</a> December 2009
Category: Informational
<span class="h1">Procedures for Rights Handling in the RFC IAB Stream</span>
Abstract
This document specifies the procedures by which authors of RFC IAB
stream documents grant the community "incoming" rights for copying and
using the text. It also specifies the "outgoing" rights the community
grants to readers and users of those documents, and it requests that the
IETF Trust manage the outgoing rights to effect this result.
Status of This Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the BSD License.
<span class="grey">Malis Informational [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc5745">RFC 5745</a> Rights for the IAB Stream December 2009</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. Background . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-3">3</a>. Goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-4">4</a>. Rules for Submission and Use of Material . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-5">5</a>. Procedures Requested of the IETF Trust . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-6">6</a>. Patent and Trademark Rules for the IAB Stream . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-7">7</a>. Security Considerations . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-8">8</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-8.1">8.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-8.2">8.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-9">9</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-10">10</a>. IAB Members at the Time of This Writing . . . . . . . . . . . . <a href="#page-6">6</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
As the IETF has grown, the process and the community have become more
careful about defining the rights relating to copying documents that
are granted by authors to the community, and the corresponding rights
that are granted by the community to readers and users of these
documents. The creation of the IETF Trust [<a href="./rfc4371" title=""BCP 101 Update for IPR Trust"">RFC4371</a>], with its
special role in managing intellectual property rights (IPR), has also
increased the need to be explicit about these rights and decisions.
This document defines the copyright procedures for RFC IAB stream
documents. It parallels the procedures for IETF-produced documents
defined in <a href="./rfc5377">RFC 5377</a> [<a href="./rfc5377" title=""Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF Documents"">RFC5377</a>] and <a href="./rfc5378">RFC 5378</a> [<a href="./rfc5378" title=""Rights Contributors Provide to the IETF Trust"">RFC5378</a>].
In summary, submissions in the IAB stream use the same submission
procedures and mechanisms that are defined in <a href="./rfc5378">RFC 5378</a>, and hence
require the same "incoming rights" as IETF-stream documents. This
document provides advice to the Trustees of the IETF Trust on
"outgoing" rights to be granted to readers and users of IAB stream
documents, and it explicitly requests the IETF Trust to manage the
rights in accordance with this advice.
This document also specifies the policies with regard to the
disclosure of Patents and Trademarks that may be relevant to a
submission intended for the IAB stream.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Background</span>
The concept of RFC streams in general, and the IAB stream in
particular, is described in <a href="./rfc4844#section-5">Section 5 of RFC 4844</a> [<a href="./rfc4844" title=""The RFC Series and RFC Editor"">RFC4844</a>].
<a href="./rfc4846#section-8">Section 8 of RFC 4846</a> [<a href="./rfc4846" title=""Independent Submissions to the RFC Editor"">RFC4846</a>] presented the copyright rules for the
Independent Submission stream. The present document is intended to
<span class="grey">Malis Informational [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc5745">RFC 5745</a> Rights for the IAB Stream December 2009</span>
be fully consistent with that section, and to update it by clarifying
the formal procedures that the IETF Trust will use to effect those
rules. In particular, it is the intention of this document to make
the copyright rules for IAB stream documents identical to those for
Independent Submission stream documents.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Goals</span>
The goal of the IAB stream of RFCs is to publish information from the
IAB to the Internet community. Consistent with the principle stated
for the Independent Submission stream in <a href="./rfc4846#section-8">Section 8 of RFC 4846</a>, this
objective will best be met with a liberal copyright policy on IAB
stream documents. Therefore, the IAB stream policy is to allow any
individual reading such documents to use the content thereof in any
manner. The only restriction is that proper credit ("attribution")
must be given. Lawyers describe this liberal policy by saying that
this stream normally permits "unlimited derivative works". The only
additional restriction for the use of IAB documents is that proper
credit ("attribution") must be given.
However, for a small subset of documents published as IAB stream
documents, such as output from other standards bodies, it is not
reasonable to permit unlimited derivative works. In such cases,
authors are permitted to request that the published IAB stream
documents permit no derivative works.
Note also that this unlimited derivative works policy applies to all
parts of an IAB stream document, including any code. Therefore, no
separate licensing procedure is required for extracting and adapting
code that is contained in an IAB stream document submitted under the
(preferred) unlimited derivative works terms. On the other hand,
code may not be extracted and adapted from IAB stream documents
submitted under the "no derivative works" terms.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Rules for Submission and Use of Material</span>
IAB stream authors will submit their material as Internet-Drafts.
These drafts will be submitted to, and stored in, the IETF Internet-
Drafts repository in the same fashion as IETF Internet-Drafts.
During Internet-Draft submission, authors who intend to submit their
document for publication in the IAB stream will grant rights as
described in [<a href="./rfc5378" title=""Rights Contributors Provide to the IETF Trust"">RFC5378</a>]. To request that the contribution be
published as an RFC that permits no derivative works, an author may
use the form specified for use with <a href="./rfc5378">RFC 5378</a>.
The IETF Trust will publish rules that provide that the Trust grants
to readers and users of material from IAB stream RFCs the right to
<span class="grey">Malis Informational [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc5745">RFC 5745</a> Rights for the IAB Stream December 2009</span>
make unlimited derivative works, unless the RFC specifies that no
derivative works are permitted. This will permit anyone to copy,
extract, modify, or otherwise use material from IAB stream RFCs as
long as suitable attribution is given.
Contributors of Internet-Drafts intended for the IAB stream will
include the appropriate boilerplate defined by the IETF Trust. This
boilerplate shall indicate compliance with <a href="./rfc5378">RFC 5378</a> and shall
explicitly indicate either that no derivative works can be based on
the contribution, or, as is preferred, that unlimited derivative
works may be crafted from the contribution.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Procedures Requested of the IETF Trust</span>
The IAB requests that the IETF Trust and its Trustees assist in
meeting the goals and procedures set forth in this document.
The Trustees are requested to publicly confirm their willingness and
ability to accept responsibility for the Intellectual Property Rights
for the IAB stream.
Specifically, the Trustees are asked to develop the necessary
boilerplate to enable the suitable marking of documents so that the
IETF Trust receives the rights as specified in <a href="./rfc5378">RFC 5378</a>. These
procedures need to also allow authors to indicate either no rights to
make derivative works, or preferentially, the right to make unlimited
derivative works from the documents. It is left to the Trust to
specify exactly how this shall be clearly indicated in each document.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Patent and Trademark Rules for the IAB Stream</span>
As specified above, contributors of documents for the IAB stream are
expected to use the IETF Internet-Draft process, complying therein
with the rules specified in the latest version of <a href="https://www.rfc-editor.org/bcp/bcp9">BCP 9</a>, whose
version at the time of writing was [<a href="./rfc2026" title=""The Internet Standards Process -- Revision 3"">RFC2026</a>]. This includes the
disclosure of Patent and Trademark issues that are known, or can be
reasonably expected to be known, to the contributor.
Disclosure of license terms for patents is also requested, as
specified in the most recent version of <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>. The version of <a href="https://www.rfc-editor.org/bcp/bcp79">BCP</a>
<a href="https://www.rfc-editor.org/bcp/bcp79">79</a> at the time of this writing was [<a href="./rfc3979" title=""Intellectual Property Rights in IETF Technology"">RFC3979</a>], updated by [<a href="./rfc4879" title=""Clarification of the Third Party Disclosure Procedure in RFC 3979"">RFC4879</a>].
The IAB stream has chosen to use the IETF's IPR disclosure mechanism,
www.ietf.org/ipr/, for this purpose. The IAB would prefer the most
liberal terms possible be made available for IAB stream documents.
Terms that do not require fees or licensing are preferable. Non-
discriminatory terms are strongly preferred over those that
discriminate among users. However, although disclosure is required
and the IAB may consider disclosures and terms in making a decision
<span class="grey">Malis Informational [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc5745">RFC 5745</a> Rights for the IAB Stream December 2009</span>
as to whether to submit a document for publication, there are no
specific requirements on the licensing terms for intellectual
property related to IAB stream publication.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
The integrity and quality of the IAB stream are the responsibility of
the IAB. This document does not change those responsibilities.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
[<a id="ref-RFC2026">RFC2026</a>] Bradner, S., "The Internet Standards Process -- Revision
3", <a href="https://www.rfc-editor.org/bcp/bcp9">BCP 9</a>, <a href="./rfc2026">RFC 2026</a>, October 1996.
[<a id="ref-RFC3979">RFC3979</a>] Bradner, S., Ed., "Intellectual Property Rights in IETF
Technology", <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>, <a href="./rfc3979">RFC 3979</a>, March 2005.
[<a id="ref-RFC4371">RFC4371</a>] Carpenter, B., Ed., and L. Lynch, Ed., "<a href="https://www.rfc-editor.org/bcp/bcp101">BCP 101</a> Update
for IPR Trust", <a href="https://www.rfc-editor.org/bcp/bcp101">BCP 101</a>, <a href="./rfc4371">RFC 4371</a>, January 2006.
[<a id="ref-RFC4844">RFC4844</a>] Daigle, L., Ed., and Internet Architecture Board, "The RFC
Series and RFC Editor", <a href="./rfc4844">RFC 4844</a>, July 2007.
[<a id="ref-RFC4846">RFC4846</a>] Klensin, J., Ed., and D. Thaler, Ed., "Independent
Submissions to the RFC Editor", <a href="./rfc4846">RFC 4846</a>, July 2007.
[<a id="ref-RFC4879">RFC4879</a>] Narten, T., "Clarification of the Third Party Disclosure
Procedure in <a href="./rfc3979">RFC 3979</a>", <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>, <a href="./rfc4879">RFC 4879</a>, April 2007.
[<a id="ref-RFC5378">RFC5378</a>] Bradner, S., Ed., and J. Contreras, Ed., "Rights
Contributors Provide to the IETF Trust", <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, <a href="./rfc5378">RFC 5378</a>,
November 2008.
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
[<a id="ref-RFC5377">RFC5377</a>] Halpern, J., Ed., "Advice to the Trustees of the IETF
Trust on Rights to Be Granted in IETF Documents", <a href="./rfc5377">RFC</a>
<a href="./rfc5377">5377</a>, November 2008.
[<a id="ref-RFC5744">RFC5744</a>] Braden, R. and J. Halpern, "Procedures for Rights Handling
in the RFC Independent Submission Stream", <a href="./rfc5744">RFC 5744</a>,
December 2009.
<span class="grey">Malis Informational [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc5745">RFC 5745</a> Rights for the IAB Stream December 2009</span>
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgements</span>
The author wishes to acknowledge that the majority of text of this
document was derived from [<a href="./rfc5744" title=""Procedures for Rights Handling in the RFC Independent Submission Stream"">RFC5744</a>], and wishes to thank the authors
of that document.
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. IAB Members at the Time of This Writing</span>
Marcelo Bagnulo
Gonzalo Camarillo
Stuart Cheshire
Vijay Gill
Russ Housley
John Klensin
Olaf Kolkman
Gregory Lebovitz
Andrew Malis
Danny McPherson
David Oran
Jon Peterson
Dave Thaler
Author's Address
Andrew G. Malis
Verizon Communications
117 West St.
Waltham, MA 02451
USA
EMail: [email protected]
IAB
EMail: [email protected]
Malis Informational [Page 6]
Annotations
Select text to annotate