<?xml version="1.0" encoding="utf-8"?>
<?xml-model href="rfc7991bis.rnc"?>  <!-- Required for schema
      validation and schema-aware editing --> 
<!-- <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> --> 
<!-- This third-party XSLT can be enabled for direct transformations
in XML processors, including most browsers --> 

<!DOCTYPE rfc [
  <!ENTITY filename "draft-eastlake-test-rfc-numbers-00">
  <!ENTITY nbsp   "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<!-- If further character entities are required then they should be
added to the DOCTYPE above. Use of an external entity file is not
recommended. --> 
<?rfc strict="yes" ?>
<?rfc toc="yes"?>

<rfc
  xmlns:xi="http://www.w3.org/2001/XInclude"
  category="bcp"
  docName="&filename;"
  ipr="trust200902"
  obsoletes=""
  updates=""
  submissionType="IETF"
  xml:lang="en"
  version="3">
<!-- 
    * docName should be the name of your draft * category should be
    one of std, bcp, info, exp, historic * ipr should be one of
    trust200902, noModificationTrust200902, noDerivativesTrust200902,
    pre5378Trust200902 * updates can be an RFC number as NNNN *
    obsoletes can be an RFC number as NNNN
-->


<!-- ____________________FRONT_MATTER____________________ -->
<front>
   <title abbrev="Test RFC Numbers">RFC Numbers for Testing and
   Example Use</title>
   <!--  The abbreviated title is required if the full title is
        longer than 39 characters --> 

   <seriesInfo name="Internet-Draft"
               value="&filename;"/>

   <author fullname="Donald E. Eastlake 3rd" initials="D."
           surname="Eastlake">
     <organization>Futurewei Technologies</organization>
     <address>
       <postal>
         <street>2386 Panoramic Circle</street>
         <city>Apopka</city>
         <region>Florida</region>
         <code>32703</code>
         <country>USA</country>
       </postal>        
       <phone>+1-508-333-2270</phone>
       <email>d3e3e3@gmail.com</email>
     </address>
   </author>
   
   <date year="2023" month="8" day="7"/>

   <area>General</area>
   <workgroup>Network Working Group</workgroup>
   <!-- "Internet Engineering Task Force" is fine for individual
        submissions.  If this element is not present, the default is
        "Network Working Group", which is used by the RFC Editor as a
        nod to the history of the RFC Series. --> 

   <keyword/>
   <!-- Multiple keywords are allowed.  Keywords are incorporated
        into HTML output files for use by search engines. --> 

<abstract>
   <t>This document specifies several RFC numbers of various lengths
   for which RFCs have never been and should never be issued. These
   RFC numbers may be useful in testing of or use as example in
   documentation and referencing systems.</t>
</abstract>
 
</front>


<!-- ____________________MIDDLE_MATTER____________________ -->
<middle>
    
<section>  <!-- 1. -->
  <name>Introduction</name>

 <t>The RFC Series (ISSN 2070-1721, <xref target="RFCeditor"/>)
 contains technical and organizational documents about the Internet,
 including the specifications and policy documents produced by several
 streams, currently the following five: the Internet Engineering Task
 Force (IETF), the Internet Research Task Force (IRTF), the Internet
 Architecture Board (IAB), Independent Submissions, and Editorial. It
 was begun before the IETF was formed. Each RFC is assigned a unique
 number and these number are not reused. (An RFC is replaced by
 issuing a new RFC with a new number that obsoletes the RFC being
 replaced.)</t>
  
 <t>RFC numbers are widely used in IETF doocumentation and are
 frequently referred to or displayed. Current systems are adapted
 for RFC numbers up to four digits ("9999") but RFC numbers will soon
 overflow to 5 digits. A five-digit example number that can be used
 for testing such systems and for use in documentation if needed.</t>

 <t>Test / example RFC numbers of shorter lengths may also be useful
 and, conveniently enough, there exist 2-, 3-, and 4- digit RFC
 numbers that have never been issued and, under current policies,
 never will be issued. Note that a system tested only with the
 currently common 4-digit RFC numbers might have difficulty with
 shorter as well as long RFC numbers. For example, in any such system,
 there are questions of whether to pad with leading zeros to some
 fixed length or the like.</t>
 
 <t>These considerations have some overlap with those noted in <xref
 target="RFC2606"/> and <xref target="RFC5737"/>, which point out that
 the use of designated code values reserved for documentation and
 examples reduces the likelihood of conflicts and confusion arising
 from such code points conflicting with code points assigned for some
 actual use.</t>

 <t>The idea of reserved RFC numbers for these purposes was suggested
 by Brian E. Carpenter.</t>

</section>

<section> <!-- 2. -->
  <name>The Reserved RFC Numbers</name>

 <t>The reserved RFC numbers that are available for use in testing and
 experimentation with systems that process or use RFC numbers are
 show below. These numbers were chosen as the smallest unused number
 of each length that had not been issued and which, to minimize the
 likelihood of errors, did not include any zeros or multiple
 occurrences of the same digit.</t>

 <table align="center">
   <thead>
     <tr><th align ="right">Length</th><th align="right">RFC Number</th></tr>
   </thead>
   <tbody>
     <tr><td align ="right">1</td><td align="right">none available</td></tr>
     <tr><td align ="right">2</td><td align ="right">14</td></tr>
     <tr><td align ="right">3</td><td align ="right">159</td></tr>
     <tr><td align ="right">4</td><td align ="right">1839</td></tr>
     <tr><td align ="right">5</td><td align ="right">12345</td></tr>
   </tbody>
 </table>

</section>
 
<section>  <!-- 3. -->
  <name>IANA Considerations</name>

  <t>This document requires no IANA actions.</t>
  
</section>

<section>  <!-- 8. -->
  <name>Security Considerations</name>

 <t>TBD</t>

</section>

</middle>

<!-- ____________________BACK_MATTER____________________ -->
<back>

<references>
  <name>Normative References</name>
        
<xi:include
    href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.2119.xml"/>
<xi:include
    href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.8174.xml"/>
       
</references>
 
<references>
  <name>Informative References</name>

  <reference anchor="RFCeditor"
	     target="https://www.rfc-editor.org">
    <front>
      <title>RFC Editor</title>
      <author>
	<organization>RFC Editor</organization>
      </author>
    </front>
  </reference>
  
<xi:include
    href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.2606.xml"/>
<xi:include
    href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.5737.xml"/>

</references>

<section anchor="Acknowledgements" numbered="false">
  <name>Acknowledgements</name>

 <t>The idea behind this document was originated by Brian Carpenter.</t>
  
 <t>The suggestions and comments of the following persons are
 gratefully acknowledged: TBD.</t>

</section>

</back>

</rfc>
