Re: [netconf] [Last-Call] Yangdoctors last call review of draft-ietf-netconf-ssh-client-server-24

Kent Watsen <kent+ietf@watsen.net> Wed, 02 June 2021 14:34 UTC

Return-Path: <01000179cd25b935-41381155-4d11-4e36-a6ec-b71b55fde875-000000@amazonses.watsen.net>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C08FE3A03EF for <netconf@ietfa.amsl.com>; Wed, 2 Jun 2021 07:34:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com
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 qsGFKv5vL153 for <netconf@ietfa.amsl.com>; Wed, 2 Jun 2021 07:34:33 -0700 (PDT)
Received: from a8-88.smtp-out.amazonses.com (a8-88.smtp-out.amazonses.com [54.240.8.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C67D3A0332 for <netconf@ietf.org>; Wed, 2 Jun 2021 07:34:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1622644472; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:Feedback-ID; bh=z+XZX8YwJATQRiSBn5APs4zqw4s2sAbCjsGUPPfqU14=; b=Pi0cs3ZMvUy5V1Hc0SijSMTmQCwuQCMsrT81+BL0OTgKkCECUltJfaLLmoMyUnZI OGwbqQy/Tua6yagl6fzFxwjW6N/pFH/YHY2GDRqOkViyY5bHnbXeUQj2BclgRQ4xSUZ 7LxSU2k9HKdpUrOiM2sSO20isZnidgIrENRJyJ7g=
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
From: Kent Watsen <kent+ietf@watsen.net>
In-Reply-To: <20210602055558.m4qzan73lt6ebnmt@anna.jacobs.jacobs-university.de>
Date: Wed, 02 Jun 2021 14:34:32 +0000
Cc: Andy Bierman <andy@yumaworks.com>, "netconf@ietf.org" <netconf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <01000179cd25b935-41381155-4d11-4e36-a6ec-b71b55fde875-000000@email.amazonses.com>
References: <162197047222.6755.5719177112947542346@ietfa.amsl.com> <01000179af378320-73241cbb-c5a4-45dd-8c87-03ff603cc2f0-000000@email.amazonses.com> <CABCOCHTjKHE1pbP05tcBGvx1Ms5LJsvmtBe1te4kOr-1jwTJPw@mail.gmail.com> <01000179c9c98396-98e37454-f6bd-4753-92a4-0c8911d102d9-000000@email.amazonses.com> <20210602055558.m4qzan73lt6ebnmt@anna.jacobs.jacobs-university.de>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2021.06.02-54.240.8.88
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/NrV02W7Pjp7N5oIlpnDvjz9sFw0>
Subject: Re: [netconf] [Last-Call] Yangdoctors last call review of draft-ietf-netconf-ssh-client-server-24
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jun 2021 14:34:35 -0000

>> It seems that the following might works:
>> 
>>  - In ietf-ssh-client, rename "userauth-*" to "client-ident-*”
>>      - since client-side config, the “userauth” nomenclature is not as strong
>>      - aligns “client-ident” usage with the “tls” and “http” drafts
>> 
>>  - In ietf-ssh-server, rename "userauth-*" to "local-user-auth-*”
>>      - makes sense as nodes depend from a container called “users” that
>>        has a if-feature statement “local-users-supported”
>>      - thus, can simultaneously be parsed as "[local-user]-auth-*”
>>        and "local-[user-auth]-*”
>> 
>> I’ll make this  change if no objections.
> 
> I have not understood which problem this renaming solves. SSH
> authentication mechanisms have well established names, why is it
> useful to invent different names?

Focus on the method names:

      "publickey"             REQUIRED
      "password"              OPTIONAL
      "hostbased"             OPTIONAL
      "none"                  NOT RECOMMENDED

The “userauth” string isn’t important.

K.