Creating an IETF Working Group Draft
draft-crocker-id-adoption-04

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in gen area)
Last updated 2013-10-12 (latest revision 2013-10-07)
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Reviews
Stream WG state (None)
Document shepherd Barry Leiba
Shepherd write-up Show (last changed 2013-10-12)
IESG IESG state AD Evaluation::Revised I-D Needed
Consensus Boilerplate Unknown
Telechat date
Responsible AD Barry Leiba
Send notices to adrian@olddog.co.uk, dcrocker@bbiw.net, barryleiba@computer.org
Network Working Group                                          A. Farrel
Internet-Draft                                          Juniper Networks
Intended status: Informational                           D. Crocker, Ed.
Expires: April 10, 2014                      Brandenburg InternetWorking
                                                        October 07, 2013

                  Creating an IETF Working Group Draft
                      draft-crocker-id-adoption-04

Abstract

   The productive output of an IETF working group is documents, as
   mandated by the working group's charter.  When a working group is
   ready to develop a particular document it usually "adopts" it as a
   working group draft.  The document that a working group adopts and
   then develops further is based on initial input at varying levels of
   maturity.  An initial working group draft might be a document already
   in wide use, or it might be a blank sheet, wholly created by the
   working group, or it might represent any level of maturity in
   between.  This document discusses how a working group typically
   handles the formal documents that it targets for publication.

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 April 10, 2014.

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

Farrel & Crocker         Expires April 10, 2014                 [Page 1]
Internet-Draft    Creating an IETF Working Group Draft      October 2013

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  What is a Working Group Draft?  . . . . . . . . . . . . .   3
     1.2.  Working Group Authority and Consensus . . . . . . . . . .   3
     1.3.  Questions Considered in This Document . . . . . . . . . .   4
   2.  Adoption Sequence . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Typical Steps . . . . . . . . . . . . . . . . . . . . . .   5
     2.2.  Criteria for Adoption . . . . . . . . . . . . . . . . . .   5
   3.  Authors/Editors . . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Document History and Stability  . . . . . . . . . . . . . . .   7
   5.  Some Issues for Consideration . . . . . . . . . . . . . . . .   9
     5.1.  Individual I-Ds Under WG Care . . . . . . . . . . . . . .   9
     5.2.  Competing Drafts  . . . . . . . . . . . . . . . . . . . .  10
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  11
   8.  Informative References  . . . . . . . . . . . . . . . . . . .  12
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   The productive output of an IETF working group is documents, as
   mandated by the working group's charter.  Working groups develop
   these documents based on initial input of varying levels of maturity.
   An initial working group draft might be a document already in wide
   use, or it might be a blank sheet, wholly created by the working
   group, or it might represent any level of maturity in between.  This
   document discusses how a working group typically handles the formal
   documents that it targets for publication.  The discussion applies
   only to the IETF and does not cover IRTF groups, where practices vary
   widely.

   Within the general constraints of formal IETF process and the
   specific constraints of a working group's charter, there can be
   considerable freedom in the adoption and development of drafts.  As
   with most IETF activities, the ultimate arbiter of such choices is
   working group agreement, within the constraints of its charter.  As
Show full document text