From nobody Mon Jul 2 01:52:20 2018 Return-Path: X-Original-To: curdle@ietf.org Delivered-To: curdle@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BC6691277BB; Mon, 2 Jul 2018 01:52:19 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: curdle@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.81.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <153052153971.27909.10469976224660738011@ietfa.amsl.com> Date: Mon, 02 Jul 2018 01:52:19 -0700 Archived-At: Subject: [Curdle] I-D Action: draft-ietf-curdle-ssh-ed25519-ed448-01.txt X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.26 List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jul 2018 08:52:20 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the CURves, Deprecating and a Little more Encryption WG of the IETF. Title : Ed25519 and Ed 448 public key algorithms for the Secure Shell (SSH) protocol Authors : Ben Harris Loganaden Velvindron Filename : draft-ietf-curdle-ssh-ed25519-ed448-01.txt Pages : 6 Date : 2018-07-02 Abstract: This document describes the use of the Ed25519 and Ed448 digital signature algorithm in the Secure Shell (SSH) protocol. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-curdle-ssh-ed25519-ed448/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-curdle-ssh-ed25519-ed448-01 https://datatracker.ietf.org/doc/html/draft-ietf-curdle-ssh-ed25519-ed448-01 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-curdle-ssh-ed25519-ed448-01 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Mon Jul 2 08:54:15 2018 Return-Path: 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 B1300130F90 for ; Mon, 2 Jul 2018 08:54:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 L6pKbEtkd2kD for ; Mon, 2 Jul 2018 08:54:11 -0700 (PDT) Received: from mx1.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05503130E35 for ; Mon, 2 Jul 2018 08:54:10 -0700 (PDT) Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 2373E814F0A3; Mon, 2 Jul 2018 15:54:10 +0000 (UTC) Received: from rhino.ipa.ssimo.org (ovpn-116-230.phx2.redhat.com [10.3.116.230]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 973BD1C596; Mon, 2 Jul 2018 15:54:08 +0000 (UTC) Message-ID: <79c83729b7778cab8f823d9e8dd85488e9482156.camel@redhat.com> From: Simo Sorce To: Eric Rescorla , Simo Sorce Cc: curdle , Hubert Kario Date: Mon, 02 Jul 2018 11:54:06 -0400 In-Reply-To: References: <1526923646.10011.43.camel@redhat.com> <34725207.E0R9U7BB6Z@pintsize.usersys.redhat.com> <1527683712.25240.42.camel@redhat.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.11.54.5 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.8]); Mon, 02 Jul 2018 15:54:10 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.8]); Mon, 02 Jul 2018 15:54:10 +0000 (UTC) for IP:'10.11.54.5' DOMAIN:'int-mx05.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'simo@redhat.com' RCPT:'' Archived-At: Subject: Re: [Curdle] AD Review of draft-ietf-curdle-gss-keyex-sha2-05 X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jul 2018 15:54:14 -0000 Hi Eric, I posted a new draft with extensive modification to Section 5, hopefully they meet your requests. nothing has changed of the described protocol itself, just stuff got shuffled around and I also provided a little artwork consistent with RFC 5656 to hopefully aid at better understanding of the flow. HTH, Simo. On Wed, 2018-05-30 at 06:24 -0700, Eric Rescorla wrote: > Sure. I was thinking something like this > > 5.1. > 5.1.1. Generic Procedures > - Generating a DH ephemeral > - Verifying the peer's ephemeral > - Computing the shared key > - Verifying the output > - Computing the key hash and MIC > > 5.1.2. GSS Key Exchange Steps > Client calls GSS_Init_sec_context()... [5.1.1 step 2] > Server verifies Q_C and calls GSS_Accept_sec_context [5.1.1, step 4] > Server generates ephemeral and computes the shared key [reduced 5.1.1 > step 5] > Server call to GSS_Accept_sec_context [5.1.1 step 6] > Client verifies Q_S and computes the shared key [5.1.1 step 7++] > Client calls GSS_VErifyMIC [5.1.1. step 8] > > It's hard for me to see if you caught everything else. If you want to > submit a new draft, I can take a look, either before or after this > change. > > -Ekr > > > > > > > On Wed, May 30, 2018 at 5:35 AM, Simo Sorce > wrote: > > On Wed, 2018-05-30 at 12:25 +0200, Hubert Kario wrote: > > > On Tuesday, 29 May 2018 21:27:34 CEST Eric Rescorla wrote: > > > > On Mon, May 21, 2018 at 10:27 AM, Simo Sorce > > wrote: > > > > > On Fri, 2018-05-18 at 14:12 -0700, Eric Rescorla wrote: > > > > > > These changes look fine, though they only address some of > > my comments. > > > > > > > > > > Just for clarity, is the change to describe the whole DH > > exchange in > > > > > one place what you see missing ? Is that a deal breaker ? > > > > > Anything else ? > > > > > > > > That and the repeated text that is the same for each group. > > > > > > the fix for repeated text about groups is already merged to > > master, for ECDHE: > > > https://github.com/simo5/ietf/blob/eb03480d5c49e7340302e4974435f3 > > 82ba26a911/ > > > draft-ietf-curdle-gss-keyex-sha2.xml#L537-L553 > > > and for FFDHE: > > > https://github.com/simo5/ietf/blob/eb03480d5c49e7340302e4974435f3 > > 82ba26a911/ > > > draft-ietf-curdle-gss-keyex-sha2.xml#L148-L164 > > > > Thanks Hubert. > > > > Eric, > > it be nice if you could give guidance on how you would like to see > > the > > DH exchange explanation changed, assuming that's the only thing of > > concern left for you, feel free to point out anything else as well. > > > > If you prefer to have a new draft submitted, with the changes > > above, as > > a baseline for further discussion, I can submit one. > > > > Simo. > > _______________________________________________ > Curdle mailing list > Curdle@ietf.org > https://www.ietf.org/mailman/listinfo/curdle From nobody Mon Jul 2 08:54:35 2018 Return-Path: X-Original-To: curdle@ietf.org Delivered-To: curdle@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 749F5130EBF; Mon, 2 Jul 2018 08:54:27 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: curdle@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.81.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <153054686744.16135.13962240646842765600@ietfa.amsl.com> Date: Mon, 02 Jul 2018 08:54:27 -0700 Archived-At: Subject: [Curdle] I-D Action: draft-ietf-curdle-gss-keyex-sha2-06.txt X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.26 List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jul 2018 15:54:28 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the CURves, Deprecating and a Little more Encryption WG of the IETF. Title : GSS-API Key Exchange with SHA2 Authors : Simo Sorce Hubert Kario Filename : draft-ietf-curdle-gss-keyex-sha2-06.txt Pages : 12 Date : 2018-07-02 Abstract: This document specifies additions and amendments to RFC4462. It defines a new key exchange method that uses SHA-2 for integrity and deprecates weak DH groups. The purpose of this specification is to modernize the cryptographic primitives used by GSS Key Exchanges. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-curdle-gss-keyex-sha2/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-curdle-gss-keyex-sha2-06 https://datatracker.ietf.org/doc/html/draft-ietf-curdle-gss-keyex-sha2-06 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-curdle-gss-keyex-sha2-06 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Fri Jul 6 13:51:36 2018 Return-Path: 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 13EDD130DD8 for ; Fri, 6 Jul 2018 13:51:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.398 X-Spam-Level: X-Spam-Status: No, score=-1.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 6OSA2LLLDvZB for ; Fri, 6 Jul 2018 13:51:32 -0700 (PDT) Received: from mail-lf0-x242.google.com (mail-lf0-x242.google.com [IPv6:2a00:1450:4010:c07::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E216130DC8 for ; Fri, 6 Jul 2018 13:51:32 -0700 (PDT) Received: by mail-lf0-x242.google.com with SMTP id y200-v6so10771640lfd.7 for ; Fri, 06 Jul 2018 13:51:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=Vso9BBSTjyBsqGSZK/AijtWA+4QaNnjSGFT/K4T4gKE=; b=Q+FGwvSrLg2EVLDZT1Hu9bDon68eL2IsojEZyxQj5FWWFqhNkTKx1wltubM6TOPMM1 c/9wVnKuiAl8/q15sjjwR3ON1K7KhFPEldKSDYfSZ7Pq4hYtlTkROJmh4ywIqYzMSOqz ooFkqAnLhR3Bp5L9SXf4FviAR46NZDV7aMt00XJV+LwR7fzSNMLIQgJK6LSjyYVqZypa Gxpl6r3iYckBA+T2MsxQZt++oA97aYlP4AAR+/B2/fJgG9rcqJd296lW0bZNn1scjt2b ZFqDHkSa0knowf0rl5cJy98UG56RB96WxNdn7o18Pp7fnK5l7HinW2Ll/IZ7r5STXm6/ v85g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=Vso9BBSTjyBsqGSZK/AijtWA+4QaNnjSGFT/K4T4gKE=; b=h5zByGxg7D9ciVG2jH3eg1v6fQO2sLwJlByJ18Oa+5Ptf5iQ9B+EaGzdU3lv7QJ7In Alb6c/Wy0T4YVx7PekW7ZzT3cH0k9bTWhQ5aBpcE5jgwMHGaVL5qfewvdeZt/aDClFkZ jWHSdgctp0zCOi57ULN9/IEpvRe3M5GASZZT9CsdBket14NUuWdpycXmrxVELITgf8te pATwTUrmuRjDuHwFSBylEcZnoFGyKKXdknCLCl7hna4pSXkDZDYc4JmLmW0YpkX7DD7Q 1u60t9jYbBZzUqisInte7pika1MOHkaON8mDRrYQQSV8XgC3OZ1JnQ3R2A6rLDYjcm9o JNAg== X-Gm-Message-State: APt69E3wDkhAJG5OMs8ayXdGw31n3FNYPBUlnZvtR9GkuCFVuVgc+Qty aYh813EdLdI6PNpMVuaMknnfDXjOOCLzebnLV70= X-Google-Smtp-Source: AAOMgpe8U8xPwpu0BKEWZrkExUDtmKCyM0c0zQwUh3NeSOKN6RJxGsCc+EjiOVo4paWJVPlW16tssXnxCpumdvRvF/8= X-Received: by 2002:a19:501e:: with SMTP id e30-v6mr8058035lfb.71.1530910290503; Fri, 06 Jul 2018 13:51:30 -0700 (PDT) MIME-Version: 1.0 Sender: mglt.ietf@gmail.com Received: by 2002:a2e:119d:0:0:0:0:0 with HTTP; Fri, 6 Jul 2018 13:51:29 -0700 (PDT) In-Reply-To: <153052153971.27909.10469976224660738011@ietfa.amsl.com> References: <153052153971.27909.10469976224660738011@ietfa.amsl.com> From: Daniel Migault Date: Fri, 6 Jul 2018 16:51:29 -0400 X-Google-Sender-Auth: 2jpivXWx8R0zV-mLqsyTT2hHZoQ Message-ID: To: curdle Content-Type: multipart/alternative; boundary="0000000000000c6e3905705ad46c" Archived-At: Subject: Re: [Curdle] I-D Action: draft-ietf-curdle-ssh-ed25519-ed448-01.txt X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jul 2018 20:51:34 -0000 --0000000000000c6e3905705ad46c Content-Type: text/plain; charset="UTF-8" Hi, We are starting a WGLC period. Please provide your review and feed backs by July 20. Yours, Daniel On Mon, Jul 2, 2018 at 4:52 AM, wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the CURves, Deprecating and a Little more > Encryption WG of the IETF. > > Title : Ed25519 and Ed 448 public key algorithms for the > Secure Shell (SSH) protocol > Authors : Ben Harris > Loganaden Velvindron > Filename : draft-ietf-curdle-ssh-ed25519-ed448-01.txt > Pages : 6 > Date : 2018-07-02 > > Abstract: > This document describes the use of the Ed25519 and Ed448 digital > signature algorithm in the Secure Shell (SSH) protocol. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-curdle-ssh-ed25519-ed448/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-curdle-ssh-ed25519-ed448-01 > https://datatracker.ietf.org/doc/html/draft-ietf-curdle- > ssh-ed25519-ed448-01 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-curdle-ssh-ed25519-ed448-01 > > > Please note that it may take a couple of minutes from the time of > submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > Curdle mailing list > Curdle@ietf.org > https://www.ietf.org/mailman/listinfo/curdle > --0000000000000c6e3905705ad46c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

