Re: [Curdle] WG status and rsa-sha2 as public key algorithm

Румен Петров <pkixssh@roumenpetrov.info> Thu, 04 May 2017 19:17 UTC

Return-Path: <pkixssh@roumenpetrov.info>
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 A564612869B for <curdle@ietfa.amsl.com>; Thu, 4 May 2017 12:17:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.701
X-Spam-Level:
X-Spam-Status: No, score=-0.701 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
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 dJKE_ri2blUq for <curdle@ietfa.amsl.com>; Thu, 4 May 2017 12:17:56 -0700 (PDT)
Received: from rila.superhosting.bg (rila.superhosting.bg [91.196.125.212]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB9B612947B for <curdle@ietf.org>; Thu, 4 May 2017 12:17:55 -0700 (PDT)
Received: from [78.128.48.21] (port=39090 helo=[192.168.0.10]) by rila.superhosting.bg with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <pkixssh@roumenpetrov.info>) id 1d6MG8-003Qt9-GM for curdle@ietf.org; Thu, 04 May 2017 22:17:52 +0300
Message-ID: <590B7E60.8000204@roumenpetrov.info>
Date: Thu, 04 May 2017 22:17:52 +0300
From: =?UTF-8?B?0KDRg9C80LXQvSDQn9C10YLRgNC+0LI=?= <pkixssh@roumenpetrov.info>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0 SeaMonkey/2.30
MIME-Version: 1.0
To: curdle <curdle@ietf.org>
References: <CADZyTkkd-JpsE89z=P10Y0esc1NCZydD5NqMTs8E5xUz-DMT_g@mail.gmail.com> <58F475B5.4090504@roumenpetrov.info> <CADPMZDBjgpzMKp1UJqWMC_xRZpfce=wOOsE51HwY2dEO73kKeA@mail.gmail.com> <CADPMZDBS3yFxWmioNRV+Vx-ThTPW636ydr1fz76vNP52DjAtZA@mail.gmail.com> <1778170c976e43569d34f051bba51f4c@ustx2ex-dag1mb1.msg.corp.akamai.com> <CADZyTknNkAWHUeqk-BQqYU_6jTGVgPurhqF7=Am7Xk7OT=D-gQ@mail.gmail.com> <CADZyTk=3pZb40upVHPuG8hYEWOCpu2hhdyBpiZ9t5+v2_AYzAQ@mail.gmail.com> <590A2FA0.3070601@roumenpetrov.info> <CADZyTknVERTsAWeU-Gk92_25JvK9otQ_9PLY=m19XM-eVH-efQ@mail.gmail.com> <590ABDAD.6000900@roumenpetrov.info> <CADPMZDB0+SdzYvMEaREHDK1C9dm+TcfehVatVtF8MMah92813A@mail.gmail.com>
In-Reply-To: <CADPMZDB0+SdzYvMEaREHDK1C9dm+TcfehVatVtF8MMah92813A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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:
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/6QJiu6pUDhwDU3nil9YXYIju2z8>
Subject: Re: [Curdle] WG status and rsa-sha2 as public key algorithm
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 04 May 2017 19:17:59 -0000

Hi denis,

denis bider wrote:
> Hello everyone,
>
> in the interest of consensus, I have adopted the requested terminology
> changes in the two drafts. What was previously "signature algorithm" is now
> "public key algorithm", and what was previously "public key algorithm" is
> now "public key format".
>
> Please review and let me know.
10x for new versions.

Main context of *draft-ietf-curdle-rsa-sha2-07.txt* is fine with me.
I still think that chapter 4 IANA Considerations could be simplified to 
list only public key algorithm but this is not so important.
The chapter refer to RFC4250 but section 7.1 Normative References lack 
reference to it. May be is good to list RFC4250 as well.
No other remarks.



About draft-ietf-curdle-ssh-ext-info-06.txt:
The name of extension "server-sig-algs" must be changed as well.
First because extension contain  abbreviation of signature in name 
(description is fine),
second because existing implementation does not follow rules from 
RFC4250, section 4.6.1. "Conventions for Names" and
third(!) due to broken OpenSSH implementation: " ...where SHA2 RSA 
signature methods were not being correctly advertised..." fixed in 7.5.


[SNIP]

Regards,
Roumen Petrov