<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>

<rfc  xmlns:xi="http://www.w3.org/2001/XInclude"
      submissionType="IETF"
      category="std"
      consensus="true"
      docName="draft-yee-ssh-iana-requirements-03"
      number="9519"
      ipr="trust200902"
      obsoletes=""
      updates="4250, 4716, 4819, 8308"
      xml:lang="en"
      tocInclude="true"
      tocDepth="4"
      symRefs="true"
      sortRefs="true"
      version="3">

 <front>
   <title abbrev="IANA SSH Registry Requirements">Update to the IANA SSH Protocol Parameters Registry Requirements</title>
   <seriesInfo name="RFC" value="9519"/>

   <author fullname="Peter E. Yee" initials="P." surname="Yee">
      <organization>AKAYLA</organization>
      <address>
        <postal>
          <street/>

         <city>Mountain View</city>
          <region>CA</region>
          <code>94043</code>
          <country>United States of America</country>
        </postal>
        <phone/>
        <email>peter@akayla.com</email>
     </address>
    </author>
    <date year="2024" month="January"/>


   <area>sec</area>

   <keyword>ssh</keyword>
   <keyword>iana</keyword>
   <keyword>registry</keyword>
   
   <abstract>
<t>
   This specification updates the registration policies for adding new entries to
   registries within the IANA "Secure Shell (SSH) Protocol Parameters" group of registries.  Previously, the registration policy was generally IETF Review, as defined in RFC
   8126, although a few registries require Standards Action. This specification changes it from IETF Review to Expert Review. This document updates RFCs 4250, 4716, 4819, and 8308.</t>
    </abstract>
  </front>
  <middle>
    <section numbered="true" toc="default">
      <name>Introduction</name>
      <t>The IANA "Secure Shell (SSH) Protocol Parameters" registry was populated by several RFCs including <xref target="RFC4250" format="default"/>, <xref target="RFC4716" format="default"/>, <xref target="RFC4819" format="default"/>, and <xref target="RFC8308" format="default"/>. Outside of some narrow value ranges that require Standards Action in order to add new values or that are marked for Private Use, the registration policy for other portions of the registry was IETF Review <xref target="RFC8126" format="default"/>. This specification changes the policy from IETF Review to Expert Review. This change is in line with similar changes undertaken for certain IPsec and TLS registries.
      </t>
      <section numbered="true" toc="default">
        <name>Requirements Language</name>
        <t>
    The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
    "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>",
    "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>",
    "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
    "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be
    interpreted as described in BCP&nbsp;14 <xref target="RFC2119"/> <xref
    target="RFC8174"/> when, and only when, they appear in all capitals, as
    shown here.
        </t>
      </section>
    </section>

    <section numbered="true" toc="default">
      <name>SSH Protocol Parameters Affected</name>
      <t>The following table lists the "Secure Shell (SSH) Protocol Parameters" registries whose registration policy has changed from IETF Review to Expert Review. Where this change applied to a specific range of values within the particular parameter, that range is given in the notes column.  Affected registries now list this document as a reference.</t>

      <table anchor="ssh_protocol_parameters_table" align="center">
        <name>Secure Shell (SSH) Protocol Parameters Affected</name>
        <thead>
          <tr>
            <th align="center">Parameter Name</th>
            <th align="center">RFC</th>
            <th align="center">Notes</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="center">Authentication Method Names</td>
            <td align="center"><xref target="RFC4250" format="default"/></td>
            <td align="center"/>
          </tr>
          <tr>
            <td align="center">Channel Connection Failure Reason Codes and Descriptions</td>
            <td align="center"><xref target="RFC4250" format="default"/></td>
            <td align="center">0x00000001-0xFDFFFFFF (inclusive)</td>
          </tr>
          <tr>
            <td align="center">Compression Algorithm Names</td>
            <td align="center"><xref target="RFC4250" format="default"/></td>
            <td align="center"/>
          </tr>
          <tr>
            <td align="center">Connection Protocol Channel Request Names</td>
            <td align="center"><xref target="RFC4250" format="default"/></td>
            <td align="center"/>
          </tr>
          <tr>
            <td align="center">Connection Protocol Channel Types</td>
            <td align="center"><xref target="RFC4250" format="default"/></td>
            <td align="center"/>
          </tr>
          <tr>
            <td align="center">Connection Protocol Global Request Names</td>
            <td align="center"><xref target="RFC4250" format="default"/></td>
            <td align="center"/>
          </tr>
          <tr>
            <td align="center">Connection Protocol Subsystem Names</td>
            <td align="center"><xref target="RFC4250" format="default"/></td>
            <td align="center"/>
          </tr>
          <tr>
            <td align="center">Disconnection Messages Reason Codes and Descriptions</td>
            <td align="center"><xref target="RFC4250" format="default"/></td>
            <td align="center">0x00000001-0xFDFFFFFF (inclusive)</td>
          </tr>
          <tr>
            <td align="center">Encryption Algorithm Names</td>
            <td align="center"><xref target="RFC4250" format="default"/></td>
            <td align="center"/>
          </tr>
          <tr>
            <td align="center">Extended Channel Data Transfer data_type_code and Data</td>
            <td align="center"><xref target="RFC4250" format="default"/></td>
            <td align="center">0x00000001-0xFDFFFFFF (inclusive)</td>
          </tr>
          <tr>
            <td align="center">Extension Names</td>
            <td align="center"><xref target="RFC8308" format="default"/></td>
            <td align="center"/>
          </tr>
          <tr>
            <td align="center">Key Exchange Method Names</td>
            <td align="center"><xref target="RFC4250" format="default"/></td>
            <td align="center"/>
          </tr>
          <tr>
            <td align="center">MAC Algorithm Names</td>
            <td align="center"><xref target="RFC4250" format="default"/></td>
            <td align="center"/>
          </tr>
          <tr>
            <td align="center">Pseudo-Terminal Encoded Terminal Modes</td>
            <td align="center"><xref target="RFC4250" format="default"/></td>
            <td align="center"/>
          </tr>
          <tr>
            <td align="center">Public Key Algorithm Names</td>
            <td align="center"><xref target="RFC4250" format="default"/></td>
            <td align="center"/>
          </tr>
          <tr>
            <td align="center">Publickey Subsystem Attributes</td>
            <td align="center"><xref target="RFC4819" format="default"/></td>
            <td align="center"/>
          </tr>
          <tr>
            <td align="center">Publickey Subsystem Request Names</td>
            <td align="center"><xref target="RFC4819" format="default"/></td>
            <td align="center"/>
          </tr>
          <tr>
            <td align="center">Publickey Subsystem Response Names</td>
            <td align="center"><xref target="RFC4819" format="default"/></td>
            <td align="center"/>
          </tr>
          <tr>
            <td align="center">Service Names</td>
            <td align="center"><xref target="RFC4250" format="default"/></td>
            <td align="center"/>
          </tr>
          <tr>
            <td align="center">Signal Names</td>
            <td align="center"><xref target="RFC4250" format="default"/></td>
            <td align="center"/>
          </tr>
          <tr>
            <td align="center">SSH Public-Key File Header Tags</td>
            <td align="center"><xref target="RFC4716" format="default"/></td>
            <td align="center">Excluding header-tags beginning with x-</td>
          </tr>
        </tbody>
      </table>
      <t>The only IANA SSH protocol parameter registries not affected are
      "Message Numbers" and "Publickey Subsystem Status Codes", as these
      remain Standards Action due to their limited resources as
      one-byte registry values.</t>
    </section>

    <section numbered="true" toc="default">
      <name>Designated Expert Pool</name>
      <t>Expert Review <xref target="RFC8126" format="default"/> registry requests
       are registered after a three-week review period on the
       &lt;ssh-reg-review@ietf.org&gt; mailing list, and on the advice of one or more
       designated experts. However, to allow for the allocation of values prior to
       publication, the designated experts may approve registration once they are
       satisfied that such a specification will be published.</t>

       <t>Registration requests sent to the mailing list for review <bcp14>SHOULD</bcp14> use
       an appropriate subject (e.g., "Request to register value in SSH protocol
       parameters &lt;specific parameter&gt; registry").</t>

       <t>Within the review period, the designated experts will either approve
       or deny the registration request, communicating this decision to the
       review list and IANA.  Denials <bcp14>MUST</bcp14> include an explanation and, if
       applicable, suggestions as to how to make the request successful.
       Registration requests that are undetermined for a period longer than
       21 days can be brought to the IESG's attention (using the
       &lt;iesg@ietf.org&gt; mailing list) for resolution.</t>

       <t>Criteria that <bcp14>SHOULD</bcp14> be applied by the designated experts includes
       determining whether the proposed registration duplicates existing
       functionality (which is not permitted), whether it is likely to be of
       general applicability or useful only for a single application, and
       whether the registration description is clear.</t>

       <t>IANA <bcp14>MUST</bcp14> only accept registry updates from the designated experts
       and the IESG. It <bcp14>SHOULD</bcp14> direct all requests for registration from other sources to the review mailing list.</t>

       <t>It is suggested that multiple designated experts be appointed who are
       able to represent the perspectives of different applications using
       this specification, in order to enable broadly informed review of
       registration decisions.  In cases where a registration decision could
       be perceived as creating a conflict of interest for a particular
       expert, that expert <bcp14>SHOULD</bcp14> defer to the judgment of the other
       experts.</t>
    </section>


   <section anchor="IANA" numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>This memo is entirely about updating the IANA "Secure Shell (SSH) Protocol Parameters" registry.</t>
    </section>
    <section anchor="Security" numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>This memo does not change the Security Considerations for any of the updated RFCs.</t>
    </section>
  </middle>

 <back>

   <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4250.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4819.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8308.xml"/>

      </references>
      <references>
        <name>Informative References</name>

<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4716.xml"/>

        <reference anchor="CURDLE-MA" target="https://mailarchive.ietf.org/arch/msg/curdle/gdiOlZr9bnrZv8umVyguGG3woIM/">
          <front>
            <title>Subject: [Curdle] Time to Review IANA SSH Registries Policies?</title>
            <author initials="S." surname="Turner" fullname="Sean Turner">
              <organization/>
            </author>
            <date year="2021" month="February"/>
          </front>
<refcontent>message to the Curdle mailing list</refcontent>
        </reference>
      </references>
    </references>

    <section anchor="Acknowledgements" numbered="false" toc="default">
      <name>Acknowledgements</name>
      <t>The impetus for this specification was a February 2021 discussion on the CURDLE mailing list <xref target="CURDLE-MA" format="default"/>.</t>
    </section>
 </back>
</rfc>
