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

From: Bob Harold <[email-masked]>
Date: Wed, 12 Jul 2017 09:38:05 -0400

On Wed, Jun 28, 2017 at 6:13 AM, Daniel Migault <[email-masked]
> wrote:

> Hi,
>
> Please find a new version for the DNSSEC validators requirements. Our
> understanding is that the current version has considered all received
> comments.
>
> We appreciate your comments and feed backs.
>
> Yours,
> Daniel
>
> -----Original Message-----
> From: [email-masked] [mailto:[email-masked]]
> Sent: Wednesday, June 28, 2017 11:46 AM
> To: Edward Lewis <[email-masked]>; Daniel Migault <
> [email-masked]>; Dan York <[email-masked]>; [email-masked] <
> [email-masked]>
> Subject: New Version Notification for draft-mglt-dnsop-dnssec-valida
> tor-requirements-05.txt
>
>
> A new version of I-D, draft-mglt-dnsop-dnssec-valida
> tor-requirements-05.txt
> has been successfully submitted by Daniel Migault and posted to the IETF
> repository.
>
> Name:           draft-mglt-dnsop-dnssec-validator-requirements
> Revision:       05
> Title:          DNSSEC Validators Requirements
> Document date:  2017-06-27
> Group:          Individual Submission
> Pages:          13
> URL:            https://www.ietf.org/internet-
> drafts/draft-mglt-dnsop-dnssec-validator-requirements-05.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-05
> Htmlized:       https://datatracker.ietf.org/
> doc/html/draft-mglt-dnsop-dnssec-validator-requirements-05
> Diff:           https://www.ietf.org/rfcdiff?
> url2=draft-mglt-dnsop-dnssec-validator-requirements-05
>
> Abstract:
>    DNSSEC provides data integrity and source authentication to a basic
>    DNS RRset.  Given a RRset, a public key and a signature, a DNSSEC
>    validator checks the signature, time constraints, and other, local,
>    policies.  In case of mismatch the RRSet is considered illegitimate
>    and is rejected.
>
>    Accuracy in DNSSEC validation, that is, avoiding false positives and
>    catching true negatives, requires that both the signing process and
>    validation process adhere to the protocol, which begins with external
>    configuration parameters.  This document describes requirements for a
>    validator to be able to perform accurate validation.
>
>
5. Trust Anchor Datastore
"A company "Example" may for address all its devices"
probably should be:
"A company "Example" may address all its devices"

-- 
Bob Harold