We are starting a W= GLC period. Please provide your review and feed backs by July 20.

Yours,
Daniel

On Mon, Jul 2, 2018 at 4:52= AM, <internet-drafts@ietf.org> wrote:

A New Internet-Draft is available from the on-line Internet-Drafts director= ies.
This draft is a work item of the CURves, Deprecating and a Little more Encr= yption WG of the IETF.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:= Ed25519 and Ed 448 public key algorithms for the Secure Shell (SSH) protoc= ol
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Ben = Harris
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 Loganaden Velvindron
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet= f-curdle-ssh-ed25519-ed448-01.txt
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:= 6
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 := 2018-07-02

Abstract:
=C2=A0 =C2=A0This document describes the use of the Ed25519 and Ed448 digit= al
=C2=A0 =C2=A0signature algorithm in the Secure Shell (SSH) protocol.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-curdle-ssh-ed25519-ed448/

There are also htmlized versions available at:
https://tools.ietf.org/html/d= raft-ietf-curdle-ssh-ed25519-ed448-01
https://datatracker.ietf= .org/doc/html/draft-ietf-curdle-ssh-ed25519-ed448-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdi= ff?url2=3Ddraft-ietf-curdle-ssh-ed25519-ed448-01


Please note that it may take a couple of minutes from the time of submissio= n
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
Curdle mailing list
Curdle@ietf.org
https://www.ietf.org/mailman/listinfo/curdle

