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

Eric Rescorla <ekr@rtfm.com> Fri, 19 June 2020 19:06 UTC

Return-Path: <ekr@rtfm.com>
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 03A823A0D91 for <dnsop@ietfa.amsl.com>; Fri, 19 Jun 2020 12:06:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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 (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 nqTEA5blXnYF for <dnsop@ietfa.amsl.com>; Fri, 19 Jun 2020 12:06:23 -0700 (PDT)
Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (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 DFF083A0AF1 for <dnsop@ietf.org>; Fri, 19 Jun 2020 12:06:22 -0700 (PDT)
Received: by mail-lj1-x22b.google.com with SMTP id y11so12707606ljm.9 for <dnsop@ietf.org>; Fri, 19 Jun 2020 12:06:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1+gLvLeqSwuyUJdevXmR48RNeX+geRFJ81lhCvL++88=; b=USxek5AXvKqbmyzv/ML5zRUxHMZZ3dJofStctMimXDQ5qIfbhmsS3I8F6uhUiT/TVk B2Doq3LoO+YdgWRbDnT3xob6OQUrmoSlAPGbuD0RzC5/w/3H98HWmMOGxgJzsc0/IKiu j3AlgSjFGzdd+ICIcdhr1ShHybUEFfbAkapxuG/fCPises8uzOzwgxtZCpqufwATx9FO ssz0RNTMPCq2MfTJ4EVDg/HzyT2aHlfNKBjsWf/tbMFVEnbsVYjUN8zig1mb2PT/iUyd IzqRXaqz1GtKVk73FzgpgHh8ZYoZ7++490aFTifOA/lYhpPxDcYmrYOdNeQNFFzGhwO8 iJJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1+gLvLeqSwuyUJdevXmR48RNeX+geRFJ81lhCvL++88=; b=c+44uZY3j5RlqqiWnNj9yGEfZh7U+ksYbYg3FUu/JCcB0RtfLf63MGmB6Z/DiMNTZi VmiKFblF9g3PlWHFKa8VSo4Ka+qJWztNgcoh4v1eCs1R/bSMBgqgK+4n1FXC5gJM+l+I ccTN5fkVBumMp5i6bFwkVHCNlYw5xNZWv1JFnmJZCENO4Z6/9eifudDqtg/z2PyDrwPT fk9ilcKFJgtQh2zuiRGFaHW/gBuRPfihqJWnYpZiaVstiSnOlvJLuyT2BWhkXSh27GsJ SKw5CbJp5n6AN/eW4hLy/VS5ddWpM3yzG8cpigZZ8hOCdTLmOovLPi0MnUND5wsJuxEw 5EYQ==
X-Gm-Message-State: AOAM532jYu5Siu8A5cFwaRVTLI8vEDL8k7gkxeYfmtKzi9eYLtK704od MxXL6GsO3nMTyVXmBXVvw8nTuvV5O1COd/J9DyVHnWvVqBI=
X-Google-Smtp-Source: ABdhPJyf6VBe941FyQ2FLnUJPRbtOKK2PZHFY4erYgO6u7dh02gD5ht65eFVKRt+o6L0TDw8/It0J9qdlMHFMkX7EDI=
X-Received: by 2002:a2e:9d98:: with SMTP id c24mr2322605ljj.17.1592593580999; Fri, 19 Jun 2020 12:06:20 -0700 (PDT)
MIME-Version: 1.0
References: <CABcZeBNT9Wf2HxLDHR=tLod4YVgF-E=uaU7+=9nGLk=01gDOXg@mail.gmail.com> <20200619183914.BC2B61B36D16@ary.qy>
In-Reply-To: <20200619183914.BC2B61B36D16@ary.qy>
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 19 Jun 2020 12:05:44 -0700
Message-ID: <CABcZeBO3OaJgt1Ub4rz2tUQ1T4oaMkba3Yz-Y5OKQo1AOPS5VQ@mail.gmail.com>
To: John Levine <johnl@taugh.com>
Cc: dnsop WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000aad8e105a8749673"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ivpWXYF1qEitxlkV5D3gkgjhoqs>
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: Fri, 19 Jun 2020 19:06:25 -0000

On Fri, Jun 19, 2020 at 11:39 AM John Levine <johnl@taugh.com> wrote:

> In article <CABcZeBNT9Wf2HxLDHR=tLod4YVgF-E=uaU7+=9nGLk=
> 01gDOXg@mail.gmail.com> you write:
> >> Yes. Leveraging the fact that the IETF community is in fact a community
> >> seems worth the effort to have the references in registries be useful
> to a
> >> new developer a decade in the future.
> >
> >OK. In that case you and I disagree.
> >
> >My reasoning is that (as above) these algorithms are generally of low
> >interest and that requiring community review for code point registration
> >has the result of consuming quite scarce resources in the service of
> making
> >the algorithms which are being registered marginally clearer. ...
>
> Sounds like expert review would be more appropriate, so only one
> person has to spend cycles deciding whether the spec looks plausible.
>

As I said, even that turns out to be quite a bit of work, depending on what
you think "plausible" means. If you review for "there appears to be
something vaguely formatted like a spec at this location", then sure. If
you mean "is this implementable", let alone secure, then it's pretty far
from easy.

-Ekr

>
> R's,
> John
>