Re: [DNSOP] Last Call: <draft-ietf-dnsop-algorithm-update-05.txt> (Algorithm Implementation Requirements and Usage Guidance for DNSSEC) to Proposed Standard

Paul Wouters <pwouters@redhat.com> Tue, 05 March 2019 01:06 UTC

Return-Path: <pwouters@redhat.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 06D39124BAA for <dnsop@ietfa.amsl.com>; Mon, 4 Mar 2019 17:06:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 FaB-KLYJ8tYg for <dnsop@ietfa.amsl.com>; Mon, 4 Mar 2019 17:06:22 -0800 (PST)
Received: from mail-lj1-f172.google.com (mail-lj1-f172.google.com [209.85.208.172]) (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 0DD9812008F for <dnsop@ietf.org>; Mon, 4 Mar 2019 17:06:22 -0800 (PST)
Received: by mail-lj1-f172.google.com with SMTP id v10so6047326lji.3 for <dnsop@ietf.org>; Mon, 04 Mar 2019 17:06:21 -0800 (PST)
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=VzeYo7ZtLWei5XJDMJm2DL6LJCjr4FY/9tQbVeoHgNY=; b=gjNLCnZUsH2KJgjqkZ1AWVwjLauBEHk94mtzEA9W7dH8ZBQgbu2z7MqpPBa4DQE2VD hijRM7Pyn3HDInYJayAUZi2EbMFgXYmnr4Pxb1oSSue68QquDFJihi4H5dsxYfnM6Siy Fn4bARVmFYGYN4tV8AgEAItZnH7oAJYEclxZNYu8qtsLu1o3R9+0PbYWocwvad+I6aNA UeiIxYDkuhUVbb786QxWQjk4bxF0RT/PrOISbGHia50kAb+Pq8UPtn4RzrK4z92v496z yfvy52zS8ttHp1MFi8HYo4X1ad9yC0PEu0+iNhDviUuIO6i8nbgkCqcIl/hyH5JyMU4H vv0A==
X-Gm-Message-State: APjAAAUYux/DoW+StuNqqlyAJjuhnPquJ/0E8t2y90K3IdTmAVQCTUD9 imE8AtQSSvOJP8gggmwrY3EJ7UXqnpFUblJh63RUOQ==
X-Google-Smtp-Source: APXvYqyYinbt5L61RKxDHvai73LcahcG2cS92D4tu3HXiAhSSRzsJu3d08gNHD3R5pSN8OPbWZmnXl7JG/GB0l34dVs=
X-Received: by 2002:a2e:85d2:: with SMTP id h18mr7662748ljj.69.1551747979894; Mon, 04 Mar 2019 17:06:19 -0800 (PST)
MIME-Version: 1.0
References: <155008617010.9548.7174990317415826094.idtracker@ietfa.amsl.com> <24677ff5-b1e2-3aaa-9f26-216c8265d890@brokendns.net>
In-Reply-To: <24677ff5-b1e2-3aaa-9f26-216c8265d890@brokendns.net>
From: Paul Wouters <pwouters@redhat.com>
Date: Mon, 4 Mar 2019 20:06:09 -0500
Message-ID: <CAAQVWxEjwGVL6EWz8vi5kR6KuNp9wtqEC=g6V6+qmgPT_3ddVw@mail.gmail.com>
To: Michael Sinatra <michael@brokendns.net>
Cc: ietf@ietf.org, Tim Wicinski <tjw.ietf@gmail.com>, draft-ietf-dnsop-algorithm-update@ietf.org, dnsop@ietf.org, dnsop-chairs@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001f7a8c05834e7b6c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Bu8luDM4RIkgxtoy13slLcy1lvo>
Subject: Re: [DNSOP] Last Call: <draft-ietf-dnsop-algorithm-update-05.txt> (Algorithm Implementation Requirements and Usage Guidance for DNSSEC) to Proposed Standard
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, 05 Mar 2019 01:06:26 -0000

Ah yes. "imminent" was a reminder of their commitment to volunteer to give
feedback :)

If we do another rev as a result of this call, I'll remove it. Otherwise,
I'll leave a note with the RFC Editor to do so.

Paul

On Mon, Mar 4, 2019 at 7:40 PM Michael Sinatra <michael@brokendns.net>
wrote:

> Section 8 - Acknowledgements:
>
> "We wish to thank Michael Sinatra, Roland van Rijswijk-Deij, Olafur
> Gudmundsson, Paul Hoffman and Evan Hunt for their imminent feedback."
>
> Paraphrasing one of my colleagues, is the part about "imminent feedback"
> a prediction, or a hint that we are supposed to give more feedback? :-)
>
> My most imminent feedback--right now--is that I think the language in
> Section 3 has come together really nicely and does a good job of
> informing operators of the trade-offs of using the different algorithms,
> and it provides good recommendations.  I certainly support advancing it.
>
> michael
>
> On 2/13/19 11:29 AM, The IESG wrote:
> >
> > The IESG has received a request from the Domain Name System Operations WG
> > (dnsop) to consider the following document: - 'Algorithm Implementation
> > Requirements and Usage Guidance for DNSSEC'
> >   <draft-ietf-dnsop-algorithm-update-05.txt> as Proposed Standard
> >
> > The IESG plans to make a decision in the next few weeks, and solicits
> final
> > comments on this action. Please send substantive comments to the
> > ietf@ietf.org mailing lists by 2019-02-27. Exceptionally, comments may
> be
> > sent to iesg@ietf.org instead. In either case, please retain the
> beginning of
> > the Subject line to allow automated sorting.
> >
> > Abstract
> >
> >
> >    The DNSSEC protocol makes use of various cryptographic algorithms in
> >    order to provide authentication of DNS data and proof of non-
> >    existence.  To ensure interoperability between DNS resolvers and DNS
> >    authoritative servers, it is necessary to specify a set of algorithm
> >    implementation requirements and usage guidelines to ensure that there
> >    is at least one algorithm that all implementations support.  This
> >    document defines the current algorithm implementation requirements
> >    and usage guidance for DNSSEC.  This document obsoletes [RFC6944].
> >
> >
> >
> >
> > The file can be obtained via
> > https://datatracker.ietf.org/doc/draft-ietf-dnsop-algorithm-update/
> >
> > IESG discussion can be tracked via
> >
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-algorithm-update/ballot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >
> >
> >
> > _______________________________________________
> > DNSOP mailing list
> > DNSOP@ietf.org
> > https://www.ietf.org/mailman/listinfo/dnsop
> >
>