--0000000000000c6e3905705ad46c-- From nobody Fri Jul 6 14:13:50 2018 Return-Path: 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 2FDF7130F62 for ; Fri, 6 Jul 2018 14:13:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.398 X-Spam-Level: X-Spam-Status: No, score=-1.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 SRZvfDKIBN44 for ; Fri, 6 Jul 2018 14:13:45 -0700 (PDT) Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E2D7130DE3 for ; Fri, 6 Jul 2018 14:13:45 -0700 (PDT) Received: by mail-lf0-x231.google.com with SMTP id u202-v6so10803794lff.9 for ; Fri, 06 Jul 2018 14:13:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=/UHos086Gurw2NVDs29lqRLvXsV1T3ehkmCT8n4Rdc8=; b=IFc0RriVERHN8v+ug2O15AELYHqTWuMVAU6aN6JsT7VlwRkmy94504aOn5E6UC3kEO RBJoFIJbu4pEU4uDvEEbDLtye1UrcGmUocQCX9VXBfpPAEbGhTwzWe9Iof1hHSgqrDPf eWycNsd4Yn1A0HjfDPid+fv1hpSfD+yMS0ror1fv83u73MtTYJiQw69nu2tL0j9pA/mY TsSF2JOseiZfWl5H9LjOwJnRDoUzn7BWliwonU0V5/NdNugOuz55NNWZF4a50/EbJjxr iQznfq1hd5VYQAQh77GxE1qSiqkTc7uhvYx8jmzqkLLBwnG7oYdaOmKQJUVaxyXkjDU1 nL8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=/UHos086Gurw2NVDs29lqRLvXsV1T3ehkmCT8n4Rdc8=; b=tbD/XDtkJNTCGGsH/0ETYi9392B/0N0ckI6/C7j2tqng0+BtNJ4KmrkxQRSY6LUHYf EjCQG789lnaqlTLAtxfu47R8mAgw8UkinYS0ispfCOb2zSVjnb98BKHM/AHrNpLFIsdV 5Fp+5zWvqJigZGRE8Mr1XCuAyRG2BJKLEiwEd9klg86uzbgZSA38FFI6MfnVXSqWD/wT bh2V0YHCBONzV7QoaRA8fh5cUTWzvrf8WRWYHsgA4ueNalRA+VAUPzA2aQn5XsDgTD6v N3BX4AtCAzIPRKZ5m9/mOpa9uE1NUxxEWYAencfPniX3j4ZRsr/PTWClr1ypZ9n16h5k GjAQ== X-Gm-Message-State: APt69E1XGPX50wBDyFnInoMDcvHmuVVWHgXCO7v5VIS1ul6J5LoAfN0j xiCRegjr9fTquzDYzBv8S1NnH1xf3SfIZ2XJfrQ= X-Google-Smtp-Source: AAOMgpc9KHcvu/vJEA1oBTOqEd/Ixw26Gf/mDl2Zpc0rUlFBoF7gALSsnZ+Hwx0JVkcezejqb8vCiUi/20ewqPdg/Vk= X-Received: by 2002:a19:6902:: with SMTP id e2-v6mr8087110lfc.70.1530911623195; Fri, 06 Jul 2018 14:13:43 -0700 (PDT) MIME-Version: 1.0 Sender: mglt.ietf@gmail.com Received: by 2002:a2e:119d:0:0:0:0:0 with HTTP; Fri, 6 Jul 2018 14:13:42 -0700 (PDT) In-Reply-To: References: From: Daniel Migault Date: Fri, 6 Jul 2018 17:13:42 -0400 X-Google-Sender-Auth: LzGkTtIiTj9tmw0N30HqKK3dEaM Message-ID: To: curdle Content-Type: multipart/alternative; boundary="0000000000007bb06c05705b23df" Archived-At: Subject: Re: [Curdle] draft-ietf-curdle-rc4-die-die-die-06 review X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jul 2018 21:13:49 -0000 --0000000000007bb06c05705b23df Content-Type: text/plain; charset="UTF-8" Hi, We would like to move the draft to the IESG, however, the draft has not been updated to address the comments received on the mailing list. We have privately contacted the author 3 times with the email address provided to the draft, but we did not receive any response. The purpose of this email is to first try to contact the author of draft via another channel and understand if he has any plan to move the draft forward. In addition, we would also like to see if there is any interest by some members of the group to co-author the draft and move the draft forward. For those interested in co-authoring the draft, please contact us privately. Our goal is to have all drafts - that is the two remaining drafts in WGLC - submitted by end of august. Yours, Rich and Daniel On Tue, May 15, 2018 at 1:00 PM, Daniel Migault wrote: > Hi, > > Please find my review for draft-ietf-curdle-rc4-die-die-die-06 [1]. I > have also proposed text, so please comment the review in the mail. I am > willing to start a WGLC as soon as the draft is being updated. > > Yours, > Daniel > > > [1] https://tools.ietf.org/html/draft-ietf-curdle-rc4-die-die-die-06 > > > RFC-Editor: > > I personally find the ton of the sentence a bit aggressive, thus I would > remove it or just leave the RFC reference. > > """ > Non-ASCII characters are allowed in RFCs as per RFC 7997. > """ > > I see deprecation and move to historic status as very similar to > draft-ietf-curdle-des-des-des-die-die-die-05 and I assume that is > correct. > > Abstract: > > The sentence below is a bit hard to parse. > "" > and formally obsoletes and moves to > Historic RFC 4345. > "" > > I would propose instead: > > """ > This document deprecates RC4 in Secure Shell (SSH). Therefore, this > document updates RFC 4253, and moves to Historic RFC 4345. > """ > > 1. Introduction > > > """ > RC4 is broken"" > """ > > Although English is not my main language, it sounds a bit abrupt to me and > it might be preferred to sue something around the lines of > draft-ietf-curdle-des-des-des-die-die-die-05: > > RC4 encryption is steadily weakening in cryptographic strength, and the > deprecation process should be begun for their use in SSH. > > > It seems to me that sections 1, 2 3 could be merged. I would propose the > following text. I am providing comments in . > > > > 1. Introduction > > > The usage of RC4 suites ( also designated as arcfour ) for SSH are > specified in RFC 4253 and RFC 4345. RFC 4253 specifies the allocation of > the "arcfour" cipher for SSH. RFC 4345 specifies and allocates the the > "arcfour-128" and "arcfour-256" ciphers for SSH. > > RC4 encryption is steadily weakening in cryptographic strength > [RFC7457][draft-ietf-curdle-des-des-des-die-die-die-05], and the > deprecation process should be begun for their use in Secure Shell (SSH) > [RFC4253]. Accordingly, RFC 4253 is updated to note the deprecation of the > RC4 ciphers and RFC 4345 is moved to Historic as all ciphers it specifies > MUST NOT be used. > > I believe that this document is very closed to > [draft-ietf-curdle-des-des-des-die-die-die-05] and as such a reference to > it should be mentioned. > > > 2. Requirements Notation > > The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", > "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this > document are to be interpreted as described in BCP 14 [RFC2119, RFC8174] > when, and only when, they appear in all capitals, as shown here. > > 3. Updates to RFC 4253 > > RFC 4253 is updated to prohibit arcfour's use in SSH. > > > """ > The last sentence of the paragraph on RC4 (called "arcfour" > in [RFC4253]) in Section 6.3 of [RFC4253] > """ > > I believe that it might be clearer to quote the text as it is not easy to > locate it. I would propose the text below. > > RFC 4253 allocate the "arcfour" cipher in Section 6.3 by defining a list > of defined ciphers where the "arcfour" cipher appears as optional as > mentioned below: > > """ > arcfour OPTIONAL the ARCFOUR stream cipher > with a 128-bit key > """ > > The current document updates the status of the "arcfour" ciphers in the > list of RFC 4253 Section 6.3 by moving it from OPTIONAL to MUST NOT. > > """ > arcfour MUST NOT the ARCFOUR stream cipher > with a 128-bit key > """ > > RFC 4253 defines the "arcfour" ciphers with the text mentioned below: > """ > The "arcfour" cipher is the Arcfour stream cipher with 128-bit keys. > The Arcfour cipher is believed to be compatible with the RC4 cipher > [SCHNEIER]. Arcfour (and RC4) has problems with weak keys, and > should be used with caution. > """ > > The current document updates RFC 4253 Section 6.3 by replacing th etext > above with the following text: > > """ > The "arcfour" cipher is the Arcfour stream cipher with 128-bit keys. > The Arcfour cipher is believed to be compatible with the RC4 cipher > [SCHNEIER]. Arcfour (and RC4) is steadily weakening in cryptographic > strength [RFC7457][draft-ietf-curdle-des-des-des-die-die-die-05], and > MUST NOT be used. > """ > > 4. IANA Considerations > > There is a reference to 3DES i think should be removed. In addition, > IANA cannot be required to update RFCs. IANA is assigned to update the SSH > registries. With [IANA] being an informational reference to > https://www.iana.org/assignments/ssh-parameters/ssh-parameters.xhtml, I > would propose the following text : > > The IANA is requested to update the Encryption Algorithm Name Registry of > the Secure Shell (SSH) Protocol Parameters [IANA]. The Registration > procedure is IETF Review which is achieved by this document. The registry > should be updated as follows: > > Encryption Algorithm Name Reference Note > arcfour [RFC-TBD] > arcfour128 [RFC-TBD] > arcfour256 [RFC-TBD] > > > Where TBD is the RFC number assigned to the document. > > > > --0000000000007bb06c05705b23df Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

We would like to mo= ve the draft to the IESG, however, the draft has not been updated to addres= s the comments received on the mailing list. We have privately contacted th= e author 3 times with the email address provided to the draft, but we did n= ot receive any response. The purpose of this email is to first try to conta= ct the author of draft via another channel and understand if he has any pla= n to move the draft forward. In addition, we would also like to see if ther= e is any interest by some members of the group to co-author the draft and m= ove the draft forward. For those interested in co-authoring the draft, plea= se contact us privately.

Our goal is to have = all drafts - that is the two remaining drafts in WGLC - submitted by end of= august.

Yours,
Rich and Danie= l

On Tue, May 15, 2018 at 1:00 PM, Daniel Migault <daniel.migault= @ericsson.com> wrote:
Hi,

Please find my review fo= r draft-ietf-curdle-rc4-die-die-die-06 [1]. I have also proposed text,= so please comment the review in the mail. I am willing to start a WGLC as = soon as the draft is being updated.

Yours,
Daniel


RFC-Editor:

I = personally find the ton of the sentence a bit aggressive, thus I would remo= ve it or just leave the RFC reference.

"""
Non-AS= CII characters are allowed in RFCs as per RFC 7997.
"""
I see deprecation and move to historic status as very similar to draf= t-ietf-curdle-des-des-des-die-die-die-05 and I assume that is correct.=

Abstract:

The sentence below is a bit hard to parse.
&q= uot;"
and formally obsoletes and moves to
=C2=A0=C2=A0 Historic = RFC 4345.
""

I would propose instead:

"&qu= ot;"
This document deprecates RC4 in Secure Shell (SSH).=C2= =A0 Therefore, this
=C2=A0=C2=A0 document updates RFC 4253, and moves to= Historic RFC 4345.
"""

1. Introduction

"""
RC4 is broken""
"""
<= br>Although English is not my main language, it sounds a bit abrupt to me a= nd it might be preferred to sue something around the lines of draft-ietf-cu= rdle-des-des-des-die-die-die-05:

RC4 encryption is steadily wea= kening in cryptographic strength, and the deprecation process should be beg= un for their use in SSH.


It seems to me that sections 1, 2 3 cou= ld be merged. I would propose the following text. I am providing comments i= n <mglt></mglt>.



1. Introduction


The = usage of RC4 suites ( also designated as arcfour ) for SSH are specified in= RFC 4253 and RFC 4345. RFC 4253 specifies the allocation of the "arcf= our" cipher for SSH. RFC 4345 specifies and allocates the the "ar= cfour-128" and "arcfour-256" ciphers for SSH.

RC4 en= cryption is steadily weakening in cryptographic strength [RFC7457][draft-ie= tf-curdle-des-des-des-die-die-die-05], and the deprecation process sho= uld be begun for their use in Secure Shell (SSH) [RFC4253]. Accordingly, RF= C 4253 is updated to note the deprecation of the RC4 ciphers and RFC 4345 i= s moved to Historic as all ciphers it specifies MUST NOT be used.=C2=A0
<mglt>I believe that this document is very closed to [draft-ietf= -curdle-des-des-des-die-die-die-05] and as such a reference to it shou= ld be mentioned. </mglt>


2.=C2=A0 Requirements Notation
=C2=A0The key words "MUST", "MUST NOT", "REQU= IRED", "SHALL", "SHALL NOT", "SHOULD", &= quot;SHOULD NOT", "RECOMMENDED", "MAY", and "= OPTIONAL" in this document are to be interpreted as described in BCP 1= 4 [RFC2119, RFC8174] when, and only when, they appear in all capitals, as s= hown here.

3. Updates to RFC 4253

RFC 4253 is updated to proh= ibit arcfour's use in SSH.

<mglt>
"""The last sentence of the paragraph on RC4 (called "arcfour"
= =C2=A0=C2=A0 in [RFC4253]) in Section 6.3 of [RFC4253]
""&quo= t;

