How to Contribute Research Results to Internet Standardization
RFC 6417, “How to Contribute Research Results to Internet Standardization”, is an Informational document published in November 2011 by P. Eardley, L. Eggert, M. Bagnulo, R. Winter. The canonical text is published by the RFC Editor.
Abstract
The development of new technology is driven by scientific research. The Internet, with its roots in the ARPANET and NSFNet, is no exception. Many of the fundamental, long-term improvements to the architecture, security, end-to-end protocols and management of the Internet originate in the related academic research communities. Even shorter-term, more commercially driven extensions are oftentimes derived from academic research. When interoperability is required, the IETF standardizes such new technology. Timely and relevant standardization benefits from continuous input and review from the academic research community.
For an individual researcher, it can however be quite puzzling how to begin to most effectively participate in the IETF and arguably to a much lesser degree, the IRTF. The interactions in the IETF are much different than those in academic conferences, and effective participation follows different rules. The goal of this document is to highlight such differences and provide a rough guideline that will hopefully enable researchers new to the IETF to become successful contributors more quickly. This document is not an Internet Standards Track specification; it is published for informational purposes.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 6417 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6416 RTP Payload Format for MPEG-4 Audio/Visual Streams
- RFC 6418 Multiple Interfaces and Provisioning Domains Problem Statement
- RFC 6415 Web Host Metadata
- RFC 6419 Current Practices for Multiple-Interface Hosts
- RFC 6414 Benchmarking Terminology for Protection Performance
- RFC 6420 PIM Multi-Topology ID Join Attribute
- RFC 6413 Benchmarking Methodology for Link-State IGP Data-Plane Route Convergence
- RFC 6421 Crypto-Agility Requirements for Remote Authentication Dial-In User Service