<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.baber-ianabis-rfc7120bis" target="https://datatracker.ietf.org/doc/html/draft-baber-ianabis-rfc7120bis-01">
   <front>
      <title>Early IANA Code Point Allocation for IETF Stream Internet-Drafts</title>
      <author initials="A." surname="Baber" fullname="Amanda Baber">
         <organization>Internet Assigned Numbers Authority</organization>
      </author>
      <author initials="S." surname="Tanamal" fullname="Sabrina Tanamal">
         <organization>Internet Assigned Numbers Authority</organization>
      </author>
      <date month="September" day="19" year="2025" />
      <abstract>
	 <t>   This memo describes the requirements for securing IANA code point
   assignments before RFC publication.  In particular, it describes the
   &quot;early allocation&quot; process that allows for temporary but renewable
   allocations from registries that would ordinarily require an IESG-
   approved Internet-Draft: primarily, registries maintained in
   accordance with the &quot;Standards Action,&quot; &quot;IETF Review,&quot; &quot;RFC
   Required,&quot; and, in some cases, &quot;Specification Required&quot; policies
   described in RFC 8126.  This process can be used when code point
   allocation is needed to facilitate desired or required implementation
   and deployment experience prior to publication.  The procedures in
   this document are intended to apply only to IETF Stream documents.

   This document obsoletes RFC 7120.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-baber-ianabis-rfc7120bis-01" />
   
</reference>