I believe that it might be clearer to quote the text as it is not= easy to locate it. I would propose the text below. </mglt>

RF= C 4253 allocate the "arcfour" cipher in Section 6.3 by defining a= list of defined ciphers where the "arcfour" cipher appears as op= tional as mentioned below:

"""
=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0 arcfour=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 = OPTIONAL=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 the ARCFOUR = stream cipher
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 with a 128-bit key
""&= quot;

The current document updates the status of the "arcfour&q= uot; ciphers in the list of RFC 4253 Section 6.3 by moving it from OPTIONAL= to MUST NOT.

"""
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 = arcfour=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 MUST NOT=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 the ARCFOUR stream ciph= er
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 with a 128-bit key
"""
RFC 4253 defines the "arcfour" ciphers with the text mentioned b= elow:
"""
=C2=A0=C2=A0 The "arcfour" cipher= is the Arcfour stream cipher with 128-bit keys.
=C2=A0=C2=A0 The Arcfou= r cipher is believed to be compatible with the RC4 cipher
=C2=A0=C2=A0 [= SCHNEIER].=C2=A0 Arcfour (and RC4) has problems with weak keys, and
=C2= =A0=C2=A0 should be used with caution.
"""=C2=A0=C2=A0
The current document updates RFC 4253 Section 6.3 by replacing th ete= xt above with the following text:

"""
=C2=A0=C2=A0= The "arcfour" cipher is the Arcfour stream cipher with 128-bit k= eys.
=C2=A0=C2=A0 The Arcfour cipher is believed to be compatible with t= he RC4 cipher
=C2=A0=C2=A0 [SCHNEIER].=C2=A0 Arcfour (and RC4) is steadi= ly weakening in cryptographic strength [RFC7457][draft-ietf-curdle-des= -des-des-die-die-die-05], and
=C2=A0=C2=A0 MUST NOT be used.
"&q= uot;"

4. IANA Considerations

<mglt>There is a ref= erence to 3DES i think should be removed. In addition, IANA cannot be requi= red to update RFCs. IANA is assigned to update the SSH registries. With [IA= NA] being an informational reference to https://www= .iana.org/assignments/ssh-parameters/ssh-parameters.xhtml,=C2= =A0 I would propose the following text :</mglt>

The IANA is re= quested to update the Encryption Algorithm Name=C2=A0 Registry of the Secur= e Shell (SSH) Protocol Parameters [IANA]. The Registration procedure is IET= F Review which is achieved by this document. The registry should be updated= as follows:

Encryption Algorithm Name =C2=A0=C2=A0 =C2=A0Reference = =C2=A0=C2=A0 =C2=A0Note
arcfour =C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0 =C2=A0 = =C2=A0=C2=A0 [RFC-TBD] =C2=A0=C2=A0 =C2=A0
arcfour128 =C2=A0=C2=A0 =C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 [RFC-TBD] =C2=A0=C2=A0 =C2=A0
arcfour256 =C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0 [RFC-TBD] =C2=A0=C2=A0 =C2=A0


Where TBD= is the RFC number assigned to the document.
=C2=A0

<= /div>

