RFC 4371

BCP 101 Update for IPR Trust

📅 published January 2006, from ietf

BCP 101 Update for IPR Trust 🎀

Request for Comments: 4371 💖 BCP: 101 ✨ Updates: 4071 🦋 Category: Best Current Practice 👑 Date: January 2006 🍓

Okay so this one is an RFC about RFCs. 💅 It's a Best Current Practice (BCP 101) that updates RFC 4071, and it was written by Brian Carpenter, Ed. (IBM) and Lucy Lynch, Ed. (UO). It came out in January 2006. Obviously the vibe is "we're switching who holds the IETF's IPR" 🫶

Status of This Memo ✨

This document is a BCP for the Internet Community, and the authors are literally asking for discussion and suggestions for improvements 🙈 Distribution of this memo is unlimited, so share the tea.

Copyright (C) The Internet Society (2006).

Abstract 🦋

This doc updates BCP 101 so it reflects the new IETF Intellectual Property Trust. That's the whole plot 🎀

Table of Contents 📜

1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 1
2.  Updates to RFC 4071 . . . . . . . . . . . . . . . . . . . . . . 2
3.  Security Considerations . . . . . . . . . . . . . . . . . . . . 2
4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 2
5.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 3
    5.1.  Normative References  . . . . . . . . . . . . . . . . . . 3
    5.2.  Informative References  . . . . . . . . . . . . . . . . . 3

1. Introduction 🧚

Okay so the first version of BCP 101, which is RFC 4071 [1], assumed that the vehicle for certain IETF-related Intellectual Property Rights (IPR) would be the Internet Society (ISOC). 🌸 Since then, an IETF Trust has been created to hold that IPR. This document appropriately updates RFC 4071. 💜

This update comes into force as soon as it has been approved by the IESG and the IETF Trust Agreement [2] has been formally signed by its Settlors and initial Trustees. ✨

Terms and abbreviations used in this document are defined in RFC 4071. 🫶

2. Updates to RFC 4071 👑

So a Trust ("the IETF Trust") has been formed to acquire, hold, maintain, and license certain existing and future intellectual property and other property used in connection with the administration of the IETF. 🌈 The Trust was formed by the signatures of its Settlors and initial Trustees. The Settlors, who contributed initial intellectual property to the Trust, were ISOC and the Corporation for National Research Initiatives. The Trustees of the IETF Trust are the members of the IAOC, and the Beneficiary of the IETF Trust is the IETF as a whole. 🎀

In its administration of IPR under the terms of BCP 101, the IASA, including the IAD and the IAOC, will treat the IETF Trust rather than ISOC as the proper entity for ownership and licensing of IETF IPR. 💅 Specifically, references to ISOC in sections 3.1, 5.3, and 7 of [1] shall be interpreted as referring to the IETF Trust wherever IPR issues are concerned. The duty to serve as Trustees is added to section 3.2 of [1]. 🦋

3. Security Considerations 🔥

This document has no security implications for the Internet. 🫶

4. Acknowledgements 🌸

The members of the IAOC when this document was written were:

   Brian Carpenter
   Steve Crocker
   Leslie Daigle
   Ed Juskevicius
   Kurtis Lindqvist
   Lucy Lynch
   Ray Pelletier
   Lynn St Amour
   Jonne Soininen

Useful comments came from Harald Alvestrand, and comments on RFC 4071 by Patrice Lyons helped shape this document. 💖 It was produced with the xml2rfc tool [3].

5. References 📚

5.1. Normative References

5.2. Informative References

  • [3] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, June 1999.

Authors' Addresses 🧚

Brian Carpenter (Ed.)
IBM
8 Chemin de Blandonnet
1214 Vernier
Switzerland

EMail: brc@zurich.ibm.com


Lucy Lynch (Ed.)
University of Oregon
1225 Kincaid St
Eugene, Oregon 97403
USA

Phone: +1 541 346 1774
EMail: llynch@darkwing.uoregon.edu

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 on 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 here, or on whether any license under those rights is available. It also hasn't made any independent effort to find such rights. For the procedures around rights in RFC documents, check out BCP 78 and BCP 79. 🎀

Copies of IPR disclosures made to the IETF Secretariat, assurances of licenses, and the results of attempts to get a general license for implementers or users are available from the IETF's online IPR repository at http://www.ietf.org/ipr. 🦋

The IETF invites any interested party to bring any copyrights, patents, patent applications, or other proprietary rights that may cover technology required to implement this standard to its attention. Send that info to ietf-ipr@ietf.org. 💅

Acknowledgement 🫶

Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). 🌟

📦 where this page comes from