Re: Protocol Action: 'Update to the IANA SSH Protocol Parameters Registry Requirements' to Proposed Standard (draft-yee-ssh-iana-requirements-03.txt)

S Moonesamy <sm+ietf@elandsys.com> Thu, 18 April 2024 11:26 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6FCAC15155F for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2024 04:26:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.085
X-Spam-Level:
X-Spam-Status: No, score=-2.085 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=elandsys.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k2_e2avmQMUf for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2024 04:26:53 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 15EACC151536 for <ietf@ietf.org>; Thu, 18 Apr 2024 04:26:53 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.183.218]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 43IBIFvw005240 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Apr 2024 04:18:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1713439130; x=1713525530; i=@elandsys.com; bh=ehqz9giMHMiaGa6F0frPG091IPicd6g6Nzxp7uZ/nWU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=sHnXPTdcdaGb7FSSISXIMnOmUPEiyQ89Oq7gfj5EJ6IY4R/n3WBSrM1TteG0rSvFE +IorFKldML646SsSHIjfN8z+QcK5QuTvwSXX0eKiPBh4fwWPRcZ8MnyCbjxopdIQ/D 2LAet10i+gornFgLM5WgtaMZIXLCKK5FzUL1K7mc=
Message-Id: <6.2.5.6.2.20240418024551.09395c58@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 18 Apr 2024 03:57:43 -0700
To: Roman Danyliw <rdd@cert.org>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Protocol Action: 'Update to the IANA SSH Protocol Parameters Registry Requirements' to Proposed Standard (draft-yee-ssh-iana-requirements-03.txt)
Cc: ietf@ietf.org
In-Reply-To: <169444715971.48679.10138657823541117013@ietfa.amsl.com>
References: <169444715971.48679.10138657823541117013@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yP8R4tF9wG7iUXNrS6uJ88A_bTE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Apr 2024 11:26:57 -0000

Hi Roman,

[Cc to ietf@ietf.org]

At 08:45 AM 11-09-2023, The IESG wrote:
>The IESG has approved the following document:
>- 'Update to the IANA SSH Protocol Parameters Registry Requirements'
>   (draft-yee-ssh-iana-requirements-03.txt) as Proposed Standard
>
>This document has been reviewed in the IETF but is not the product of an IETF
>Working Group.
>
>The IESG contact person is Roman Danyliw.

The text which is quoted above is an extract of the email [1] which 
was sent on 11 September 2023.  If I am not mistaken, you are the 
appropriate contact person for the process which ended up with the 
publication of a Proposed Standard (RFC 9519).

Section 3 of the Proposed Standard specification stated that there 
will be a mailing list (ssh-reg-review@ietf.org) for registry 
requests.  A search for the mailing list did not return any positive 
result.  I found that odd.  It is usually not that difficult to 
create a mailing list.  Furthermore, there shouldn't be any 
significant procedural issue as it is stated in the Proposed Standard 
that "It represents the consensus of the IETF community."

Would it be possible for you to look into the oddity?

Regards,
S. Moonesamy

1. 
https://mailarchive.ietf.org/arch/msg/ietf-announce/1-m11RaD_aITtJ-LJLhUYDLNHDc/