--0000000000007bb06c05705b23df-- From nobody Fri Jul 6 14:44:06 2018 Return-Path: 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 234D11310C6 for ; Fri, 6 Jul 2018 14:43:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net 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 a5Q--0isf1ht for ; Fri, 6 Jul 2018 14:43:56 -0700 (PDT) Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 19DA11310AE for ; Fri, 6 Jul 2018 14:43:56 -0700 (PDT) Received: from pps.filterd (m0108158.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w66LhrlQ023804; Fri, 6 Jul 2018 14:43:53 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=to : cc : subject : in-reply-to : references : from : date : message-id : sender : mime-version : content-type; s=PPS1017; bh=fo8WRcD6ZDI02vV+k2GaBbxP8xog00TGuNyF7vpA+ew=; b=MNegTfk3jiYFTpKc3L6GfPpn2FtcU8g15ctYxzJ1q4sVSK0GzeevRwOoDfRP55KLoLdL czEkSFpsmiOO9pUWr2bmZ7Sb7np4oMEQjj4yQgzBx1uG2YJdgarPVYNp3IavtI4Fp7nX /GL02te9mL+1HGGeWsrgR5GaYZyhja5aTsRSe6hZHeA3+2KXIPz/w+lxgubzgERLGNHX uDohd3mFt8n4ID8XUzAuomlVzIgJBDovf0PKImVITfwncQDZwCfdofMv4mVkTD6ffUKF RYMwZpRYRWXlXS9vV3TFU7w3v6LpLBREaSQxFe085kO4KiNOdIxSX7oX4jEaRiYE6Gcc HA== Received: from nam05-by2-obe.outbound.protection.outlook.com (mail-by2nam05lp0243.outbound.protection.outlook.com [216.32.181.243]) by mx0a-00273201.pphosted.com with ESMTP id 2k24bv1esw-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 06 Jul 2018 14:43:53 -0700 Received: from SN4PR0501CA0005.namprd05.prod.outlook.com (2603:10b6:803:40::18) by DM5PR05MB3177.namprd05.prod.outlook.com (2603:10b6:3:c7::7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.952.8; Fri, 6 Jul 2018 21:43:51 +0000 Received: from BY2NAM05FT021.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e52::204) by SN4PR0501CA0005.outlook.office365.com (2603:10b6:803:40::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.952.7 via Frontend Transport; Fri, 6 Jul 2018 21:43:51 +0000 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.12 as permitted sender) Received: from P-EXFEND-EQX-01.jnpr.net (66.129.239.12) by BY2NAM05FT021.mail.protection.outlook.com (10.152.100.158) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.930.2 via Frontend Transport; Fri, 6 Jul 2018 21:43:50 +0000 Received: from P-EXFEND-EQX-01.jnpr.net (10.104.8.54) by P-EXFEND-EQX-01.jnpr.net (10.104.8.54) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Fri, 6 Jul 2018 14:43:50 -0700 Received: from P-EMFE01C-SAC.jnpr.net (172.24.192.43) by P-EXFEND-EQX-01.jnpr.net (10.104.8.54) with Microsoft SMTP Server (TLS) id 15.0.1367.3 via Frontend Transport; Fri, 6 Jul 2018 14:43:50 -0700 Received: from p-mailhub01.juniper.net (10.47.226.20) by P-EMFE01C-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.123.3; Fri, 6 Jul 2018 14:43:50 -0700 Received: from eng-mail01.juniper.net (eng-mail01.juniper.net [10.160.0.88]) by p-mailhub01.juniper.net (8.14.4/8.11.3) with ESMTP id w66Lhndt016681; Fri, 6 Jul 2018 14:43:49 -0700 (envelope-from mdb@juniper.net) Received: from eng-mail01.juniper.net (localhost [127.0.0.1]) by eng-mail01.juniper.net (Postfix) with ESMTP id 369357E817; Fri, 6 Jul 2018 14:43:49 -0700 (PDT) To: Daniel Migault CC: curdle In-Reply-To: References: <153052153971.27909.10469976224660738011@ietfa.amsl.com> Comments: In-reply-to: Daniel Migault message dated "Fri, 06 Jul 2018 16:51:29 -0400." From: "Mark D. Baushke" Date: Fri, 6 Jul 2018 14:43:49 -0700 Message-ID: <83201.1530913429@eng-mail01.juniper.net> Sender: MIME-Version: 1.0 Content-Type: text/plain X-EOPAttributedMessage: 0 X-MS-Office365-Filtering-HT: Tenant X-Forefront-Antispam-Report: CIP:66.129.239.12; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(346002)(136003)(39860400002)(396003)(376002)(2980300002)(199004)(189003)(105596002)(76506005)(486006)(476003)(106466001)(16586007)(76176011)(7126003)(8936002)(11346002)(86362001)(8676002)(186003)(126002)(26005)(53416004)(51416003)(81156014)(81166006)(97876018)(336012)(77096007)(6916009)(305945005)(6306002)(5660300001)(229853002)(6392003)(47776003)(7846003)(4743002)(55016002)(50466002)(48376002)(117636001)(97736004)(2810700001)(6246003)(6266002)(4326008)(478600001)(2906002)(68736007)(7696005)(966005)(426003)(316002)(53936002)(356003)(69596002)(446003)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR05MB3177; H:P-EXFEND-EQX-01.jnpr.net; FPR:; SPF:SoftFail; LANG:en; PTR:InfoDomainNonexistent; A:1; MX:1; X-Microsoft-Exchange-Diagnostics: 1; BY2NAM05FT021; 1:FYplOJD/e7eGGFYFY80gTYdj6hYbwoD5ea/nYFuR/2YR8sqc5st3h50YNNxmcweAGwlcCpxd1bUcsKPl7fRpLVRnFlDzcXqnKuZS4G/VTPOMr8vhG2IGKHaPZQXJHf5o X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: 47c991b9-2b60-4c4d-4759-08d5e3898ff9 X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(5600053)(711020)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(2017052603328)(7153060); SRVR:DM5PR05MB3177; X-Microsoft-Exchange-Diagnostics: 1; DM5PR05MB3177; 3:96CdCt4PXwL2A7Cvk1ItEfDf7v8ZRy3fdnNraq31fee7aR4V7fjoCUYRpICtfTu9ZhJUaksq7QM2FudlWtBDf7zL8YTSeT9ZkFp6Udtisl0VcIOSEK5M262YK5vOC7G0mzQfzNKfyA1uwsOYfoR9tklNRJUBsLHXCU8ZAiAegN5y4KAJYU5ojB+j6BmaqznnASjYHvD/jr37ShZHBfbSF574rjIwoUAm19Tf8YT3JLKGnbrXTMs3g7uZDhZOP/UvVpUpxuCVEn1HIq7vQavNU0S2pRW+PKgK1A1AdXObsXmXmygjPLTTe4jIeAfEEdwebYKwuvufBU5L6Xz3VDpfYcgwq0zX57f9alzjiy8Q/I0=; 25:voqv1RiqcdXnFwq9DQow5xjX/uJIR5lJ+8DJ0htq7Q8Sf9di1HP+hBQ0ByqJemVxLwVkOa6zFcRYQxC+6hv/y4CJADiGcaKblT0E6sULet5EA1CSEqMzV9ob1SBP6Nv1NMZoQlUUr1jJ3+gF4SQBHdavRLDu4/rYE7SKpth5xEibG4OkbkHFddM6lZ2CV1VDeV8cMk5W3AkhynOsi1Cw0D/OMt4+rEtEc/x3o4Z02mQS5yQL9I1TTukUtuMtRqloogavcoQcMAaNmmqt3Bhk8o/Uw3II7hHeQriRIXRFE1eJEfPaKcW1HOLO9U/IIt3Sz6vz+bZoXJjTOWm705+f3g== X-MS-TrafficTypeDiagnostic: DM5PR05MB3177: X-Microsoft-Exchange-Diagnostics: 1; DM5PR05MB3177; 31:0QeWn6rb0lvc5zMd8zWDHBaChfeYKr5mF8lkLelnuMReTHxcgtR31phz4+md5hCP0STPTzlDRRV59iIzh2gl3BI0labjoW5ySkqB8V8Qp01tivdZhaOJ66Lp2vTZ3JFevB6IQordGTGFy9CBWLCTfiBwHCNO2MI9X57OLtJwmwxnvU+mxGZPFAFQfaiIy7NG0Cl0j4E2jKTwsI0s7tfQ6yJrUqjqcM/PTg70a6Xym08=; 20:XsfKwJIa58SS6ueCcGXEYl1U1R500edd7w6EAmSMGzUW9uGxTYrx8j9k7XRVv6l/QeLxs+J3EYwT/1S8Yl3LVfrZFJ9PLg99+4ZVScOQ3wZ9KXnhU1+YZIW8bEwkDATyAix5ygWlQjUpTAJLLL0wraG6957kRY7ks7USDYG5D4L7lJLTWcgmhB3T+G3UFEQAj2ZQRx9jAMUgd66U/ZbLVCdSxBllLy2DCVKbaf7O+h1EkDGXBDKQMjtzcLPJoRkslPFJuzWhrV+ssl0OhuR9PHdTOzkYiqwpMfnOqieqQOaBR3/R1b2yJNiUBnm+WrcoDeilR+qyNwgx0LUJ+0qK7rSc6alo2C+r3ir/NzyGPBs5pGGR31LNGzwvs1VynLnArFa6Jq1f4kbjaUsKYo+EeTR89VH/NxMAKYY80aW9jzdVJ8hGzZ4EfD7Xse5+gMzRS3BouFBmcn5+EFaXiW0GJC/bayVy35dfnjt95wYDeEsFWkj+r9gVWcV9OYvhy0ts X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:(1591387915157); X-MS-Exchange-SenderADCheck: 1 X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3002001)(10201501046)(93006095)(93003095)(3231254)(944501410)(52105095)(6055026)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123562045)(20161123558120)(20161123560045)(6072148)(201708071742011)(7699016); SRVR:DM5PR05MB3177; BCL:0; PCL:0; RULEID:; SRVR:DM5PR05MB3177; X-Microsoft-Exchange-Diagnostics: 1; DM5PR05MB3177; 4:uHCJBDBDvx5nnbL+cQ9iAhHFcGk8kPHDDl+6W3HAyoU2xQwWw3FXhDAUoOLXptPZd8j4K+4eYyzVEa2U8M/muXxKqWibxelyc815CSGDLrHwEpiAVlb3JunoQFUg/cpVhBx9xZGcdv/lRyeANSI7f6zf6SXXm3wP4XPsfhmhB5aMpFtJvHD73XEPaev+WyIOYBj9p3hjRG102YZiyx6DWRE2CuwxxQdml5shkGcWhUFYyJl39dTazbUXOXaqnVwDFI5Zg/fzRDa1gJTTNZcAHRUevmzXmqZlQ3evKiylm9nBtt+fszvrQ79K7ufFNKe3 X-Forefront-PRVS: 0725D9E8D0 X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; DM5PR05MB3177; 23:gqd+7q9UKM+8jSq0PNcFddlBtofmrGXDoyToGxR9j?= =?us-ascii?Q?fLYT56G5alBTokGlfnc4R+RaJ7b23T3ww/FA96gKqrfWuT9c235OQc9KzzRw?= =?us-ascii?Q?vlobowCoX72aqNt0EtowFQrftPyHOmwXOJgXeXqqbA3Fkzwco+nm0cFE8Jxv?= =?us-ascii?Q?qQKlSKzbEkc8RkdfWRFTIx23EN72GymWhiJt8qTluOcZnn2CyZldLpsiwVhH?= =?us-ascii?Q?UXHcbZzXd+RMGhwxgwgTIw9bIGvRr6UWNEKYaXHmlBAz0loG5gPGfk+Nmhmb?= =?us-ascii?Q?ad0ed9tQfPQ9fBA/QtBb3GvhM7qERSbzmVjpJ6zy2DKZx/bDFUXeFHiHub28?= =?us-ascii?Q?4sYKrucRcWxzKIaNqnI5P9Gr7nNH+vvqNdl7QSvnlElLkP05kguRgyVjb3m0?= =?us-ascii?Q?qHfrtVo87xjEex1LQKSerG4BxJiKSInZKE/hngsU1pmAZkpVmM83dBnIxebs?= =?us-ascii?Q?3Zi4ZCtoBVtFm+MqfpgHgb63Hun9fMwhyUoDbe0FX9llCVTo1EqBIiSiOv3J?= =?us-ascii?Q?eErDFcO+HLg7Nc8CmexMwO8CYxmk2j4fLIp74HaJa8zn/lZHptXu3CPtaIOH?= =?us-ascii?Q?1ZEX83lPOx5CIBQsZOD6Eb/XmHve/kFBzo0ONxZiHFK3Lnx2CmUBU1LhbQrU?= =?us-ascii?Q?kPFcxGaa2O/nn6FaQCU6Xk+ByWci5Mh1/cHBGTw/IRxdC04mD9290hbzg/19?= =?us-ascii?Q?serwYDquZJsIEshIXSxUd+mP0Ye8SvrdJmbe2gEgcjT7eV856Jq0w4wbXglK?= =?us-ascii?Q?tXxG5GxzUS1q0GX1uvmFCnP7Nmecpvbw64nwAL1eaUgM9UGOGkOVi2ZRVnJw?= =?us-ascii?Q?/MxxXTFqeegwuVm3/NsmZXw75lyPwb8nJmtShokbXKaPdOaiSjh3b+LD8tGR?= =?us-ascii?Q?Him65Wzq4uuhiRjPQAsN7jPgrZAdd+PEpWDJFC+SYQUaScQgsNsl6TmsLEQK?= =?us-ascii?Q?D7B/uxPnapLIf+g2f6rxmRAl7HFWPpwUrySx+7nuJPDFA7174wUZ6ZK/GMrz?= =?us-ascii?Q?8+jjf7fUcbS1QQOPnAbFnNNbwvb8qPSrm/qlCFq+DSyW4e1/fkfqS56renQs?= =?us-ascii?Q?DKv8YT2NpVQpuIoCYv8jyc3H1qYdRk2Ey2U3o60t57X+MRsMJufi+Kt3ckcv?= =?us-ascii?Q?T06EJTfpioTQjqhnf9QmtCRPo5veUqV0l1zM4YPiQ6TiD5lnJatJOcA/S78c?= =?us-ascii?Q?0lZ/3zph40YQoYG6M07zMkdhRjIFna9qwkKGXwa4J+lWf9docBbtxwa6Kx9f?= =?us-ascii?Q?FpNJ15fg51PVSC+AZ33HeVYBqq2Tb+h6ikaRvxw5SXHSJH+/pd/2bJyfrrEZ?= =?us-ascii?Q?cIyEHrmSwYHwvPBImrUFI8=3D?= X-Microsoft-Antispam-Message-Info: xYe6Ugi7/EYFJOdfZsPYggJFhRBVebdTKeP5/TaOq97kZhT0L6GSm8a2td6g7at2iDs6PFWsCsmgPD/cDIJUtijCQZnHmNGh01SFh/1NR7tTRYxnU8R8njzf/BEGJctj9MDVDKWvifQty0DOJhHi+gPejzWoqPCTv7VQsVqY2q7wTJwL53q9fV7GC6Cf5eLL+AioLQ0EddLk+eLTJ75pOqhGJDxKjXdsVqqCZnFY6uUZEDwBFIZjLU9VwN2W78OCM6Q8aYPesz2cZkIpPukwoWDJpMQxsJ1DweUA/9sZ3FLhierdWoL+B3ChQgjPznltpRU2XAQo5IBg6eruqiE3+kwyR2vVobvpkc2QJyGeGtE= X-Microsoft-Exchange-Diagnostics: 1; DM5PR05MB3177; 6:eiFH541GpP6cu5gh/MKl2CJ295Kiu8s3selaaRuOnR4XO/BiT/ar1huY0V8lRD/Krq8bJupDIqbqZgabQGuuqllsoMPmkbFOzivZ90dSULM3IQSELB+54ZS+4oovUZwMUFTTWiXlqd4RbzDja9QT8a9+iL8f1GOKIwL7nGrD08relNcK10VjZRr3wljHX0ZQWs2nsPRiOiZZNMcKch9tpf+t61G5yoZLtWLL+aSMe93PfhZxcDb0sF7lEFB6J2l9SPGhhRxEa1X/kYEou6vf/xhX+c8sXQjI/sLaUvEU0vfXaCoFXpDZuwPdKSrSJ9G6jWMfQwdNy8KCire8LXSiRGGIcjNbIOA1ipo3r/qkYrx40P1/0VqqV8S98YtpFdFJKdhFzgkMc8v1wMV267JNGOm1cYDsmjshh2Wjg52s75eAMJwK4mcefLByH33Zmq9cCadZoM07P44kdusJnkzpiQ==; 5:q/7QRlwFatyEGqhIaR1XZG0MNG9Mxr13dcn6jELDQ8B95ajHdaEnaLp1gXeAGSI4R5oq44qU5LnqfxTSlbtZYGWqojF0DAi6t4AqXpZYLFeNXHHD0dhuypjtR9YvMENN+lB2GiV4oqEr66php+JkBafehUqC9YbdWjNy8ORpwyo=; 24:noeJhazwiyOm8R6SHVgIBcq7c7AHgu/rZamxVYVnJM0t7iHMp3qpFRAnJYy8CqsUJqS9UrCdKdy12jMdlxxhRLI4dq+qeMuqT2CvMEnDqbM= SpamDiagnosticOutput: 1:99 SpamDiagnosticMetadata: NSPM X-Microsoft-Exchange-Diagnostics: 1; DM5PR05MB3177; 7:vRivBDLAP1GvmipcvQ3J/kwsGpJkgo5hmQHfoBmpDXSp/v4oxGRKtQ7TsPRtDcI7Nu+rZ9xzxVqpNqQMxrion8aJzl65+drx08UYwpiGi1cUM68tCZwsBDsUnqHwnPLDH7lnMxfTBepxDxc205d1FLIoaQRjQrE63GueJeS2Pyp62LWlxDLMLHuB2DRn+hUI9CymXkuGxWmk/ArK7rBSkZZmA3C4QPGXd8FbdT2JUWj7wcltaZeeL4kKPTfBx2z6 X-OriginatorOrg: juniper.net X-MS-Exchange-CrossTenant-OriginalArrivalTime: 06 Jul 2018 21:43:50.7671 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 47c991b9-2b60-4c4d-4759-08d5e3898ff9 X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4 X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.12]; Helo=[P-EXFEND-EQX-01.jnpr.net] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR05MB3177 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-07-06_06:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=2 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=998 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1806210000 definitions=main-1807060243 Archived-At: Subject: Re: [Curdle] I-D Action: draft-ietf-curdle-ssh-ed25519-ed448-01.txt X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jul 2018 21:44:05 -0000 The https://tools.ietf.org/html/draft-ietf-curdle-ssh-ed25519-ed448-01 looks better than the -00 revision. A very minor correction should be the table in section 9 which adds the SSHFP RR Type value 5 for "Ed448" for SSHFP RR Types for public key algorithms. I believe there should be an informative reference to [IANA-SSHFP] https://www.iana.org/assignments/dns-sshfp-rr-parameters/dns-sshfp-rr-parameters.xhtml#dns-sshfp-rr-parameters-1 which is the IANA.ORG parameter table that should be updated. Thank you, -- Mark From nobody Tue Jul 17 10:58:36 2018 Return-Path: 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 D4DC9130E3A for ; Tue, 17 Jul 2018 10:58:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.4 X-Spam-Level: X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 mnBarJZZ7KZY for ; Tue, 17 Jul 2018 10:58:30 -0700 (PDT) Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 323871277D2 for ; Tue, 17 Jul 2018 10:58:30 -0700 (PDT) Received: by mail-lf0-x231.google.com with SMTP id f18-v6so1492122lfc.2 for ; Tue, 17 Jul 2018 10:58:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=uLlMb0uQNkxcxrl16PG9fAyFcnRc9AT1q3uoxze3qns=; b=mVehi2451db0w3T+S1cOeB8CHZ2JN80Qu/HpG6XVreRfg19HaLMw4meaBK7gHpiP7C 85m9YyyMbLbBOe7L+5GLoit36Hxvwq+5Cbnx58K5svVVFmPxkNbbPWlcPc4084XM6o3y U3FCjqVcCyskflzA8vFkguWn2CADDYwkZro10Cb6z4a18JKzBmo+tZfVjQs0x/XcDHej qjiwV7/NvhTP0TrDAXbXrInYqwQ2AorWLRspSW1tURJJVknm586mIlfno5io5+BCifCp ZkAV/DxFlnz4Z7GFkH13xCr0/HwVF82UeBSlNfpLkgwJAbKly9UqAcYPQ8g76Rf1aVJn oTKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=uLlMb0uQNkxcxrl16PG9fAyFcnRc9AT1q3uoxze3qns=; b=AjE56/vz+VVbmFIW06WkG3sMxqgQ0MQlVQj39HFV/+hXZYRJQirQocT2p1YvEPMKfP TLzoiQlHriEviUjYXeqjBupuf2omPZ7sMi/K9MeOZgr/Oi8ycKu6uCGE4G1oxkwxfF7G QJjmnGkmsz1bBFAvk9t2ZpayCq0iGmM63bdM5SCJR2qPsqZQozWg1xVW79PpXZZBQiwd zx0GcC0uFSQTQicr0qlF1C0QVADJlvbVpBA81yc/hiQnCbtdvpoiggCtnjARGQR+1QXf VIJPi96iHt8RC1eb3RQE6Mv9RqvZsq2pLoP73ChZn8USGNV15GZGgLd6Femo0I5cYlTk 3udQ== X-Gm-Message-State: AOUpUlH8q7DSFkCPem6NRD3k2XNzUCx35i8zT0Iuq3ywzCN16TZA5zWw a13zU3IawQORftdrpOJ3K9tmBD+8SZ1k7uTi+IQqsw== X-Google-Smtp-Source: AAOMgpfh9teHjhvoT+kl85GvNamTYYYLsP+M237yRSOiAHmy+q7cvBXkqv5mkl4HDBB8P5HUnjv4j90KLTOgw7qb/eo= X-Received: by 2002:a19:e40d:: with SMTP id b13-v6mr1967147lfh.141.1531850308185; Tue, 17 Jul 2018 10:58:28 -0700 (PDT) MIME-Version: 1.0 Sender: mglt.ietf@gmail.com Received: by 2002:a2e:119d:0:0:0:0:0 with HTTP; Tue, 17 Jul 2018 10:58:27 -0700 (PDT) In-Reply-To: References: From: Daniel Migault Date: Tue, 17 Jul 2018 13:58:27 -0400 X-Google-Sender-Auth: JMQ02QQs5DazkzPgHAnB7bbSaYU Message-ID: To: curdle Content-Type: multipart/alternative; boundary="00000000000077f283057135b18b" Archived-At: Subject: Re: [Curdle] draft-ietf-curdle-rc4-die-die-die-06 review X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jul 2018 17:58:35 -0000 --00000000000077f283057135b18b Content-Type: text/plain; charset="UTF-8" Hi, We would like to thank Loganaden Velvindron for volunteering to co-author and move the draft forward. Yours, Daniel On Fri, Jul 6, 2018 at 5:13 PM, Daniel Migault wrote: > Hi, > > We would like to move the draft to the IESG, however, the draft has not > been updated to address the comments received on the mailing list. We have > privately contacted the author 3 times with the email address provided to > the draft, but we did not receive any response. The purpose of this email > is to first try to contact the author of draft via another channel and > understand if he has any plan to move the draft forward. In addition, we > would also like to see if there is any interest by some members of the > group to co-author the draft and move the draft forward. For those > interested in co-authoring the draft, please contact us privately. > > Our goal is to have all drafts - that is the two remaining drafts in WGLC > - submitted by end of august. > > Yours, > Rich and Daniel > > On Tue, May 15, 2018 at 1:00 PM, Daniel Migault < > daniel.migault@ericsson.com> wrote: > >> Hi, >> >> Please find my review for draft-ietf-curdle-rc4-die-die-die-06 [1]. I >> have also proposed text, so please comment the review in the mail. I am >> willing to start a WGLC as soon as the draft is being updated. >> >> Yours, >> Daniel >> >> >> [1] https://tools.ietf.org/html/draft-ietf-curdle-rc4-die-die-die-06 >> >> >> RFC-Editor: >> >> I personally find the ton of the sentence a bit aggressive, thus I would >> remove it or just leave the RFC reference. >> >> """ >> Non-ASCII characters are allowed in RFCs as per RFC 7997. >> """ >> >> I see deprecation and move to historic status as very similar to >> draft-ietf-curdle-des-des-des-die-die-die-05 and I assume that is >> correct. >> >> Abstract: >> >> The sentence below is a bit hard to parse. >> "" >> and formally obsoletes and moves to >> Historic RFC 4345. >> "" >> >> I would propose instead: >> >> """ >> This document deprecates RC4 in Secure Shell (SSH). Therefore, this >> document updates RFC 4253, and moves to Historic RFC 4345. >> """ >> >> 1. Introduction >> >> >> """ >> RC4 is broken"" >> """ >> >> Although English is not my main language, it sounds a bit abrupt to me >> and it might be preferred to sue something around the lines of >> draft-ietf-curdle-des-des-des-die-die-die-05: >> >> RC4 encryption is steadily weakening in cryptographic strength, and the >> deprecation process should be begun for their use in SSH. >> >> >> It seems to me that sections 1, 2 3 could be merged. I would propose the >> following text. I am providing comments in . >> >> >> >> 1. Introduction >> >> >> The usage of RC4 suites ( also designated as arcfour ) for SSH are >> specified in RFC 4253 and RFC 4345. RFC 4253 specifies the allocation of >> the "arcfour" cipher for SSH. RFC 4345 specifies and allocates the the >> "arcfour-128" and "arcfour-256" ciphers for SSH. >> >> RC4 encryption is steadily weakening in cryptographic strength >> [RFC7457][draft-ietf-curdle-des-des-des-die-die-die-05], and the >> deprecation process should be begun for their use in Secure Shell (SSH) >> [RFC4253]. Accordingly, RFC 4253 is updated to note the deprecation of the >> RC4 ciphers and RFC 4345 is moved to Historic as all ciphers it specifies >> MUST NOT be used. >> >> I believe that this document is very closed to >> [draft-ietf-curdle-des-des-des-die-die-die-05] and as such a reference >> to it should be mentioned. >> >> >> 2. Requirements Notation >> >> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", >> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this >> document are to be interpreted as described in BCP 14 [RFC2119, RFC8174] >> when, and only when, they appear in all capitals, as shown here. >> >> 3. Updates to RFC 4253 >> >> RFC 4253 is updated to prohibit arcfour's use in SSH. >> >> >> """ >> The last sentence of the paragraph on RC4 (called "arcfour" >> in [RFC4253]) in Section 6.3 of [RFC4253] >> """ >> >> I believe that it might be clearer to quote the text as it is not easy to >> locate it. I would propose the text below. >> >> RFC 4253 allocate the "arcfour" cipher in Section 6.3 by defining a list >> of defined ciphers where the "arcfour" cipher appears as optional as >> mentioned below: >> >> """ >> arcfour OPTIONAL the ARCFOUR stream cipher >> with a 128-bit key >> """ >> >> The current document updates the status of the "arcfour" ciphers in the >> list of RFC 4253 Section 6.3 by moving it from OPTIONAL to MUST NOT. >> >> """ >> arcfour MUST NOT the ARCFOUR stream cipher >> with a 128-bit key >> """ >> >> RFC 4253 defines the "arcfour" ciphers with the text mentioned below: >> """ >> The "arcfour" cipher is the Arcfour stream cipher with 128-bit keys. >> The Arcfour cipher is believed to be compatible with the RC4 cipher >> [SCHNEIER]. Arcfour (and RC4) has problems with weak keys, and >> should be used with caution. >> """ >> >> The current document updates RFC 4253 Section 6.3 by replacing th etext >> above with the following text: >> >> """ >> The "arcfour" cipher is the Arcfour stream cipher with 128-bit keys. >> The Arcfour cipher is believed to be compatible with the RC4 cipher >> [SCHNEIER]. Arcfour (and RC4) is steadily weakening in cryptographic >> strength [RFC7457][draft-ietf-curdle-des-des-des-die-die-die-05], and >> MUST NOT be used. >> """ >> >> 4. IANA Considerations >> >> There is a reference to 3DES i think should be removed. In >> addition, IANA cannot be required to update RFCs. IANA is assigned to >> update the SSH registries. With [IANA] being an informational reference to >> https://www.iana.org/assignments/ssh-parameters/ssh-parameters.xhtml, I >> would propose the following text : >> >> The IANA is requested to update the Encryption Algorithm Name Registry >> of the Secure Shell (SSH) Protocol Parameters [IANA]. The Registration >> procedure is IETF Review which is achieved by this document. The registry >> should be updated as follows: >> >> Encryption Algorithm Name Reference Note >> arcfour [RFC-TBD] >> arcfour128 [RFC-TBD] >> arcfour256 [RFC-TBD] >> >> >> Where TBD is the RFC number assigned to the document. >> >> >> >> > --00000000000077f283057135b18b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

