[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 RFC 4748

Network Working Group                                        S. Bradner
Internet-Draft                                       Harvard University
Updates: RFC 3978                                                Editor
                                                         September 2006

              RFC 3978 Update to recognize the IETF Trust

               <draft-ietf-ipr-ietf-trust-update-03.txt>

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   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
   aware will be disclosed, in accordance with Section 6 of BCP 79.


   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on February 5, 2007.

Abstract
   This document updates RFC 3978 "IETF Rights in Contributions" to
   recognize that the IETF Trust is now the proper custodian of all
   IETF-related intellectual property rights.

   This document does not constrain how the IETF Trust exercises those
   rights.


Copyright Notice
      Copyright (C) The Internet Society. (2006)

1. Introduction



Bradner                                                         [Page 1]

Internet-Draft       RFC 3978 Update for IETF Trust       September 2006


1.1  IETF Trust

   Currently the IETF requires that authors of Contributions to 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
   permissions as part of the process of submitting such Contribution.
   These rights and permissions are detailed in "IETF Rights in
   Contributions" (RFC 3978 - BCP 78) [RFC3978].

   The IETF Trust was recently formed to act as the administrative
   custodian of all copyrights and other intellectual property rights
   relating to the IETF Standards Process that had previously been held
   by ISOC and CNRI (See [IETF Trust Agreement]).

   The IETF is supported by an IETF Administrative Support Activity
   (IASA) defined in BCP 101 [BCP101].  BCP 101 was updated by [RFC4371]
   to recognize the creation of the IETF Trust.

   This document updates RFC 3978 in order to recognize the IETF Trust
   and to implement the structure needed to support it.  Most
   importantly, it alters the license-grant path as follows:  whereas
   previously authors of Contributions to the IETF would grant a license
   ISOC, such authors will grant a license to the IETF Trust (in Section
   3.3).  This document concerns itself only with changes to RFC 3978
   needed to recognize the creation of the IETF Trust.

   This introductory section is to provide context for the reader.
   Section 2 of this document is intended to be normative.


2. Updates to RFC 3978

   The text of RFC 3978 is hereby updated as set forth below to reflect
   the creation of the IETF Trust.

2.1. Update introduction

   In the third paragraph of Section 2 replace "IETF and Internet
   Society (ISOC)" with "IETF Trust and the IETF" and replace "IETF and
   ISOC" with "IETF Trust and the IETF."

2.2. Update Section 3.3

   In section 3.3 replace two instances of "ISOC and the IETF" and one
   instance of "IETF and ISOC" with "IETF Trust and the IETF."

2.3. Update Section 3.4




Bradner                                                         [Page 2]

Internet-Draft       RFC 3978 Update for IETF Trust       September 2006


   In Section 3.4(b) add "IETF Trust, " after "IETF,".

2.4. Update Section 4.2

   In section 4.2 replace two instances of "ISOC and the IETF" and one
   instance of "IETF and ISOC" with "IETF Trust and the IETF."

2.5. Update Section 5

   In Section 5 change two instances of "ISOC" to "IETF Trust."

2.6. Update copyright statement

   Replace "Internet Society" with "IETF Trust" in the copyright
   statement in Section 5.4.

2.7. Update Section 5.5

   In Section 5.5 insert ", THE IETF TRUST" after "INTERNET SOCIETY".

2.8. Update Section 5.6

   In Section 5.6, replace all occurrences of "Internet Society" with
   "IETF Trust".

2.9. Update Section 7.1

   In Section 7.1, replace two instances of "IETF/ISOC" with "IETF Trust
   and IETF".

2.10. Update Section 8

   In Section 8, insert ", the IETF Trust" after "ISOC".

3. References

3.1. Normative References

   [RFC3978] Bradner, S., Ed., "IETF Rights in Contributions", BCP 78,
      RFC 3978, March 2005.

   [BCP101] Austein, R., and B. Wijnen, "Structure of the IETF
      Administrative Support Activity (IASA)," BCP 101, RFC 4071, April
      2005.

   [RFC4371] Carpenter, B., and L. Lynch Ed., " BCP 101 Update for IPR
      Trust," RFC 4371, January 2006




Bradner                                                         [Page 3]

Internet-Draft       RFC 3978 Update for IETF Trust       September 2006


   [IETF Trust Agreement]
      www.ietf.org/trust/IETFtrustAgreement20051208.pdf

4. Security Considerations

   This type of process document does not have a direct impact on the
   security of the Internet or Internet protocols.

5. IANA Considerations

   (Note to RFC Editor - this section to be removed before publication
   as a RFC)

   There are no IANA actions required by this document.

6. Editor's Address

   Scott Bradner
   Harvard University
   29 Oxford St.
   Cambridge MA, 02138

   Phone: +1 617 495 3864
   EMail: sob@harvard.edu


7.   Full copyright statement

   Copyright (C) The Internet Society (2006).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

   Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   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
   made any independent effort to identify any such rights.  Information



Bradner                                                         [Page 4]

Internet-Draft       RFC 3978 Update for IETF Trust       September 2006


   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 IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license 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 repository at
   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 this standard.  Please address the
   information to the IETF at ietf-ipr@ietf.org.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.

































Bradner                                                         [Page 5]


Html markup produced by rfcmarkup 1.107, available from http://tools.ietf.org/tools/rfcmarkup/