Re: [netconf] Latest ietf-netconf-server draft and related modules

Kent Watsen <kent+ietf@watsen.net> Wed, 05 May 2021 20:12 UTC

Return-Path: <010001793e2953ba-e3b3a097-91de-4df6-9096-072452c1b0d8-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 DDEFB3A1F55 for <netconf@ietfa.amsl.com>; Wed, 5 May 2021 13:12:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.908
X-Spam-Level:
X-Spam-Status: No, score=-2.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H5=-1, RCVD_IN_MSPIKE_WL=-0.01, 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 CVcrND_FNeGI for <netconf@ietfa.amsl.com>; Wed, 5 May 2021 13:12:48 -0700 (PDT)
Received: from a48-95.smtp-out.amazonses.com (a48-95.smtp-out.amazonses.com [54.240.48.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A7F33A1F53 for <netconf@ietf.org>; Wed, 5 May 2021 13:12:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1620245566; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:Feedback-ID; bh=gNbqbhWugM0a0tY+qSZn0SMcumqxrCtiqHhh1FExWdg=; b=Jwxq0usd07v7DNjcpasJRKrS3yawKymUPEkBFGz4cOg+m/C1myKAy3bw7Qa+MvCI 9rrPfgc6lE2DCQcZCLqxPlfblYVc3P93uZUsRYDbgmaUwMcVkDY5HKwK6+zLQOURbdl JVkX3y5650Mt4xhAYO6VQ+RXI7GiPPOtGP310no4=
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: <20210429190209.dheo4q2sol5jt473@anna.jacobs.jacobs-university.de>
Date: Wed, 5 May 2021 20:12:46 +0000
Cc: =?utf-8?Q?Michal_Va=C5=A1ko?= <mvasko@cesnet.cz>, "netconf@ietf.org" <netconf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <010001793e2953ba-e3b3a097-91de-4df6-9096-072452c1b0d8-000000@email.amazonses.com>
References: <971-608af580-15-2e293dc0@34342692> <010001791eead163-ac714f94-ac4f-455a-adcf-20577ce13dc4-000000@email.amazonses.com> <20210429190209.dheo4q2sol5jt473@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.05.05-54.240.48.95
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/Zw2JoquNfhJtWOkLbjljmFIiodw>
Subject: Re: [netconf] Latest ietf-netconf-server draft and related modules
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, 05 May 2021 20:12:51 -0000

Hi Juergen,

>> How about this (the last sentence), in ietf-ssh-client?
>> 
>>        The credentials are unordered.  Clients may initially send
>>         any configured method or, per RFC 4252, Section 5.2, send
>>         the 'none' method to prompt the server to provide a list
>>         of productive methods.  Whenever a choice amongst methods
>>         arises, implementations SHOULD use a default ordering that
>>         prioritizes automation over human-interaction.

Not directed at Juergen, but I’ll assume that the last sentence is fine.


> I find the terminology at several places confusing. We have been
> talking about the order in which user authentication methods are
> tried. This has nothing to do with 'credential' ordering.
> 
> In draft-ietf-netconf-ssh-client-server-23.txt, I see
> 
>   *  The "client-identity" node configures a "username" and
>      credentials, each enabled by a "feature" statement defined in
>      Section 3.1.1.

Replaced “credentials” with "authentication methods”
   - for both modules and the draft itself


> Why is this called 'client-identity', should this not be called
> user-authentication instead to align with SSH terminology?
> 
> The guarding features likely also should have different names:
> client-identity-publickey -> userauth-publickey
> client-identity-password -> userauth-password
> client-identity-hostbased -> userauth-hostbased
> client-identity-none -> userauth-none
> 

In ietf-ssh-client, renamed "client-identity-*" to "userauth-*"
In ietf-ssh-server, renamed "client-auth-*" to "userauth-*"


Thanks,
Kent