We would like to th= ank Loganaden Velvindron for volunteering to co-author and move the draft f= orward.

Yours,
Daniel

On Fri, Jul 6, = 2018 at 5:13 PM, Daniel Migault <daniel.migault@ericsson.com= > wrote:
= Hi,

We would like to move the draft to the IE= SG, however, the draft has not been updated to address the comments receive= d on the mailing list. We have privately contacted the author 3 times with = the email address provided to the draft, but we did not receive any respons= e. The purpose of this email is to first try to contact the author of draft= via another channel and understand if he has any plan to move the draft fo= rward. In addition, we would also like to see if there is any interest by s= ome members of the group to co-author the draft and move the draft forward.= For those interested in co-authoring the draft, please contact us privatel= y.

Our goal is to have all drafts - that is t= he two remaining drafts in WGLC - submitted by end of august.

Yours,
Rich and Daniel

On Tue, May 15, 2018 at 1:00 PM, Daniel Migault <daniel.migault@ericsson.com> wrote:
Hi,

Pleas= e find my review for draft-ietf-curdle-rc4-die-die-die-06 [1]. I have = also proposed text, so please comment the review in the mail. I am willing = to start a WGLC as soon as the draft is being updated.

<= /div>
Yours,
Daniel


RFC= -Editor:

I personally find the ton of the sentence a bit aggressive= , thus I would remove it or just leave the RFC reference.

