Update to the IANA SSH Protocol Parameters Registry Requirements
draft-yee-ssh-iana-requirements-03

[Ballot comment]
Thanks for this. Two minor points --

"IANA MUST only accept registry updates from the designated experts"

Presumably the IESG can also update the registry, indeed that's implicit in "Registration requests that are undetermined for a period longer than 21 days can be brought to the IESG's attention (using the  mailing list) for resolution."

I don't imagine the text is a practical problem since I don't think the IESG's role is subject to being disclaimed by an RFC in this way.

And,

  Criteria that SHOULD be applied by the designated experts includes
  determining whether the proposed registration duplicates existing
  functionality
 
Implicit, but not stated, is that duplication of existing functionality is grounds to decline allocating a code point. If that's intended, you might want to make it explicit. If it's *not* intended, that too.

[Ballot comment]
Thank you for writing this document -- it's clear and easy to read... and, better yet, short :-)

Also much thanks to Scott Rose for the DNSDIR review ( https://datatracker.ietf.org/doc/review-yee-ssh-iana-requirements-01-dnsdir-lc-rose-2022-10-13/ )

[Ballot comment]
Please consider adding a sentence somewhere listing which IANA SSH Registries were not updated ? Especially since you changed the list to be alphabetical.
Perhaps: The only IANA SSH registries not affected are "Message Numbers" and "Publickey Subsystem Status Codes", as these remain at standard track policy due to their limited resources as one byte registry values.

Please consider using the same listing order as the IANA registry or request IANA alphabetizes their listing too ?


NITS: change "wholly" to "entirely" to help non-English native speaking people.

[Ballot comment]
Hi,

Thanks for this document.  Only one comment:

Minor level comments:

(1) p 3, sec 3.  Designated Expert Pool

  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 MUST 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
    mailing list) for resolution.

I think that this would be better to be escalated to the Security ADs (sec-ads@ietf.org) rather than being directed to the whole IESG.

Regards,
Rob

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

The IANA Functions Operator has completed its review of draft-yee-ssh-iana-requirements-02. If any part of this review is inaccurate, please let us know.

The IANA Functions Operator has a question about one of the actions requested in the IANA Considerations section of this document.

The IANA Functions Operator understands that, upon approval of this document, there is a single action which we must complete.

On the Secure Shell (SSH) Protocol Parameters registry page located at:

https://www.iana.org/assignments/ssh-parameters/

a set of registries is to have their registration procedure changed from IETF Review to Expert Review (RFC8126). Where this change applies to a specific range of values within the particular parameter, that range is given in the notes column.

The following list of registries are those to be changed:

Registry Name Reference Notes
Authentication Method Names [RFC4250]
Channel Connection Failure Reason Codes and Descriptions [RFC4250] 0x00000001-0xFDFFFFFF (inclusive)
Compression Algorithm Names [RFC4250]
Connection Protocol Channel Request Names [RFC4250]
Connection Protocol Channel Types [RFC4250]
Connection Protocol Global Request Names [RFC4250]
Connection Protocol Subsystem Names [RFC4250]
Disconnection Messages Reason Codes and Descriptions [RFC4250] 0x00000001-0xFDFFFFFF (inclusive)
Encryption Algorithm Names [RFC4250]
Extended Channel Data Transfer data_type_code and Data [RFC4250] 0x00000001-0xFDFFFFFF (inclusive)
Extension Names [RFC8308]
Key Exchange Method Names [RFC4250]
MAC Algorithm Names [RFC4250]
Pseudo-Terminal Encoded Terminal Modes [RFC4250]
Public Key Algorithm Names [RFC4250]
Publickey Subsystem Attributes [RFC4819]
Publickey Subsystem Request Names [RFC4819]
Publickey Subsystem Response Names [RFC4819]
Service Names [RFC4250]
Signal Names [RFC4250]
SSH Public-Key File Header Tags [RFC4716] Excluding header-tags beginning with x-

IANA Question --> Should [ RFC-to-be ] be added to the reference to each of the updated registries to reflect this change?

The IANA Functions Operator understands that this is the only action required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is meant only to confirm the list of actions that will be performed.

For definitions of IANA review states, please see:

https://datatracker.ietf.org/help/state/draft/iana-review

Thank you,

David Dong
IANA Services Specialist

The following Last Call announcement was sent out (ends 2023-06-21):

From: The IESG
To: IETF-Announce
CC: draft-yee-ssh-iana-requirements@ietf.org, rdd@cert.org
Reply-To: last-call@ietf.org
Sender:
Subject: Last Call:  (Update to the IANA SSH Protocol Parameters Registry Requirements) to Proposed Standard


