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

Daniel Migault <daniel.migault@ericsson.com> Thu, 13 April 2017 18:32 UTC

Return-Path: <mglt.ietf@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 62F3A1315A6 for <dnsop@ietfa.amsl.com>; Thu, 13 Apr 2017 11:32:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Level:
X-Spam-Status: No, score=-2.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=gmail.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 zU6xU2b8RT_e for <dnsop@ietfa.amsl.com>; Thu, 13 Apr 2017 11:32:31 -0700 (PDT)
Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (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 4C47C1315BF for <dnsop@ietf.org>; Thu, 13 Apr 2017 11:32:29 -0700 (PDT)
Received: by mail-lf0-x22d.google.com with SMTP id s141so33638501lfe.3 for <dnsop@ietf.org>; Thu, 13 Apr 2017 11:32:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=FC5wA7Nmv/m6ixbK89whvB4NF0RwSM4KwRHgd/x3IMk=; b=PDKclXmq1ouxuny9oCoiVN42foyOyVh0FbeAkh3OL5S9tqsdDB3z0IkDE+4X/TdcuK +bd3pWH+eeRuf7Y8tg6AfLxAGsBWvPWaalFvMzNy/ZyOxtwucYVg8GmsEPuBmsBR4BBC IVBTtuYG70BO7Co6RemrTnw0nJ8td6rI1sMs4/tv4cHUy0jiUZjmszBnI7p8ODFQB20e MDz1QcqATyoDTNDObYhIzRjMBUUy3Qh45ctvS9+m9s/aiB0UQH1HvuySOYSfoMvhlWEd rP8387y+4Yzg2m89ZcOcDonWZdXrvebbXaLZFT5ABVUVdCK58q/06afl6nwIKI9KvvSd PS5w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=FC5wA7Nmv/m6ixbK89whvB4NF0RwSM4KwRHgd/x3IMk=; b=mg5zn9SkD4UhIzpjs1H+3drlJrqWB7uXHeaATFBkNHm6Zv2ergSwU+GHCp/t3uYqm4 /88EhkzvMXuZZrvEK0WCuuJYakqPN5r8JIASQMVvb0NI7+0629ztZ/t4t36ij8oOda4w U0RTTr8eMSvV98tGEzoexpBxx6p1Kt5ehnjf+h80H8pDqj2ObvKAtCQBH1k0v4O0CyfQ ICIqvfgGAG3Emk8j2WtZ9Un9K4Lf8ADVdYqvPRuHktVokqwCFqVQ7QlalQeHkrQgfvm7 7PpVTlIEGx/oPs1zh9WhLtZhpe0l7t/1KDsFFKAzG74qOwJtrf2nVmfY6ZfI8zWCLYKP /QGQ==
X-Gm-Message-State: AN3rC/6dbvpVnH2U8+IMOpOiCOoYsyujh3X4CjSbaI5lYCkTs6zLCSIe RWZHLvSmBynj/L1iLb/tL/NAk1izxw==
X-Received: by 10.25.23.32 with SMTP id n32mr1463492lfi.142.1492108347519; Thu, 13 Apr 2017 11:32:27 -0700 (PDT)
MIME-Version: 1.0
Sender: mglt.ietf@gmail.com
Received: by 10.46.69.85 with HTTP; Thu, 13 Apr 2017 11:32:26 -0700 (PDT)
In-Reply-To: <CADZyTkn3=9tzm0oS4=OM1R4XYjH+YohsrxPFc+5HTi6QT=BrUA@mail.gmail.com>
References: <149062396899.30595.6360166634187605799.idtracker@ietfa.amsl.com> <2DD56D786E600F45AC6BDE7DA4E8A8C118BB74CA@eusaamb107.ericsson.se> <CA+nkc8C3fwKi5e9ZiNrcuavMGTkR2HQmuzgiyENe1f3JA+hs9Q@mail.gmail.com> <CADZyTkn3=9tzm0oS4=OM1R4XYjH+YohsrxPFc+5HTi6QT=BrUA@mail.gmail.com>
From: Daniel Migault <daniel.migault@ericsson.com>
Date: Thu, 13 Apr 2017 14:32:26 -0400
X-Google-Sender-Auth: 0A0EzO_6BxS9GoYeXOWCcX1RqwI
Message-ID: <CADZyTkmyhRV0avfjZRXkUimK1vZMK-p8spZEsSqXQtZZj5fruw@mail.gmail.com>
To: Bob Harold <rharolde@umich.edu>
Cc: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary=001a114058060576e7054d108c8f
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Xb79oXz9lgQNPNFdl3-mcO3mnW8>
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: Thu, 13 Apr 2017 18:32:34 -0000

Hi Bob,

Thanks you for the clarifications, I have updated my local copy with all
your comments.

Yours,
Daniel

[1]
https://github.com/mglt/draft-mglt-dnsop-dnssec-validator-requirements/blob/master/draft-mglt-dnsop-dnssec-validator-requirements.xml

On Fri, Apr 7, 2017 at 7:35 PM, Daniel Migault <daniel.migault@ericsson.com>
wrote:

> Thanks for the review, I will update the copy on the git accordingly.
>
> Yours,
> Daniel
>
> On Fri, Apr 7, 2017 at 9:51 AM, Bob Harold <rharolde@umich.edu> wrote:
>
>>
>> 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-valida
>>> tor-requirements-04.txt
>>>
>>>
>>> A new version of I-D, draft-mglt-dnsop-dnssec-valida
>>> tor-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/d
>>> raft-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
>>
>>
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
>>
>>
>