"&qu= ot;"
Non-ASCII characters are allowed in RFCs as per RFC 7997.
&= quot;""

I see deprecation and move to historic status as v= ery similar to draft-ietf-curdle-des-des-des-die-die-die-05 and I assu= me that is correct.

Abstract:

The sentence below is a bit ha= rd to parse.
""
and formally obsoletes and moves to
=C2= =A0=C2=A0 Historic RFC 4345.
""

I would propose instea= d:

"""
This document deprecates RC4 in Secu= re Shell (SSH).=C2=A0 Therefore, this
=C2=A0=C2=A0 document updates RFC = 4253, and moves to Historic RFC 4345.
"""

1. Intro= duction


"""
RC4 is broken""
"= ;""

Although English is not my main language, it sounds a = bit abrupt to me and it might be preferred to sue something around the line= s of draft-ietf-curdle-des-des-des-die-die-die-05:

RC4 encrypti= on is steadily weakening in cryptographic strength, and the deprecation pro= cess should be begun for their use in SSH.


It seems to me that s= ections 1, 2 3 could be merged. I would propose the following text. I am pr= oviding comments in <mglt></mglt>.



1. Introducti= on


The usage of RC4 suites ( also designated as arcfour ) for SS= H are specified in RFC 4253 and RFC 4345. RFC 4253 specifies the allocation= of the "arcfour" cipher for SSH. RFC 4345 specifies and allocate= s the the "arcfour-128" and "arcfour-256" ciphers for S= SH.

RC4 encryption is steadily weakening in cryptographic strength = [RFC7457][draft-ietf-curdle-des-des-des-die-die-die-05], and the depre= cation process should be begun for their use in Secure Shell (SSH) [RFC4253= ]. Accordingly, RFC 4253 is updated to note the deprecation of the RC4 ciph= ers and RFC 4345 is moved to Historic as all ciphers it specifies MUST NOT = be used.=C2=A0

<mglt>I believe that this document is very clo= sed to [draft-ietf-curdle-des-des-des-die-die-die-05] and as such a re= ference to it should be mentioned. </mglt>


2.=C2=A0 Requir= ements Notation

=C2=A0The key words "MUST", "MUST NOT= ", "REQUIRED", "SHALL", "SHALL NOT", &qu= ot;SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY= ", and "OPTIONAL" in this document are to be interpreted as = described in BCP 14 [RFC2119, RFC8174] when, and only when, they appear in = all capitals, as shown here.

3. Updates to RFC 4253

RFC 4253 = is updated to prohibit arcfour's use in SSH.

<mglt>
&q= uot;""
The last sentence of the paragraph on RC4 (called "= ;arcfour"
=C2=A0=C2=A0 in [RFC4253]) in Section 6.3 of [RFC4253] """

