RFC 4841

RFC 4841: RFC 4181 Update to Recognize the IETF Trust 🎀

Okay bestie, this one is a BCP (Best Current Practice, BCP 111 🦋) from March 2007, and it's written by C. Heard, Ed. It's categorised as Best Current Practice and it's part of the Network Working Group 💅. It updates RFC 4181 and doesn't obsolete anything. Okay so it's a tiny little doc but it's giving main character energy ✨.

---

Status of This Memo 📜

This document is an Internet Best Current Practice for the Internet Community 🌸. It's asking for discussion and suggestions for improvements, and anyone can distribute it as much as they want (the distribution is unlimited) 💖.

Copyright Notice 🎀

Copyright (C) The IETF Trust (2007). ✨

Abstract 🦋

Okay so this doc updates RFC 4181, the "Guidelines for Authors and Reviewers of MIB Documents" 📚, so that it recognises that the IETF Trust now exists 👑.

1. Introduction 🧚

So the IETF Trust was created, and that meant some copyright notices had to change. RFC 3978 [RFC3978] requires those notices in IETF documents, and the changes were published in RFC 4748 [RFC4748]. This document updates RFC 4181 [RFC4181] so it lines up with those changes 🫶.

2. Updates to RFC 4181 💅

The text of RFC 4181 is updated as set out below to reflect the creation of the IETF Trust. This is the whole plan, no cap 🔥.

2.1. Updates to Section 3.7 🍓

In the copyright notice templates in Section 3.7, you replace every single occurrence of "The Internet Society" with "The IETF Trust". Iconic, right? 💜

3. Security Considerations 🙈

The updates in this document have no impact on the security of the Internet. Honestly, nothing risky here, periodt 💖.

4. Normative References 📚

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

[RFC4748] Bradner, S., "RFC 3978 Update to Recognize the IETF Trust", BCP 78, RFC 4748, October 2006.

[RFC4181] Heard, C., "Guidelines for Authors and Reviewers of MIB Documents", BCP 111, RFC 4181, September 2005.

---

Editor's Address 💌

C. M. Heard 158 South Madison Ave. #207 Pasadena, CA 91101-2569 USA

Phone: +1 626 795 5311 EMail: heard@pobox.com

Full Copyright Statement ⭐

Copyright (C) The IETF Trust (2007).

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, THE IETF TRUST 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 in this document, or on the extent to which any licence under such rights might or might not be available. It also doesn't claim to have made any independent effort to identify any such rights. Information on the procedures for rights in RFC documents can be found in BCP 78 and BCP 79 🌈.

Copies of IPR disclosures made to the IETF Secretariat, any assurances of licences to be made available, or the result of an attempt to obtain a general licence 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. Send that info to the IETF at ietf-ipr@ietf.org. 💜

Acknowledgement 🫶

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