IETF Logo Mail Archive

[Ssh] Re: I-D Action: draft-ietf-sshm-cert-00.txt

Roumen Petrov <pkixssh@roumenpetrov.info> Wed, 29 April 2026 18:13 UTC

Return-Path: <pkixssh@roumenpetrov.info>
X-Original-To: ssh@mail2.ietf.org
Delivered-To: ssh@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 90C31E5E1FFD for <ssh@mail2.ietf.org>; Wed, 29 Apr 2026 11:13:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1777486399; bh=ZmF2WtqAX7I3WxMZf5NWb7zBAymA3Es/23WuXJCKWjA=; h=Date:Subject:To:References:From:In-Reply-To; b=fQWdpkrxKXR0TzX92LtEMb/kqhvwGs2olGOmgRnyFDzmXVsqGU3ZPupZu6FWMEvJE S72A8ytl1xhdjutdAhiIht8y27czsyj2hajWIE5YdgQraZL7VkyICPKnp62KPN2uss MDsgOkGlT6BUV45oh+zZq0lij0n06E9hPbjHTROE=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 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_LOW=-0.7, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=roumenpetrov.info
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3bMv79lF_8bl for <ssh@mail2.ietf.org>; Wed, 29 Apr 2026 11:13:18 -0700 (PDT)
Received: from rila.superhosting.bg (rila.superhosting.bg [91.196.125.212]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 5F739E5E1FF8 for <ssh@ietf.org>; Wed, 29 Apr 2026 11:13:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=roumenpetrov.info; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:From:References:To:Subject:MIME-Version:Date:Message-ID:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=ujuUeWBkeubQ4hUfTryzZ5jRESSe7UN7KufFlP30lZE=; b=NuO3tWWPqPZDlpzLYv5tI6aZ0H d3q7v9BXX0fPNx4AG30Gik4yLFjAt4f4kN7ZO5MCTXbiRgapcF+LTRH/ctNB+IqFFLM57EdI+z26/ uCCQDIj5LGE9Te2Id8X+W9i6MqlqcQntP1MSKdy+KDqHx9Ezyqrm857nTAzvD+v7XYJeZIaZm4j/F wfDYdHMT537na9eUSFEHM09yHsqDpsB+2b/nFhkrv1m3SEeuDufYAhiqPQWAVr1kwVAeWch4WLykN 5lD+UiicE5wPRhkGlmx8vUn2xeZdMLPQnQSUjo4LD/53+db0JOs+fHYhxsF7Q737WXlKVZSf/ttql ykBnK8Lw==;
Received: from [46.232.157.251] (port=62048 helo=[192.168.1.11]) by rila.superhosting.bg with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.99.1) (envelope-from <pkixssh@roumenpetrov.info>) id 1wI9PM-00000008wrQ-0q5N for ssh@ietf.org; Wed, 29 Apr 2026 21:13:17 +0300
Message-ID: <8f96821d-6e2b-459d-957f-41ff274ed57a@roumenpetrov.info>
Date: Wed, 29 Apr 2026 21:13:12 +0300
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: ssh@ietf.org
References: <177694026124.1167663.14342393855069278288@dt-datatracker-b45949c58-5szpr> <1777012657-sup-6689@thyestes.tartarus.org> <27119.42744.866989.598921@fireball.acr.fi> <A6C50332-FFB8-42B2-8664-94A79D7753B9@gmail.com> <27121.64808.580379.214602@fireball.acr.fi>
Content-Language: en-GB
From: Roumen Petrov <pkixssh@roumenpetrov.info>
In-Reply-To: <27121.64808.580379.214602@fireball.acr.fi>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - rila.superhosting.bg
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - roumenpetrov.info
X-Get-Message-Sender-Via: rila.superhosting.bg: authenticated_id: master78@roumenpetrov.info
X-Authenticated-Sender: rila.superhosting.bg: master78@roumenpetrov.info
X-Source:
X-Source-Args:
X-Source-Dir:
Message-ID-Hash: TWBVC7BXVMEFJVMDCSXERMAXKRYXRBHK
X-Message-ID-Hash: TWBVC7BXVMEFJVMDCSXERMAXKRYXRBHK
X-MailFrom: pkixssh@roumenpetrov.info
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Ssh] Re: I-D Action: draft-ietf-sshm-cert-00.txt
List-Id: "The SSH mail list will allow discussions on improving aspects of the Secure Shell (SSH) protocol." <ssh.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ssh/nq4Bna7qKagDNhO7XnJEuDO-_PA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ssh>
List-Help: <mailto:ssh-request@ietf.org?subject=help>
List-Owner: <mailto:ssh-owner@ietf.org>
List-Post: <mailto:ssh@ietf.org>
List-Subscribe: <mailto:ssh-join@ietf.org>
List-Unsubscribe: <mailto:ssh-leave@ietf.org>

Hello,

На 29.04.26 г. в 15:44, Tero Kivinen написа:
> Ran Atkinson writes:
>> If Tero’s approach is taken, then correct process means the OpenSSH
>> maintainers explicit prior approval is needed — because it is using
>> their namespace.
> 
> If we are just documenting what openssh has been using, and not
> changing it, then we should document it exactly so it is compatible
> with what the existing implementations, and that includes using the id
> they are using.


An entity(company/person/organisation) could publish specification.

So, I cannot understand why a design in "local/private" namespace could be promoted as standard.


> [SNIP]

Regards,
Roumen

v2.46.0 | Report a Bug | By Email | System Status