RFC 7221 on Handling of Internet-Drafts by IETF Working Groups
rfc-editor@rfc-editor.org Tue, 29 April 2014 17:07 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C5331A091D for <ietf-announce@ietfa.amsl.com>; Tue, 29 Apr 2014 10:07:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.853
X-Spam-Level:
X-Spam-Status: No, score=-104.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4-DZKJ3fX23z for <ietf-announce@ietfa.amsl.com>; Tue, 29 Apr 2014 10:06:57 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id C89FA1A0941 for <ietf-announce@ietf.org>; Tue, 29 Apr 2014 10:06:54 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D7E01180014; Tue, 29 Apr 2014 10:06:43 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7221 on Handling of Internet-Drafts by IETF Working Groups
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140429170643.D7E01180014@rfc-editor.org>
Date: Tue, 29 Apr 2014 10:06:43 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/7Fn-02-3XDi-j8EOI4t-7fVsVe8
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 17:07:03 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7221
Title: Handling of Internet-Drafts by IETF
Working Groups
Author: A. Farrel, D. Crocker, Ed.
Status: Informational
Stream: IETF
Date: April 2014
Mailbox: adrian@olddog.co.uk,
dcrocker@bbiw.net
Pages: 14
Characters: 31669
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-crocker-id-adoption-09.txt
URL: http://www.rfc-editor.org/rfc/rfc7221.txt
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, the most common mechanism is
for it to "adopt" an existing document as a starting point. 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.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://www.rfc-editor.org/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC