Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Improving Awareness of Running Code: The Implementation Status Section (RFC7942)

IP.com Disclosure Number: IPCOM000246883D
Original Publication Date: 2016-Jul-01
Included in the Prior Art Database: 2016-Jul-12
Document File: 16 page(s) / 17K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

Y. Sheffer: AUTHOR [+2]

Abstract

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 specifications that have gone through to publication as Proposed Standard RFCs without implementation. Some of them may never get implemented.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 16% of the total text.

Internet Engineering Task Force (IETF)                        Y. Sheffer Request for Comments: 7942                                        Intuit BCP: 205                                                       A. Farrel Obsoletes: 6982                                         Juniper Networks Category: Best Current Practice                                July 2016 ISSN: 2070-1721

  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.

   This process is not mandatory.  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.  This document obsoletes RFC 6982,    advancing it to a Best Current Practice.

Status of This Memo

   This memo documents an Internet Best Current Practice.

   This document is a product of the Internet Engineering Task Force    (IETF).  It has been approved for publication by the Internet    Engineering Steering Group (IESG).  Further information on BCPs is    available in Section 2 of RFC 7841.

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

Sheffer & Farrel          Best Current Practice                 [Page 1]
 RFC 7942                      Running Code                     July 2016

 Copyright Notice

   Copyright (c) 2016 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  . . . . . . . . . . . . . . . . . . . . . . ....