[OPS-AREA] FW: RFC 4858 on Document Shepherding from Working Group Last Call toPublication

"Romascanu, Dan \(Dan\)" <dromasca@avaya.com> Thu, 10 May 2007 11:36 UTC

Return-path: <ops-area-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hm6wO-0005Vx-E5; Thu, 10 May 2007 07:36:12 -0400
Received: from ops-area by megatron.ietf.org with local (Exim 4.43) id 1Hm6wM-0005Uf-Rh for ops-area-confirm+ok@megatron.ietf.org; Thu, 10 May 2007 07:36:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hm6wJ-0005UW-Ur for ops-area@ietf.org; Thu, 10 May 2007 07:36:07 -0400
Received: from nj300815-nj-outbound.net.avaya.com ([198.152.12.100] helo=nj300815-nj-outbound.avaya.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hm6wI-0006jz-M7 for ops-area@ietf.org; Thu, 10 May 2007 07:36:07 -0400
Received: from 51.105.64.135.in-addr.arpa (HELO IS0004AVEXU1.global.avaya.com) ([135.64.105.51]) by nj300815-nj-outbound.avaya.com with ESMTP; 10 May 2007 07:36:06 -0400
X-IronPort-AV: i="4.14,517,1170651600"; d="scan'208"; a="14098761:sNHT10933020"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 10 May 2007 14:35:49 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0CCFB086@is0004avexu1.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: RFC 4858 on Document Shepherding from Working Group Last Call toPublication
Thread-Index: AceSjZl5T0CFbcyYTri6hRwCKvNMQwAabz4A
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: ops-area@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Subject: [OPS-AREA] FW: RFC 4858 on Document Shepherding from Working Group Last Call toPublication
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
Errors-To: ops-area-bounces@ietf.org

 


 

-----Original Message-----
From: rfc-editor@rfc-editor.org [mailto:rfc-editor@rfc-editor.org] 
Sent: Thursday, May 10, 2007 1:55 AM
To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
Cc: rfc-editor@rfc-editor.org
Subject: RFC 4858 on Document Shepherding from Working Group Last Call
toPublication


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4858

        Title:      Document Shepherding from Working Group 
                    Last Call to Publication 
        Author:     H. Levkowetz, D. Meyer,
                    L. Eggert, A. Mankin
        Status:     Informational
        Date:       May 2007
        Mailbox:    henrik@levkowetz.com, 
                    dmm@1-4-5.net, 
                    lars.eggert@nokia.com,  mankin@psg.com
        Pages:      21
        Characters: 48572
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-proto-wgchair-doc-shepherding-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4858.txt

This document describes methodologies that have been designed to improve
and facilitate IETF document flow processing.  It specifies a set of
procedures under which a working group chair or secretary serves as the
primary Document Shepherd for a document that has been submitted to the
IESG for publication.  Before this, the Area Director responsible for
the working group has traditionally filled the shepherding role.  This
memo provides information for the Internet community.


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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce


_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-area