Improving Awareness of Running Code: The Implementation Status Section
RFC 6982

 
Document Type RFC - Experimental (July 2013; No errata)
Last updated 2013-07-17
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 6982 (Experimental)
Telechat date
Responsible AD Stephen Farrell
Send notices to yaronf.ietf@gmail.com, adrian@olddog.co.uk, draft-sheffer-running-code@ietf.org
IANA IANA review state Version Changed - Review Needed
IANA action state No IC
Internet Engineering Task Force (IETF)                        Y. Sheffer
Request for Comments: 6982                                      Porticor
Category: Experimental                                         A. Farrel
ISSN: 2070-1721                                                  Juniper
                                                               July 2013

 Improving Awareness of Running Code: The Implementation Status Section

Abstract

   This document describes a simple process that allows authors of
   Internet-Drafts to record the status of known implementations by
   including an Implementation Status section.  This will allow
   reviewers and working groups to assign due consideration to documents
   that have the benefit of running code, which may serve as evidence of
   valuable experimentation and feedback that have made the implemented
   protocols more mature.

   The process in this document is offered as an experiment.  Authors of
   Internet-Drafts are encouraged to consider using the process for
   their documents, and working groups are invited to think about
   applying the process to all of their protocol specifications.  The
   authors of this document intend to collate experiences with this
   experiment and to report them to the community.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for examination, experimental implementation, and
   evaluation.

   This document defines an Experimental Protocol for the Internet
   community.  This document is a product of the Internet Engineering
   Task Force (IETF).  It represents the consensus of the IETF
   community.  It has received public review and has been approved for
   publication by the Internet Engineering Steering Group (IESG).  Not
   all documents approved by the IESG are a candidate for any level of
   Internet Standard; see Section 2 of RFC 5741.

   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/rfc6982.

Sheffer & Farrel              Experimental                      [Page 1]
RFC 6982                      Running Code                     July 2013

Copyright Notice

   Copyright (c) 2013 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.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  The "Implementation Status" Section . . . . . . . . . . . . .   4
   2.1.  Introductory Text . . . . . . . . . . . . . . . . . . . . .   5
   3.  Alternative Formats . . . . . . . . . . . . . . . . . . . . .   6
   4.  Benefits  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Process Experiment  . . . . . . . . . . . . . . . . . . . . .   7
   5.1.  Duration  . . . . . . . . . . . . . . . . . . . . . . . . .   7
   5.2.  Summary Report  . . . . . . . . . . . . . . . . . . . . . .   8
   5.3.  Success Criteria  . . . . . . . . . . . . . . . . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   8.  Informative References  . . . . . . . . . . . . . . . . . . .   9

Sheffer & Farrel              Experimental                      [Page 2]
RFC 6982                      Running Code                     July 2013

1.  Introduction

   Most IETF participants are familiar with the saying "rough consensus
   and running code" [Tao] and can identify with its pragmatic approach.
   However, implementation is not a requirement for publication as an
   RFC.  There are many examples of Internet-Drafts containing protocol
   specification that have gone through to publication as Proposed
   Standard RFCs without implementation.  Some of them may never get
   implemented.

   Over time, a variety of policies have been applied within the IETF to
   consider running code.  In the Routing Area, it used to be a
   requirement that one or more implementations must exist before an
   Internet-Draft could be published as a Proposed Standard RFC
   [RFC1264].  That RFC was later obsoleted and the requirement for
Show full document text