Re: [DNSOP] FW: New Version Notification for draft-mglt-dnsop-dnssec-validator-requirements-04.txt

Bob Harold <rharolde@umich.edu> Fri, 07 April 2017 13:51 UTC

Return-Path: <rharolde@umich.edu>
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 1C2951294B7 for <dnsop@ietfa.amsl.com>; Fri, 7 Apr 2017 06:51:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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=umich.edu
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 O_68Xxh7Z_jQ for <dnsop@ietfa.amsl.com>; Fri, 7 Apr 2017 06:51:18 -0700 (PDT)
Received: from mail-yb0-x231.google.com (mail-yb0-x231.google.com [IPv6:2607:f8b0:4002:c09::231]) (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 AE5D11294BE for <dnsop@ietf.org>; Fri, 7 Apr 2017 06:51:08 -0700 (PDT)
Received: by mail-yb0-x231.google.com with SMTP id l201so17200856ybf.0 for <dnsop@ietf.org>; Fri, 07 Apr 2017 06:51:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=google-2016-06-03; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=q8UAO9QtBoh8YEYmDTjFhLwRDJps7oPHwOeTAGxP6PE=; b=Vvf54ptyEccJxLzBo7hHQnV1dFBJq6ZY3eGl+Vp1W6souAwqP5glY/nVXLyC9twLNv FU1j8XgIscXF0mskhCMDBJrYOdsVRE6CLh+M2VyBzF18OOIHbboGqpQdzcb83XYsCoFa xz/Fhugorgv0s0M451MsaCKmbEHpgia4vaYSmK/aRdZQj/oIZzpj4x+H128Y/idveB1N 70KiCn4dfbnDN1/sPJ7SQA5FulUSoCwBdYCj7L4T/jGSdpFij0epL4g/vDJUcjixjFP1 IjGl0gSMRmiEqO1LGGxBEPPs0261KmuyE1YgzDhcEfuKkIAlF7g5jRoWLKTbQbY7XbMH D8vw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=q8UAO9QtBoh8YEYmDTjFhLwRDJps7oPHwOeTAGxP6PE=; b=blo54VwZeT/V1G6SAnUqjXD2K2HcyfuYV/aVVYzVTjqcmFT2OdZVdAMfaYSpRMjpiA /T2W3zaGUveR+YmAy0irOCVQ9RWkk2//CYSat4j9l2bz49Uvmhasb1Dh+DVAt+OUY7SV INwhTkeqV3NRHILa4iYqkHmCwyUFIvMt3ik8rzkUs0NSaYj4PkaQK5/u8N8d4WNZVixQ 41KYr1+Xe3rTPNm7jnHkudaJyFD8fE+z6mB57vi/lXUHeZrlsnvfoyQxFs0StBC2nxz/ kvvNNvbWP5X0FerkjedMLSA4ytpPWJ/nXOlb6CWkQpWZIeyZjCzVe4j1CGFMVwuvzt82 DWgg==
X-Gm-Message-State: AN3rC/75sfRFBz9/rBe9VmRYmUVjBmKBAbfD37yRwnfA+m+E+nAnWnUHv0SL9cX3cqYGIIbr8Jqf5T6C/+BE326s
X-Received: by 10.37.215.140 with SMTP id o134mr7200382ybg.95.1491573067293; Fri, 07 Apr 2017 06:51:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.109.134 with HTTP; Fri, 7 Apr 2017 06:51:06 -0700 (PDT)
In-Reply-To: <2DD56D786E600F45AC6BDE7DA4E8A8C118BB74CA@eusaamb107.ericsson.se>
References: <149062396899.30595.6360166634187605799.idtracker@ietfa.amsl.com> <2DD56D786E600F45AC6BDE7DA4E8A8C118BB74CA@eusaamb107.ericsson.se>
From: Bob Harold <rharolde@umich.edu>
Date: Fri, 7 Apr 2017 09:51:06 -0400
Message-ID: <CA+nkc8C3fwKi5e9ZiNrcuavMGTkR2HQmuzgiyENe1f3JA+hs9Q@mail.gmail.com>
To: Daniel Migault <daniel.migault@ericsson.com>
Cc: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c05c8bed58e6d054c93eac1
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/6fTD9ko8B3fEl83y9M95d-YV0Lo>
Subject: Re: [DNSOP] FW: New Version Notification for draft-mglt-dnsop-dnssec-validator-requirements-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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, 07 Apr 2017 13:51:21 -0000

On Mon, Mar 27, 2017 at 10:16 AM, Daniel Migault <
daniel.migault@ericsson.com> wrote:

> Hi,
>
> Please find an update of our draft on requirements for DNSSEC resolver.
>
> DNS resolvers hardly enable DNSSEC as 1) resolvers are not robust too DNS
> authoritative operations – like KSK roll over, signing errors…. – and 2)
> network administrators have little control on these resolvers to recover
> such situations.
>
> The draft describes how invalid DNSSEC related RRsets may be considered by
> the resolver. The listed requirements aim at designing mechanisms as well
> as interactions with network managers can easily solve/avoid these
> situations. Such mechanisms are expected to encourage DNSSEC deployment on
> resolvers.
>
> Yours,
> Daniel
>
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Monday, March 27, 2017 9:13 AM
> To: Edward Lewis <edward.lewis@icann.org>rg>; Daniel Migault <
> daniel.migault@ericsson.com>gt;; Dan York <york@isoc.org>rg>; york@isoc.org <
> york@isoc.org>
> Subject: New Version Notification for draft-mglt-dnsop-dnssec-
> validator-requirements-04.txt
>
>
> A new version of I-D, draft-mglt-dnsop-dnssec-
> validator-requirements-04.txt
> has been successfully submitted by Daniel Migault and posted to the IETF
> repository.
>
> Name:           draft-mglt-dnsop-dnssec-validator-requirements
> Revision:       04
> Title:          DNSSEC Validators Requirements
> Document date:  2017-03-27
> Group:          Individual Submission
> Pages:          10
> URL:            https://www.ietf.org/internet-drafts/draft-mglt-dnsop-
> dnssec-validator-requirements-04.txt
> Status:         https://datatracker.ietf.org/doc/draft-mglt-dnsop-dnssec-
> validator-requirements/
> Htmlized:       https://tools.ietf.org/html/draft-mglt-dnsop-dnssec-
> validator-requirements-04
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-mglt-dnsop-
> dnssec-validator-requirements-04
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-mglt-dnsop-dnssec-
> validator-requirements-04
>
> Abstract:
>    DNSSEC provides data integrity and authentication for DNSSEC
>    validators.  However, without valid trust anchor(s) and an acceptable
>    value for the current time, DNSSEC validation cannot be performed.
>    This document lists the requirements to be addressed so resolvers can
>    have DNSSEC validation can be always-on.
>

A few minor sugguestions:

 The last part of the abstract
"can have DNSSEC validation can be always-on"
remove the last 'can' to get:
"can have DNSSEC validation be always-on"

2. Introduction Second paragraph ends: "and then most of the communications
relying on the DNS resolution." I would suggest "thus disabling the
communications relying on the DNS resolution."

Fourth paragraph starts:
"The lake of management"
"lake" -> "lack"

Fourth paragraph near end:
"these steps are way to small"
"to" -> "too"
and suggest
"these steps are much too small"

Fifth paragraph
"and additiona mechanism"
try either
"and an additional mechanism"
or
"and additional mechanisms"

8.  Private KSK/ZSK
"split-zone" -> "split-view"

-- 
Bob Harold