<?xml version="1.0" encoding="utf-8"?>
<!-- name="GENERATOR" content="github.com/mmarkdown/mmark Mmark Markdown Processor - mmark.miek.nl" -->
<rfc version="3" ipr="trust200902" docName="draft-levine-iduse-00" submissionType="IETF" category="bcp" xml:lang="en" xmlns:xi="http://www.w3.org/2001/XInclude" updates="2026" indexInclude="true" consensus="true">

<front>
<title abbrev="I-D update">Update to the use of Internet-Drafts in the Internet Standards Process</title><seriesInfo value="draft-levine-iduse-00" stream="IETF" status="bcp" name="Internet-Draft"></seriesInfo>
<author initials="J." surname="Levine" fullname="John Levine"><organization>Standcore LLC</organization><address><postal><street></street>
</postal><email>standards@standcore.com</email>
</address></author><date/>
<area>General</area>
<workgroup></workgroup>
<keyword>internet-draft</keyword>

<abstract>
<t>This memo updates the way that Internet-Drafts are used in the Internet Standards Process.</t>
<t>Rather than expiring, Internet-Drafts are marked active or inactive.
Also, the rules for referencing Internet-Drafts in other documents are clarified.</t>
</abstract>

</front>

<middle>

<section anchor="introduction"><name>Introduction</name>
<t><xref target="RFC2026" sectionFormat="of" relative="#" section="2"></xref> describes the way that Internet-Drafts are used in the standards process.
It says that after six months, an I-D &quot;is simply removed from the Internet-Drafts directory.&quot;
It also says in a highlighted box &quot;Under no circumstances should an Internet-Draft
be referenced by any paper, report, or Request-for-Proposal.&quot;
In practice, neither of those have turned out to be true.</t>
<t>This memo creates an Active flag to indicate whether an I-D is currently active.
It also updates the advice about referencing I-Ds to reflect existing practice.</t>
<t>[[ please remove this section before publication ]]</t>
<t>This memo does not use RFC2119 keywords because it's not about technical interoperation.</t>
<t>The no-draft-expiry@ietf.org mailing list would be a good place to argue about this draft.</t>
</section>

<section anchor="active"><name>Active and Inactive Drafts</name>
<t>Drafts will no longer expire, and instead are marked active or inactive to indicate
whether the authors are still likely to be working on them.</t>

<section anchor="how-drafts-expire-now"><name>How Drafts Expire Now</name>
<t>When the xmlrfc version of an I-D is rendered into text, HTML, or PDF, the headings in
the rendered version include an an &quot;Expired:&quot; line with a date six months after the date
that the I-D was rendered.  The &quot;Status of This Memo&quot; boilerplate states that the draft
is valid for a maximum of six months, and &quot;It is inappropriate to use Internet-Drafts as reference
material or other than 'work in progress'&quot;.</t>
<t>Currently, Internet-Drafts are stored in the IETF's Datatracker indefinitely.  If more than
six months have passed since the I-D was submitted and the I-D has not been superseded,
the Datatracker shows an orange warning
box saying &quot;This Internet-Draft is no longer active&quot; but still contains the same links to
display the I-D.
The rsync server at rsync.ietf.org contains one collection
&quot;internet-drafts&quot; with currently active I-Ds, i.e., ones that are less than six months
old and have not been superseded, and another collection &quot;id-archive&quot; which contains drafts as far back
as 1992.</t>
<t>Once an I-D has expired, the only way to get it out of expired status is
to submit a new version of the I-D, which may be identical other than the version number.</t>
</section>

<section anchor="making-drafts-active-or-inactive"><name>Making Drafts Active or Inactive</name>
<t>Internet-Drafts will no longer have an expiration date.
When a draft is submitted, it is marked Active in the Datatracker.
After six months, if the I-D has not been superseded, it normally changes to Inactive.
At any time, any of the I-D's authors can log into the Datatracker and mark the draft as Active.
If it is Inactive. it becomes Active again.
The timer is reset and the draft will remain Active for six months from each time it is marked
Active.
There is no limit to how many times a draft can be marked Active.</t>
<t>The Active flag exists only in the Datatracker; it is not placed in the draft itself since there
would be no way to change the Active flag in a draft once it has been published and downloaded.</t>
</section>
</section>

<section anchor="idref"><name>Referencing an Internet-Draft</name>
<t>In some cases it is acceptable to use an Internet-Draft as a reference in another document.</t>
<t>Internet-Drafts can reference other I-Ds without limit.
RFCs can use Internet-Drafts as informative references but not as normative ones.</t>
</section>

<section anchor="boilerfix"><name>Changes to the boilerplate text</name>
<t>The &quot;Status of This Memo&quot; boilerplate inserted into rendered versions of Internet-Drafts will
be changed to reflect the changes in <xref target="active"></xref> and <xref target="idref"></xref>.
The new text is:</t>
<t>TBD</t>
</section>

<section anchor="security"><name>Security considerations</name>
<t>This memo only changes some details of the Internet Standards editorial process and should have no
effect on the security of the Internet.</t>
</section>

</middle>

<back>
<references><name>Informative References</name>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2026.xml"/>
</references>

</back>

</rfc>