I believe that it might be clearer to quote the= text as it is not easy to locate it. I would propose the text below. </= mglt>

RFC 4253 allocate the "arcfour" cipher in Section= 6.3 by defining a list of defined ciphers where the "arcfour" ci= pher appears as optional as mentioned below:

"""
= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 arcfour=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 OPTIONAL=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 the ARCFOUR stream cipher
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 with a 128-bit ke= y
"""

The current document updates the status of t= he "arcfour" ciphers in the list of RFC 4253 Section 6.3 by movin= g it from OPTIONAL to MUST NOT.

"""
=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 arcfour=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 MUST NOT=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 the A= RCFOUR stream cipher
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 with a 128-bit key
"&= quot;"

RFC 4253 defines the "arcfour" ciphers with th= e text mentioned below:
"""
=C2=A0=C2=A0 The "ar= cfour" cipher is the Arcfour stream cipher with 128-bit keys.
=C2= =A0=C2=A0 The Arcfour cipher is believed to be compatible with the RC4 ciph= er
=C2=A0=C2=A0 [SCHNEIER].=C2=A0 Arcfour (and RC4) has problems with we= ak keys, and
=C2=A0=C2=A0 should be used with caution.
""&q= uot;=C2=A0=C2=A0

The current document updates RFC 4253 Section 6.3 = by replacing th etext above with the following text:

""&qu= ot;
=C2=A0=C2=A0 The "arcfour" cipher is the Arcfour stream ci= pher with 128-bit keys.
=C2=A0=C2=A0 The Arcfour cipher is believed to b= e compatible with the RC4 cipher
=C2=A0=C2=A0 [SCHNEIER].=C2=A0 Arcfour = (and RC4) is steadily weakening in cryptographic strength [RFC7457][draft-i= etf-curdle-des-des-des-die-die-die-05], and
=C2=A0=C2=A0 MUST NOT b= e used.
"""

4. IANA Considerations

<mgl= t>There is a reference to 3DES i think should be removed. In addition, I= ANA cannot be required to update RFCs. IANA is assigned to update the SSH r= egistries. With [IANA] being an informational reference to https://www.iana.org/assignments/ssh-parameters/ssh-param= eters.xhtml,=C2=A0 I would propose the following text :</mglt>
The IANA is requested to update the Encryption Algorithm Name=C2=A0 Re= gistry of the Secure Shell (SSH) Protocol Parameters [IANA]. The Registrati= on procedure is IETF Review which is achieved by this document. The registr= y should be updated as follows:

Encryption Algorithm Name =C2=A0=C2= =A0 =C2=A0Reference =C2=A0=C2=A0 =C2=A0Note
arcfour =C2=A0=C2=A0 =C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 [RFC-TBD] =C2=A0=C2=A0 =C2=A0
arcfour128 = =C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [RFC-TBD] =C2=A0=C2=A0 =C2=A0
arcfo= ur256 =C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [RFC-TBD] =C2=A0=C2=A0 =C2=A0

Where TBD is the RFC number assigned to the document.
=C2=A0




--00000000000077f283057135b18b-- From nobody Wed Jul 18 11:35:39 2018 Return-Path: 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 9E529130F7C for ; Wed, 18 Jul 2018 11:35:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.31 X-Spam-Level: X-Spam-Status: No, score=-4.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 bbk3UYnSd1n4 for ; Wed, 18 Jul 2018 11:35:35 -0700 (PDT) Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (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 04748130F5E for ; Wed, 18 Jul 2018 11:35:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1531938934; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=5xRrIGl3dWNS+dJb34fptesspKcuehMEXqClzYDdaTo=; b=T4+ZHwZ1xkKK8bMbllmuk1mILfPpq9Oq6WcYEGfTfxjnm4MUPSB4CFFLpp9AV8iN +gkBqmBU9Hkz/ObTLeqdEoxcmGVAEQh7bIOAu/Zo0P/Tvp7/ks31SdwzmZnhVtRB D3dI+Qwt5sHaXirhHnuub5a67kIt6ZQdYLJfkUZ1OSc=; X-AuditID: c618062d-bc3ff70000004941-ef-5b4f8876f85b Received: from EUSAAMB501.ericsson.se (Unknown_Domain [147.117.188.214]) by usplmg20.ericsson.net (Symantec Mail Security) with SMTP id B1.E2.18753.6788F4B5; Wed, 18 Jul 2018 20:35:34 +0200 (CEST) Received: from EUSASMB503.ericsson.se (147.117.188.221) by EUSAAMB501.ericsson.se (147.117.188.231) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Wed, 18 Jul 2018 14:35:33 -0400 Received: from EUSASMB503.ericsson.se ([147.117.188.239]) by EUSASMB503.ericsson.se ([147.117.188.239]) with mapi id 15.01.1466.003; Wed, 18 Jul 2018 14:35:33 -0400 From: Daniel Migault To: "'saag@ietf.org'" CC: "curdle-chairs@ietf.org" , "curdle@ietf.org" Thread-Topic: CURDLE WG report Thread-Index: AdQexd0bvXxyG4XPTmOE8XlsSI6pyA== Date: Wed, 18 Jul 2018 18:35:33 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [147.117.188.8] Content-Type: multipart/alternative; boundary="_000_ff00dccda6864ba4b3028953d4af9439ericssoncom_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrFLMWRmVeSWpSXmKPExsUyuXTPNd2yDv9og9mXBCxm9mxgtti6cBaz xZT+TiYHZo8lS34yBTBGcdmkpOZklqUW6dslcGX8nxlUsFm4onnaK6YGxkbBLkZODgkBE4nv jQ2MXYxcHEICxxglni06zQTh/GCUeHfhCzuEs4JRYtPWBnaQFjYBI4m2Q/1gtoiAqkTP3TYW EJtZIEbi5t/pYHFhAUmJZ+8nMUPUyEl8eLyNEcLWk3j+8gwriM0C1PvvzD4mEJtXwFrixLUJ YHMYBcQkvp9awwQxU1zi1pP5TBCnCkgs2XOeGcIWlXj5+B8rhK0o8fn0DaC9HED1yRJnthRD jBSUODnzCcsERuFZSCbNQqiahaQKokRHYsHuT2wQtrbEsoWvmWHsMwceMyGLL2BkX8XIUVpc kJObbmSwiREYI8ck2HR3MN6f7nmIUYCDUYmH93mFf7QQa2JZcWXuIUYJDmYlEd6D7/2ihXhT EiurUovy44tKc1KLDzFKc7AoifOe8eSNEhJITyxJzU5NLUgtgskycXBKNTCeuBtvuMHhUd7W x4l/Z/1IyGMNKeF4HPXeljFy6bRn51qWnZ1n5efGnPhJs+jN+n/dzk+sX63Wz3j06ff7n8Kv u8r+zI0rXjHh6qMX0jlNWxn/xa9PEFqjnfl/JvffvnevL7n+PN1RPZ3dJvhEfkLX//WuMbOU dQ3PTlX7yfK5j/mu1ebdDL/nKLEUZyQaajEXFScCAONLYk6NAgAA Archived-At: Subject: [Curdle] CURDLE WG report X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jul 2018 18:35:38 -0000 --_000_ff00dccda6864ba4b3028953d4af9439ericssoncom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Curdle did not met at IETF102. The WG has two remaining documents that are = in WGLC. All documents are expected to be sent to the IESG in August. Yours, Rich and Daniel --_000_ff00dccda6864ba4b3028953d4af9439ericssoncom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Curdle did not met at IETF102. The WG has two remain= ing documents that are in WGLC. All documents are expected to be sent to th= e IESG in August.

Yours,

Rich and Daniel

--_000_ff00dccda6864ba4b3028953d4af9439ericssoncom_--