The IESG has received a request from an individual submitter to consider the
following document: - 'Update to the IANA SSH Protocol Parameters Registry
Requirements'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2023-06-21. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


  This specification updates the requirements for adding new entries to
  the IANA Secure Shell (SSH) Protocol Parameters registry.  Currently,
  the requirement is generally for "IETF Review", as defined in RFC
  8126, although a few portions of the registry require "Standards
  Action".  This specification will change that former requirement to
  "Expert Review".  This draft updates RFC 4250, RFC 4716, RFC 4819,
  RFC 8308.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-yee-ssh-iana-requirements/



No IPR declarations have been submitted directly on this I-D.

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

The IANA Functions Operator has completed its review of draft-yee-ssh-iana-requirements-01. If any part of this review is inaccurate, please let us know.

We understand that the approval of this document will require a single IANA action.

On the Secure Shell (SSH) Protocol Parameters registry page located at

https://www.iana.org/assignments/ssh-parameters/

21 registries (listed below) are to have their registration policy changed from IETF Review to Expert Review, as defined by RFC8126. If the change applies to a specific range of values in the registry (rather than the registry as a whole), this information is provided in the "Notes" column.

+===============================+===========+=======================+
| Parameter Name | RFC | Notes |
+===============================+===========+=======================+
| Authentication Method | [RFC4250] | |
| Names | | |
+-------------------------------+-----------+-----------------------+
| Channel Connection | [RFC4250] | 0x00000001-0xFDFFFFFF |
| Failure Reason Codes | | (inclusive) |
| and Descriptions | | |
+-------------------------------+-----------+-----------------------+
| Compression Algorithm | [RFC4250] | |
| Names | | |
+-------------------------------+-----------+-----------------------+
| Connection Protocol | [RFC4250] | |
| Channel Request Names | | |
+-------------------------------+-----------+-----------------------+
| Connection Protocol | [RFC4250] | |
| Channel Types | | |
+-------------------------------+-----------+-----------------------+
| Connection Protocol | [RFC4250] | |
| Global Request Names | | |
+-------------------------------+-----------+-----------------------+
| Connection Protocol | [RFC4250] | |
| Subsystem Names | | |
+-------------------------------+-----------+-----------------------+
| Disconnection Messages | [RFC4250] | 0x00000001-0xFDFFFFFF |
| Reason Codes and | | (inclusive) |
| Descriptions | | |
+-------------------------------+-----------+-----------------------+
| Encryption Algorithm | [RFC4250] | |
| Names | | |
+-------------------------------+-----------+-----------------------+
| Extended Channel Data | [RFC4250] | 0x00000001-0xFDFFFFFF |
| Transfer data_type_code | | (inclusive) |
| and Data | | |
+-------------------------------+-----------+-----------------------+
| Extension Names | [RFC8308] | |
+-------------------------------+-----------+-----------------------+
| Key Exchange Method | [RFC4250] | |
| Names | | |
+-------------------------------+-----------+-----------------------+
| MAC Algorithm Names | [RFC4250] | |
+-------------------------------+-----------+-----------------------+
| Pseudo-Terminal Encoded | [RFC4250] | |
| Terminal Modes | | |
+-------------------------------+-----------+-----------------------+
| Public Key Algorithm | [RFC4250] | |
| Names | | |
+-------------------------------+-----------+-----------------------+
| Publickey Subsystem | [RFC4819] | |
| Attributes | | |
+-------------------------------+-----------+-----------------------+
| Publickey Subsystem | [RFC4819] | |
| Request Names | | |
+-------------------------------+-----------+-----------------------+
| Publickey Subsystem | [RFC4819] | |
| Response Names | | |
+-------------------------------+-----------+-----------------------+
| Service Names | [RFC4250] | |
+-------------------------------+-----------+-----------------------+
| Signal Names | [RFC4250] | |
+-------------------------------+-----------+-----------------------+
| SSH Public-Key File | [RFC4716] | Excluding header-tags |
| Header Tags | | beginning with x- |
+-------------------------------+-----------+-----------------------+

The IANA Functions Operator understands that this is the only action required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is meant only to confirm the list of actions that will be performed.

Thank you,

Amanda Baber
IANA Operations Manager

The following Last Call announcement was sent out (ends 2022-10-28):

From: The IESG
To: IETF-Announce
CC: draft-yee-ssh-iana-requirements@ietf.org, rdd@cert.org
Reply-To: last-call@ietf.org
Sender:
Subject: Last Call:  (Update to the IANA SSH Protocol Parameters Registry Requirements) to Proposed Standard


The IESG has received a request from an individual submitter to consider the
following document: - 'Update to the IANA SSH Protocol Parameters Registry
Requirements'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2022-10-28. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


  This specification updates the requirements for adding new entries to
  the IANA Secure Shell (SSH) Protocol Parameters registry.  Currently,
  the requirement is generally for "IETF Review", as defined in RFC
  8126, although a few portions of the registry require "Standards
  Action".  This specification will change that former requirement to
  "Expert Review".  This draft updates RFC 4250, RFC 4716, RFC 4819,
  RFC 8308.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-yee-ssh-iana-requirements/



No IPR declarations have been submitted directly on this I-D.