Improving Awareness of Running Code: the Implementation Status Section
draft-sheffer-running-code-03

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-04-12 (latest revision 2013-04-05)
Stream IETF
Intended RFC status Experimental
Formats plain text pdf html
Stream WG state (None)
Document shepherd None
IESG IESG state AD is watching
Telechat date
Responsible AD Stephen Farrell
Send notices to yaronf.ietf@gmail.com, adrian@olddog.co.uk, draft-sheffer-running-code@tools.ietf.org
Network Working Group                                         Y. Sheffer
Internet-Draft                                                  Porticor
Intended status: Experimental                                  A. Farrel
Expires: October 7, 2013                                         Juniper
                                                           April 5, 2013

 Improving Awareness of Running Code: the Implementation Status Section
                     draft-sheffer-running-code-03

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 and potentially reward the
   documented protocols by treating the documents with implementations
   preferentially.

   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 Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on October 7, 2013.

Copyright Notice

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

Sheffer & Farrel         Expires October 7, 2013                [Page 1]
Internet-Draft                Running Code                    April 2013

   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 . . . . . . . . . . . . . . . . . . . . . . 4
   3.    Alternative Formats . . . . . . . . . . . . . . . . . . . . . 5
   4.    Benefits  . . . . . . . . . . . . . . . . . . . . . . . . . . 5
   5.    Process Experiment  . . . . . . . . . . . . . . . . . . . . . 6
   5.1.  Duration  . . . . . . . . . . . . . . . . . . . . . . . . . . 6
   5.2.  Summary Report  . . . . . . . . . . . . . . . . . . . . . . . 7
   5.3.  Success Criteria  . . . . . . . . . . . . . . . . . . . . . . 7
   6.    Implementation Status . . . . . . . . . . . . . . . . . . . . 7
   6.1.  Current Drafts Using This Guidance  . . . . . . . . . . . . . 7
   7.    Security Considerations . . . . . . . . . . . . . . . . . . . 8
   8.    IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
   9.    Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . 8
   10.   Informative References  . . . . . . . . . . . . . . . . . . . 8
         Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . 9

Sheffer & Farrel         Expires October 7, 2013                [Page 2]
Internet-Draft                Running Code                    April 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, 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 implemented within the
   IETF to consider running code.  In the Routing Area it used to be a
Show full document text