Browse Prior Art Database

A Model for IETF Process Experiments (RFC3933)

IP.com Disclosure Number: IPCOM000032483D
Original Publication Date: 2004-Nov-01
Included in the Prior Art Database: 2004-Nov-06
Document File: 8 page(s) / 14K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Klensin: AUTHOR [+2]

Abstract

The IETF has designed process changes over the last ten years in one of two ways: announcement by the IESG, sometimes based on informal agreements with limited community involvement and awareness, and formal use of the same mechanism used for protocol specification. The first mechanism has often proven to be too lightweight, the second too heavyweight.

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

Network Working Group                                         J. Klensin

Request for Comments: 3933                                    S. Dawkins

BCP: 93                                                    November 2004

Category: Best Current Practice

                  A Model for IETF Process Experiments

Status of this Memo

   This document specifies an Internet Best Current Practices for the

   Internet Community, and requests discussion and suggestions for

   improvements.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2004).

Abstract

   The IETF has designed process changes over the last ten years in one

   of two ways: announcement by the IESG, sometimes based on informal

   agreements with limited community involvement and awareness, and

   formal use of the same mechanism used for protocol specification.

   The first mechanism has often proven to be too lightweight, the

   second too heavyweight.

   This document specifies a middle-ground approach to the system of

   making changes to IETF process, one that relies heavily on a "propose

   and carry out an experiment, evaluate the experiment, and then

   establish permanent procedures based on operational experience" model

   rather than those previously attempted.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2

   2.  Background and Specification . . . . . . . . . . . . . . . . . 2

   3.  Security Considerations  . . . . . . . . . . . . . . . . . . . 5

   4.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5

   5.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 5

       5.1.  Normative Reference. . . . . . . . . . . . . . . . . . . 5

       5.2.  Informative References . . . . . . . . . . . . . . . . . 5

   6.  Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 6

       Full Copyright Statement . . . . . . . . . . . . . . . . . . . 7

Klensin & Dawkins        Best Current Practice                  [Page 1]

RFC 3933          A Model for IETF Process Experiments     November 2004

1.  Introduction

   This document specifies a middle-ground approach to the system of

   making changes to IETF process, one that relies heavily on a "propose

   and carry out an experiment, evaluate the experiment, and then

   establish permanent procedures based on operational experience" model

   rather than those previously attempted.

2.  Background and Specification

   Since the 1992 changes documented in [RFC1396], the IETF has used two

   mechanisms for process changes.

   1. IESG has adopted a number of procedural changes on its own

      initiative and documented them informally, utilizing the wide

   ...