Re: [Curdle] Time to Review IANA SSH Registries Policies?

Ron Frederick <ronf@timeheart.net> Wed, 03 February 2021 20:01 UTC

Return-Path: <ronf@timeheart.net>
X-Original-To: curdle@ietfa.amsl.com
Delivered-To: curdle@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8D4A3A135A for <curdle@ietfa.amsl.com>; Wed, 3 Feb 2021 12:01:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=timeheart.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dwohnz_kSp4c for <curdle@ietfa.amsl.com>; Wed, 3 Feb 2021 12:01:41 -0800 (PST)
Received: from mail-pl1-x62c.google.com (mail-pl1-x62c.google.com [IPv6:2607:f8b0:4864:20::62c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D31B13A123C for <curdle@ietf.org>; Wed, 3 Feb 2021 12:01:17 -0800 (PST)
Received: by mail-pl1-x62c.google.com with SMTP id b17so461927plz.6 for <curdle@ietf.org>; Wed, 03 Feb 2021 12:01:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=timeheart.net; s=mail; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=PLVAXz5EoHFERJeVpX1jjmHFDroZZ5Y/wfmD8Prcnyo=; b=OlXzSVo2Tb41PMmo5KUzAQX8wyxVnH9PF4XRb+UEBUojWFh6n17Wj82kEnpj/IgB3S qGcJ0ymjs+uO5ACZ+/IrTXvyNFI+C2ON19EA36YXMHKvmhpteYxxFs2JEBRRLkJylQBV kOfBa1q2S1SVCNlZZHGt32sDLOM5X5BTM+QHQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=PLVAXz5EoHFERJeVpX1jjmHFDroZZ5Y/wfmD8Prcnyo=; b=EnMpgAqlGtymcuM1bUjDggx/5p+oCUh92tYbbvtgibQNVs8rcOKPM3K/ebzuyyHdSF bPg8v6b7RqI2e2UwrUytj12HK89faOy67nQgIobqL2orWR3jMU5zzWV5URJHjRVNrDIg jHo3XdTa13nfDx3ipIWNgofaon3Y/sFDv8JY/FurOkRIuo9n02X/9kahNj6Qdq4Tqjkv E/zi3uQt61M03mICmidfbO7VVkiVhec/KBac6xt3zfDLLHIaKH0FjHv/nWC1bJqrEWDK W9wT75j1TASkdVPRHPZOcAExwLur5FK9w9sa1zNGXENFJEa9Tun0b70VcXaqBKJV6ko8 0c5g==
X-Gm-Message-State: AOAM533qDdm4i4NNUZOLuTmO16FrT4JiHewOqrJmMLcWgxD+PyaiRyLU E0hkEk+dJokyej3c4YAFcaeRgpzJuIvtyjfx
X-Google-Smtp-Source: ABdhPJwMPTCRbFnZ3mxSRhVNRFDwVKIJGQcIH7xqAvO3T2JYnB1KalO7LYG/zlB8u0tOz5GcCt/+pg==
X-Received: by 2002:a17:902:d510:b029:e1:1040:3726 with SMTP id b16-20020a170902d510b02900e110403726mr4555429plg.59.1612382476992; Wed, 03 Feb 2021 12:01:16 -0800 (PST)
Received: from d25qp0mlgq17.wifi.broadcom.net ([192.19.8.250]) by smtp.gmail.com with ESMTPSA id e76sm1799214pfh.102.2021.02.03.12.01.15 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Feb 2021 12:01:16 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Ron Frederick <ronf@timeheart.net>
In-Reply-To: <02E82091-15F9-4C36-96AD-1F88CC2E5594@akamai.com>
Date: Wed, 3 Feb 2021 12:01:15 -0800
Cc: Sean Turner <sean@sn3rd.com>, Curdle List <curdle@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <367596AB-B583-4105-9099-9055A5E5526F@timeheart.net>
References: <A77E7858-C4ED-4DA0-8015-5E67EB921144@sn3rd.com> <02E82091-15F9-4C36-96AD-1F88CC2E5594@akamai.com>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/G3Z87TQiaJzjDv8-QF_YEMW--a8>
Subject: Re: [Curdle] Time to Review IANA SSH Registries Policies?
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2021 20:01:49 -0000

I’m not currently familiar with the “expert review” process that’s in place for these other registries right now, but (also speaking as an individual) I’d be interested in learning more and would potentially be interested in participating in such a review depending on the time commitment involved.

On Feb 3, 2021, at 11:54 AM, Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> wrote:
> Speaking as an individual,
> 
>> Is there interest in reviewing the SSH registries to see if it makes sense to move them to expert review (or some other level)?
> 
> I support this and would contribute to the review.  (I'm author of a draft which is currently in the WG adoption phase; https://datatracker.ietf.org/doc/draft-rsalz-update-registries/
> 
> 
> _______________________________________________
> Curdle mailing list
> Curdle@ietf.org
> https://www.ietf.org/mailman/listinfo/curdle

-- 
Ron Frederick
ronf@timeheart.net