Skip to main content

IESG Procedures for Handling of Independent and IRTF Stream Submissions
RFC 5742 also known as BCP 92

Document Type RFC - Best Current Practice (December 2009)
Obsoletes RFC 3932
Was draft-housley-iesg-rfc3932bis (individual in gen area)
Authors Russ Housley , Harald T. Alvestrand
Last updated 2019-06-15
RFC stream Internet Engineering Task Force (IETF)
Formats
IESG Responsible AD Jari Arkko
Send notices to (None)
RFC 5742
amp; Housley     Best Current Practice                  [Page 8]
RFC 5742                   Update to RFC 3932              December 2009

9.2.  Informative References

   [I1]  Alvestrand, H., "The IESG and RFC Editor Documents:
         Procedures", BCP 92, RFC 3932, October 2004.

   [I2]  Falk, A., "Definition of an Internet Research Task Force (IRTF)
         Document Stream", RFC 5743, December 2009.

   [I3]  Klensin, J., Ed., and D. Thaler, Ed., "Independent Submissions
         to the RFC Editor", RFC 4846, July 2007.

   [I4]  Internet Architecture Board and B. Carpenter, Ed., "Charter of
         the Internet Architecture Board (IAB)", BCP 39, RFC 2850, May
         2000.

   [I5]  Alvestrand, H., "An IESG charter", RFC 3710, February 2004.

   [I6]  Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
         Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.

Authors' Address

   Harald Alvestrand
   EMail: harald@alvestrand.no

   Russell Housley
   EMail: housley@vigilsec.com

Alvestrand & Housley     Best Current Practice                  [Page 9]