Re: [DNSOP] I-D Action: draft-ietf-dnsop-algorithm-update-03.txt

Dick Franks <rwfranks@acm.org> Tue, 23 October 2018 20:38 UTC

Return-Path: <rwfranks@gmail.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 133D71277C8 for <dnsop@ietfa.amsl.com>; Tue, 23 Oct 2018 13:38:11 -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, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 etooqn5dk0A1 for <dnsop@ietfa.amsl.com>; Tue, 23 Oct 2018 13:38:09 -0700 (PDT)
Received: from mail-wr1-f54.google.com (mail-wr1-f54.google.com [209.85.221.54]) (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 5D62F12008A for <dnsop@ietf.org>; Tue, 23 Oct 2018 13:38:09 -0700 (PDT)
Received: by mail-wr1-f54.google.com with SMTP id i4-v6so3121868wrr.13 for <dnsop@ietf.org>; Tue, 23 Oct 2018 13:38:09 -0700 (PDT)
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=sfPKbs5HDU4742q/CEmysH/mNjXm/GHBansUrQpImuw=; b=XxA4Z/5mgidQE1Lfqz2aMeDJzqRRX1CAdHJWdII2orY3vS613/7I17lYoqbme0PGZU xbs193mot781M8gz9+m1erklpzrl2kno93RL20/4hZCpBBw8jib4pCO0uQNtkYwFk+7e uqh0QRNCxLZZ8QFQZ4JCpJH54Sgj6TMSsLOK1Yo7Z8So8l2s6uU+2aJfMZk7B0eICy0s +9XzPX3337VNxtxVk417kzJOHYkxlExrqjd7WBmf5GSVVMWN6sdThYgXx2JwzaTymqoo sQMhiyWUOW/iKfyhPE4DMt/BFHcz/ZIlnQniHkbsGv674SbyG9+ywscgwQxPT3njOZqp eHHw==
X-Gm-Message-State: ABuFfoh/kinkkN+bNEuly/96mhZCaC6NyF0KNq0sMwbqwjhvGgb0j+CT CD1KXh6WtOlbBHNHK8ok3Si4GgSBkYANQZIq7CA=
X-Google-Smtp-Source: ACcGV63DqQq14ox2rdJbj+7Qj+UL/GOdRjrFRfJ7f5a+Fl5APZDv3YpmMuU4gj7ygfZSxe+2GiRPy3WcwhZGV9Oz9Gc=
X-Received: by 2002:adf:80c7:: with SMTP id 65-v6mr51522103wrl.57.1540327087778; Tue, 23 Oct 2018 13:38:07 -0700 (PDT)
MIME-Version: 1.0
References: <154031719651.31281.7278063213758534340@ietfa.amsl.com> <2AF9FBC4-8552-4B47-BC33-8D78FE92A734@isc.org> <CADyWQ+EGXFLM_8UX1mDv9mY1Jtiz=amutidxtM5t-cSYY4HgKw@mail.gmail.com>
In-Reply-To: <CADyWQ+EGXFLM_8UX1mDv9mY1Jtiz=amutidxtM5t-cSYY4HgKw@mail.gmail.com>
From: Dick Franks <rwfranks@acm.org>
Date: Tue, 23 Oct 2018 21:37:30 +0100
Message-ID: <CAKW6Ri6f+9OUKa_cJN4zWkgOepwbuJo4WbBi8FGJscP=X8rmZw@mail.gmail.com>
To: tjw ietf <tjw.ietf@gmail.com>
Cc: =?UTF-8?B?T25kxZllaiBTdXLDvQ==?= <ondrej@isc.org>, IETF DNSOP WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e7b5d10578eb58a4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/EcHLxrXDWDtCID0gBv7CLM3cx0U>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-algorithm-update-03.txt
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: Tue, 23 Oct 2018 20:38:11 -0000

On Tue, 23 Oct 2018 at 19:34, Tim Wicinski <tjw.ietf@gmail.com> wrote:

The WGLC has completed and we were waiting on the authors on addressing all
> comments and updating their document.
> The chairs feel this is ready to proceed.
>

Just spotted a fumble with document references in section 3.1 which will
need to be fixed before this is put to bed.

[3.1, para 6] reads:

   ECC-GOST (GOST R 34.11-94) has been superseded by GOST R 34.11-2012
   in [RFC6986 <https://tools.ietf.org/html/rfc6986>].  The GOST R
34.11-2012 hasn't been standardized for use
   in DNSSEC.

should read:

   ECC-GOST (GOST R 34.10-2001) has been superseded by GOST R 34.10-2012
   in [RFC7091 <https://tools.ietf.org/html/rfc7091>].  The GOST R
34.10-2012 hasn't been standardized for use
   in DNSSEC.


I apologise for not having noticed this earlier.


-- Dick



DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>