Re: [DNSOP] [Ext] Call for Adoption: draft-belyavskiy-rfc5933-bis

Joe Abley <jabley@hopcount.ca> Thu, 18 June 2020 15:01 UTC

Return-Path: <jabley@hopcount.ca>
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 509F53A1390 for <dnsop@ietfa.amsl.com>; Thu, 18 Jun 2020 08:01:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 D4h40fy4Q4Xo for <dnsop@ietfa.amsl.com>; Thu, 18 Jun 2020 08:01:46 -0700 (PDT)
Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (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 1868D3A12D4 for <dnsop@ietf.org>; Thu, 18 Jun 2020 08:01:15 -0700 (PDT)
Received: by mail-ej1-x633.google.com with SMTP id l27so6793148ejc.1 for <dnsop@ietf.org>; Thu, 18 Jun 2020 08:01:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=SKrx0gvJ6DVLuNiMknKhJIYTTs3/yWePw86VBKkIbYQ=; b=Oz9sqAPkyInMTBuuGr8L5huxt0IG2ThZvZ9vfCakU2pyGzh5RXs3iCJrufb5w3px3X k7LEvlRilBE4fJ2UoYO8b+diIBpMBn/+0t8b647HcKtnlrgN2Ua1AeKzjwOTrMYncq5i 7Mys/qoEwMf5dwmKcaLSDL7CPRtm6iU+LglI8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=SKrx0gvJ6DVLuNiMknKhJIYTTs3/yWePw86VBKkIbYQ=; b=cZE8IngfTr9mut2KInlbxLQTmO1kTb8oK7WxuGaoHdaxyeYtgy7BmyM9Bp3x3A+tBt LS4Z5CeeXMzRlK7z7BVJonh5Tz+zFGrEinrddvt29Nba81oTXwDk/1bbQgqy8dORiUAc P7rxjGez64Zigc03hgkgEYbtxUw7ytPVoQAWHZxApNIjlh2JOOik1E43wPaSSv8IeRM1 h0SHWWn10+pLUW8spX9lPBlc5sFyjtjcacn/xE19QYzQ6w7OqP5Uxy72EvNZrOJvQeYL yo4Ip5vAzT1N3kj8X+Gqm1K6jMMoUyPF3yHszbZTwNtdQ6ZAicgekYwZwZi3kVjNFbwc Tq8w==
X-Gm-Message-State: AOAM531zQsS7g9HrJ/sjufwIylxYdpTElc7unO7lfCBl8B9YydKgDfz1 GLqdhVLHu1TNDzfInY5MFKhNAiF4r/E=
X-Google-Smtp-Source: ABdhPJzqiG3cy61ve2dKZDNUH3+6iO87Of8SWJhCrS7wvmbIXndMRKUjU7HfbZ2SU4kMzXagYn/6hw==
X-Received: by 2002:a17:906:971a:: with SMTP id k26mr4125164ejx.230.1592492472528; Thu, 18 Jun 2020 08:01:12 -0700 (PDT)
Received: from ?IPv6:2001:980:6aad:1:78ee:ee00:b03:427e? ([2001:980:6aad:1:78ee:ee00:b03:427e]) by smtp.gmail.com with ESMTPSA id y18sm2329427edu.76.2020.06.18.08.01.11 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 18 Jun 2020 08:01:11 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Joe Abley <jabley@hopcount.ca>
Mime-Version: 1.0 (1.0)
Date: Thu, 18 Jun 2020 17:01:03 +0200
Message-Id: <F4857DCC-D623-41A5-8B02-575A0FBE3D1A@hopcount.ca>
References: <C2C9BDB4-AA7B-47B8-8735-2A529B37B4BA@icann.org>
Cc: dnsop WG <dnsop@ietf.org>
In-Reply-To: <C2C9BDB4-AA7B-47B8-8735-2A529B37B4BA@icann.org>
To: Paul Hoffman <paul.hoffman@icann.org>
X-Mailer: iPad Mail (17F80)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/bOJBxQ0dcmTiS-q_3Nqw9rpyzJE>
Subject: Re: [DNSOP] [Ext] Call for Adoption: draft-belyavskiy-rfc5933-bis
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: Thu, 18 Jun 2020 15:01:53 -0000

On Jun 18, 2020, at 16:48, Paul Hoffman <paul.hoffman@icann.org> wrote:

> Why is this WG considering making this document Standards Track instead of Informational? Also, why is the WG considering putting the document in our work stream at all? Can the WG can bring much value to the document itself? We do have lots of other things we are working on.

I think the question of the value the wg can bring is the important one.

In this case it seems unlikely that dnsop has the expertise to review this document to the depths of the crypto. The degree to which the advice for DNSSEC implementers is clear and unambiguous can surely be assessed without putting it through the working group machinery.

An individual submission will still require conflict review by the IESG and that will involve credible DNS people to express an opinion, so there will no doubt be some familiar faces from dnsop that are still involved in an individual capacity, but I think (as I think Paul infers above) that there is little benefit to adding this to the workload of the wg chairs and AD if we don't expect the document to benefit from corresponding levels of improvement.

For what it's worth if this was to proceed on the individual submission stream and if the authors needed independent reviewers to express an opinion as part of that process I'd happily put my hand up with a DNS perspective. I almost certainly can't help with the crypto.

The question of how dnsop tracks algorithms that exist and whether they are recommended or not is reasonably separate from whether this document should be published, I think.


Joe