RFC 4879

Clarification of the Third Party Disclosure Procedure in RFC 3979

📅 published April 2007, from ietf

RFC 4879: Clarification of the Third Party Disclosure Procedure in RFC 3979 🎀

  • Series: Network Working Group, Request for Comments 4879 💌
  • Author: Thomas (Thomas Narten) of IBM 🧑‍💻
  • Category: Best Current Practice, BCP 79 ✨
  • Date: April 2007 📅
  • Updates: RFC 3979 🔁

Status of This Memo 🎀

This doc is a Best Current Practice for the Internet community, and the IETF is asking for discussion and suggestions on how to make it better 💖 Distribution of this memo is unlimited.

Copyright (C) The IETF Trust (2007).

Abstract 🌸

This doc clarifies and updates one single sentence in RFC 3979 🫶 When third party Intellectual Property Rights (IPR) disclosures get made, the plan is for the IETF Executive Director to tell the IPR holder that a third party disclosure was filed, and to ask the IPR holder if they have any disclosure that needs to be made, following the RFC 3979 rules that apply 💅

1. Introduction 🦋

Okay so this doc clarifies and updates one single sentence in RFC 3979 [RFC3979] 🥹 Basically, when third party IPR disclosures are made, the IETF Executive Director is supposed to notify the IPR holder that a third party disclosure has been filed, and ask the IPR holder whether they have any disclosure that needs to be made, per the applicable RFC 3979 rules ✨

This document updates RFC 3979 🔥

2. The Fix 💅

RFC 3979, Section 4 (C), says:

 (C) Where Intellectual Property Rights have been disclosed for IETF
     Documents as provided in Section 6 of this document, the IETF
     Executive Director shall request from the discloser of such IPR,
     a written assurance that upon approval by the IESG for
     publication as RFCs of the relevant IETF specification(s), all
     persons will be able to obtain the right to implement, use,
     distribute and exercise other rights with respect to
     Implementing Technology under one of the licensing options
     specified in Section 6.5 below unless such a statement has
     already been submitted.

Here's the thing 👀 In the case of third party disclosures, it makes zero sense to ask the discloser about potential licensing terms, because they don't own the IPR. It only makes sense to ask the IPR holder 🙄💀

So this document updates RFC 3979 by changing the word "discloser" to "holder" in the text above. Main character fix, periodt 👑

3. Security Considerations 🔐

This document has no known security implications 🧚

4. Normative Reference 📚

[RFC3979]  Bradner, S., "Intellectual Property Rights in IETF
           Technology", BCP 79, RFC 3979, March 2005.

Author's Address 💌

Thomas Narten
IBM Corporation
3039 Cornwallis Ave.
PO Box 12195 - BRQA/502
Research Triangle Park, NC 27709-2195

Phone: 919-254-7798
EMail: narten@us.ibm.com

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 license 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 licenses to be made available, or the result of an attempt 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 required to implement this standard. Please send that information to the IETF at ietf-ipr@ietf.org 💜

Acknowledgement 🌈

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

📦 where this page comes from