Governing RFCs

The RFC Editor function is currently defined and governed by the following RFCs:

  • RFC 2026: Bradner, S., “The Internet Standards Process — Revision 3”, BCP 9, RFC 2026, October 1996.
  • RFC 4844: Daigle, L. and Internet Architecture Board, “The RFC Series and RFC Editor”, RFC 4844, July 2007.
  • RFC 4846: Klensin, J. and D. Thaler, “Independent Submissions to the RFC Editor”, RFC 4846, July 2007.
  • RFC 6410: Housley, R., Crocker, D., and E. Burger, “Reducing the Standards Track to Two Maturity Levels”, BCP 9, RFC 6410, October 2011.
  • RFC 6548: Brownlee, N., Ed., and IAB, “Independent Submission Editor Model”, RFC 6548, June 2012.
  • RFC 6635: Kolkman, O., Ed., Halpern, J., Ed., and IAB, “RFC Editor Model (Version 2)”, RFC 6635, June 2012.

The following RFCs define particular RFC contents:

The following RFCs govern intellectual property issues related to RFCs:

  • RFC 5378: Bradner, S., Ed., and J. Contreras, Ed., “Rights Contributors Provide to the IETF Trust”, BCP 78, RFC 5378, November 2008.
  • RFC 5743: Falk, A., “Definition of an Internet Research Task Force (IRTF) Document Stream”, RFC 5743, December 2009.
  • RFC 5744: Braden, R. and J. Halpern, “Procedures for Rights Handling in the RFC Independent Submission Stream”, RFC 5744, December 2009.
  • RFC 5745: Malis, A., Ed., and IAB, “Procedures for Rights Handling in the RFC IAB Stream”, RFC 5745, December 2009.
  • RFC 8179: Bradner, S. and J. Contreras, “Intellectual Property Rights in IETF Technology”, BCP 79, RFC 8179, May 2017.

In addition to RFC 8126, the following RFCs govern RFC Editor actions with respect to particular IANA registrations:

  • RFC 4289: Freed, N. and J. Klensin, “Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures”, RFC 4289, December 2005.
  • RFC 6838: Freed, N., Klensin, J., and T. Hansen, “Media Type Specifications and Registration Procedures”, BCP 13, RFC 6838, January 2013.
  • RFC 7595: Thaler, D., Ed., Hansen, T., and T. Hardie, “Guidelines and Registration Procedures for URI Schemes”, BCP 35, RFC 7595, June 2015.
  • RFC 8141: Saint-Andre, P. and J. Klensin, “Uniform Resource Names (URNs)”, RFC 8141, April 2017.