<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.carpenter-rfced-model" target="https://datatracker.ietf.org/doc/html/draft-carpenter-rfced-model-00">
   <front>
      <title>Alternative Proposed Model for RFC Editing and Publication</title>
      <author initials="B. E." surname="Carpenter" fullname="Brian E. Carpenter">
         <organization>The University of Auckland</organization>
      </author>
      <date month="August" day="20" year="2020" />
      <abstract>
	 <t>   The finishing process for a document that is approved for publication
   as an RFC currently involves a somewhat detailed and lengthy process.
   The system that executes that process involves a number of different
   actors, each bringing competency with different aspects of the
   overall process.  Ensuring that this process functions smoothly is
   critical to the mission of the organizations that publish documents
   in the RFC series.

   This document proposes a framework for that system that aims to
   provide clear delineations of accountability and responsibility for
   each of the actors in this system.  It would require significant
   updates to RFC 8728 and RFC 8729, and minor updates to RFC 2850 and
   RFC 7841.

   Discussion of this document takes place on the RFC Editor Futures
   mailing list (rfced-future@iab.org).

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-carpenter-rfced-model-00" />
   
</reference>
