Re: [saag] SSH & Ntruprime
S Moonesamy <sm+ietf@elandsys.com> Sat, 30 March 2024 04:33 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 39C2DC14F61C for <ietf@ietfa.amsl.com>; Fri, 29 Mar 2024 21:33:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.696
X-Spam-Level:
X-Spam-Status: No, score=-6.696 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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=fail (1024-bit key) reason="fail (message has been altered)" 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 gv4rAB6zskGC for <ietf@ietfa.amsl.com>; Fri, 29 Mar 2024 21:33:42 -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 44069C14F5ED for <ietf@ietf.org>; Fri, 29 Mar 2024 21:33:42 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.69.153]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 42U4Wew3016341 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Mar 2024 21:33:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1711773218; x=1711859618; i=@elandsys.com; bh=51MrAPv+M3R4XSqEWzBeWQDtCTrgNn5Z4NyGc25s2ZA=; h=Date:To:From:Subject:In-Reply-To:References; b=bvaGzLHscRctBpC3+2VnAQV2DuXBIAjKtw9f/fDSfskApuEotMFUJrsmM1obljgnH 1ao2/QdeBS395M/9B6Ju+Sz9XR8Jlj6svgUlJz5dAo1vail5iinyrYQSgmjdGZoSEq 963AJwJA14wjbHodY//4iiEp+sJMsbCT7FqSGmo8=
Message-Id: <6.2.5.6.2.20240329200425.0aa09938@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 29 Mar 2024 21:24:23 -0700
To: John C Klensin <john@jck.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [saag] SSH & Ntruprime
In-Reply-To: <A2C21DCBDCAB094E144891A7@PSB>
References: <ACA03432-1AE4-4ACB-B469-64AAF6F3FB52@iana.org> <A2C21DCBDCAB094E144891A7@PSB>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8NPrtGEcxhuLPljzxS4mYkN2-zg>
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: Sat, 30 Mar 2024 04:33:46 -0000
Hi John, At 03:28 PM 28-03-2024, John C Klensin wrote: >And that "encouragement" is another task I had in mind for this >group, directed to specs setting up new registries, i.e., having >some team in the IETF specifically tasked for reviewing such >guidance, including commenting when it is not present and >strengthening the encouragement rather than having many or most >area-designated reviewers glaze over when they reach the details >of IANA Considerations section. I used to review the "IANA Considerations" section going through Last Call. I have not done that in a while as there are other people to do that work. I also went through the fuddle of a registration some time ago. I saw people encountering some hurdle during the registration of a code point. I commented a few times or less as there is usually an expert to see to those things. I have not come across any major issue over the recent years which might be attributed to a PTI, formerly IANA, shortcoming. There are several layers of review before the I-D proposing a new registry or a change in registration policy reaches the IESG. It's a bit difficult to push back against a policy which is too restrictive when the WG has already made its mind on that. I am currently not convinced on having a new group tasked to review the guidance in the IANA Considerations section. In my opinion, it would be a lot of effort to keep that group (of volunteers) working. There is some text in BCP 26 about security vulnerabilities. The guidance is to have a note in the relevant registration so that the public is not misled into using that code point. I have not seen that being done. Regards, S. Moonesamy
- Re: [saag] SSH & Ntruprime Amanda Baber
- Re: [saag] SSH & Ntruprime Salz, Rich
- Re: [saag] SSH & Ntruprime Randy Presuhn
- Re: [saag] SSH & Ntruprime John C Klensin
- Re: [saag] SSH & Ntruprime S Moonesamy
- Re: [saag] SSH & Ntruprime Randy Presuhn
- Re: [saag] SSH & Ntruprime S Moonesamy
- Re: [saag] SSH & Ntruprime Randy Presuhn
- Re: [saag] SSH & Ntruprime John C Klensin
- Re: [saag] SSH & Ntruprime Carsten Bormann
- Re: [saag] SSH & Ntruprime S Moonesamy
- Re: [saag] SSH & Ntruprime Michael StJohns
- Re: [saag] SSH & Ntruprime John C Klensin
- Re: [saag] SSH & Ntruprime David Schinazi
- Re: [saag] SSH & Ntruprime Michael StJohns
- Re: [saag] SSH & Ntruprime S Moonesamy
- Re: [saag] SSH & Ntruprime S Moonesamy
- Re: [saag] SSH & Ntruprime Randy Presuhn
- Re: [saag] SSH & Ntruprime John C Klensin
- Re: [saag] SSH & Ntruprime S Moonesamy
- Re: [saag] SSH & Ntruprime John C Klensin
- Re: [saag] SSH & Ntruprime John Scudder
- Re: [saag] SSH & Ntruprime Eliot Lear
- Re: [saag] SSH & Ntruprime John Scudder
- Re: [saag] SSH & Ntruprime Keith Moore
- Registration of code points. Re: [saag] SSH & Ntr… Phillip Hallam-Baker