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

Румен Петров <pkixssh@roumenpetrov.info> Wed, 03 May 2017 19:31 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 9C59E129AF1 for <curdle@ietfa.amsl.com>; Wed, 3 May 2017 12:31:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.589
X-Spam-Level:
X-Spam-Status: No, score=-2.589 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, T_HTML_ATTACH=0.01] 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 CM_IFvOAI5fp for <curdle@ietfa.amsl.com>; Wed, 3 May 2017 12:31:34 -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 4EF0D129AEE for <curdle@ietf.org>; Wed, 3 May 2017 12:29:39 -0700 (PDT)
Received: from [78.128.48.21] (port=45196 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 1d5zxw-001e1U-8a for curdle@ietf.org; Wed, 03 May 2017 22:29:36 +0300
Message-ID: <590A2FA0.3070601@roumenpetrov.info>
Date: Wed, 03 May 2017 22:29:36 +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>
In-Reply-To: <CADZyTk=3pZb40upVHPuG8hYEWOCpu2hhdyBpiZ9t5+v2_AYzAQ@mail.gmail.com>
Content-Type: multipart/mixed; boundary="------------020000000909070005050907"
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/orCePLdoa1Id3mkJnn8Nb1czqsw>
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: Wed, 03 May 2017 19:31:43 -0000

Hi
Daniel Migault wrote:
> Hi,
>
> [snip]
> Romen please re-state your issues with the draft, clearly expose the issues
> as well as the alternate you would fine acceptable.

I would like to propose an redaction over draft-ietf-curdle-rsa-sha2-03 
(see attached file draft-ietf-curdle-rsa-sha2-03+rpetrov.txt).
Attached file" draft-ietf-curdle-rsa-sha2-03+rpetrov.wdiff.html" shows 
modifications as word-diff in html format :
- removed: red font, strikeout
- added : green font


I chose version 3 as this version is mostly fine with me except few 
substitutions(rewording)  to follow style of previous SSH related 
documents - [RFC4253], [RFC5656] and [RFC6187] (see modifications in 
chapter 2 Public Key Algorithms).
No modification in structure of messages, formats and etc.


Using mostly word "Public Key Algorithm" will allow section(chapter) "4. 
IANA Considerations" to be written in very simple manner.
The totally rewritten chapter adds references to [RFC4250]  and [RFC4251] .


Section "3.  Discovery of signature algorithms supported by servers" in 
not updated yet (depends from another discussion).


Regards,
Roumen Petrov