How to Contribute Research Results to Internet Standardization
RFC 6417

Document Type RFC - Informational (November 2011; No errata)
Last updated 2015-10-14
Stream ISE
Formats plain text pdf html bibtex
Stream ISE state (None)
Consensus Boilerplate Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 6417 (Informational)
Telechat date
Responsible AD Wesley Eddy
IESG note ISE Submission
Send notices to rfc-ise@rfc-editor.org
Independent Submission                                        P. Eardley
Request for Comments: 6417                                            BT
Category: Informational                                        L. Eggert
ISSN: 2070-1721                                                    Nokia
                                                              M. Bagnulo
                                                                    UC3M
                                                               R. Winter
                                                              NEC Europe
                                                           November 2011

     How to Contribute Research Results to Internet Standardization

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.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This is a contribution to the RFC Series, independently of any other
   RFC stream.  The RFC Editor has chosen to publish this document at
   its discretion and makes no statement about its value for
   implementation or deployment.  Documents approved for publication by
   the RFC Editor are not a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

Eardley, et al.               Informational                     [Page 1]
RFC 6417            Contributing Research to the IETF      November 2011

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6417.

Copyright Notice

   Copyright (c) 2011 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.

Table of Contents

   1. Introduction ....................................................3
   2. Is the IETF the Right Venue? ....................................4
   3. How to Get the IETF to Start Work on Your Proposal? .............6
      3.1. Identify the Right Part of the IETF ........................6
      3.2. Build a Community ..........................................6
      3.3. Outline Your Protocol ......................................7
      3.4. Establish a New Working Group ..............................8
   4. How to Increase the Chances that the IETF Successfully
      Standardizes Your Proposal ......................................8
      4.1. Commit Enough Time, Energy, and Perseverance ...............8
      4.2. Be Open and Focus Out ......................................9
      4.3. Seek Resolution, Not Perfection ...........................10
      4.4. Implement .................................................10
   5. Examples .......................................................11
      5.1. Multipath TCP .............................................11
      5.2. Congestion Exposure .......................................12
   6. Security Considerations ........................................13
   7. Acknowledgments ................................................13
   8. Informative References .........................................13

Eardley, et al.               Informational                     [Page 2]
RFC 6417            Contributing Research to the IETF      November 2011

1.  Introduction
Show full document text