Re: [DNSOP] Working Group Last Call for: draft-ietf-dnsop-algorithm-update

Ondřej Surý <ondrej@isc.org> Sun, 14 October 2018 12:16 UTC

Return-Path: <ondrej@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1C471293FB for <dnsop@ietfa.amsl.com>; Sun, 14 Oct 2018 05:16:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.922
X-Spam-Level:
X-Spam-Status: No, score=-5.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_EXCESS_BASE64=0.979, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 xIJzIxxfxIZh for <dnsop@ietfa.amsl.com>; Sun, 14 Oct 2018 05:16:00 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 B33FD128CB7 for <dnsop@ietf.org>; Sun, 14 Oct 2018 05:16:00 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 7875D3AB03B; Sun, 14 Oct 2018 12:16:00 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 49DBD160052; Sun, 14 Oct 2018 12:16:00 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 12CAF160068; Sun, 14 Oct 2018 12:16:00 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id lEmBLRJ9zi9m; Sun, 14 Oct 2018 12:15:59 +0000 (UTC)
Received: from [IPv6:2001:67c:64:49:9c3f:7ea6:5645:acd8] (nat64pool-31-240.ripemtg.ripe.net [193.0.31.240]) by zmx1.isc.org (Postfix) with ESMTPSA id 2BE3E160052; Sun, 14 Oct 2018 12:15:59 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.1 \(3445.100.42\))
From: =?utf-8?B?T25kxZllaiBTdXLDvQ==?= <ondrej@isc.org>
In-Reply-To: <CAOp4FwQOEBKzdJfjUo8WcpA-Jecp26APXbuQC8fBTM+GoOLwsw@mail.gmail.com>
Date: Sun, 14 Oct 2018 14:15:56 +0200
Cc: Tim Wicinski <tjw.ietf@gmail.com>, dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <E6CA4E6B-E4A1-4E39-BDCD-ECC2C58A3A86@isc.org>
References: <CADyWQ+GqybVhe6c-L_LyFB4wQPxOhOfMy_uwv46nSc2Y5-7FEQ@mail.gmail.com> <CAOp4FwQOEBKzdJfjUo8WcpA-Jecp26APXbuQC8fBTM+GoOLwsw@mail.gmail.com>
To: Loganaden Velvindron <loganaden@gmail.com>
X-Mailer: Apple Mail (2.3445.100.42)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ekw0MhBmjmLP2Ccbpln3t-Ebgcw>
Subject: Re: [DNSOP] Working Group Last Call for: draft-ietf-dnsop-algorithm-update
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Oct 2018 12:16:03 -0000

Hi Loganaden,

while I understand what you are asking for, I don’t understand how it would improve the document.

IETF RFCs are static and if we include any current “numbers” they quickly become invalid.  Adding figures to the document doesn’t improve readability or the content.  While it would support the claims we make in the document I feel that the consensus process IETF have is just fine for giving the content enough validity, and we don’t have to support every claim we make in the document with figures.

Ondrej
--
Ondřej Surý
ondrej@isc.org

> On 2 Oct 2018, at 15:40, Loganaden Velvindron <loganaden@gmail.com>; wrote:
> 
> On Tue, Oct 2, 2018 at 4:51 PM Tim Wicinski <tjw.ietf@gmail.com>; wrote:
>> 
>> 
>> The chairs and the authors of this document feel that the
>> document is in solid shape to proceed to WGLC.
>> 
>> 
>> This starts a Working Group Last Call for draft-ietf-dnsop-algorithm-update
>> 
>> Current versions of the draft is available here:
>> https://datatracker.ietf.org/doc/draft-ietf-dnsop-algorithm-update/
>> 
> 
> Section 3.1.
> 
> "
> RSASHA1 and RSASHA1-NSEC3-SHA1 are widely deployed, although zones
>   deploying it are recommended to switch to ECDSAP256SHA256 as there is
>   an industry-wide trend to move to elliptic curve cryptography.
> "
> 
> And also this paragraph:
> "
> 
> RSASHA256 is in wide use and considered strong.
> 
> "
> 
> My suggestion would be to include figures or at minimum a reference.
> There is a document from ISOC with 3 tables where there is an analysis
> of deployment DNSSEC worldwide.
> 
> https://www.internetsociety.org/wp-content/uploads/2017/08/ISOC-State-of-DNSSEC-Deployment-2016-v1.pdf,
> Page 23 & Page 24.
> 
> 
>> The Current Intended Status of this document is: Proposed Standard
>> 
>> Please review the draft and offer relevant comments.
>> If this does not seem appropriate please speak out.
>> If someone feels the document is *not* ready for publication, please speak out with your reasons.
>> 
>> This starts a two week Working Group Last Call process, and ends on:  16 October 2018
>> 
>> thanks
>> tim
>> 
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop