Michael StJohns writes:
> This document is written with language that works only with the start
> with one key/one key in/one key out/end with one key model for trust
> anchor keys. 5011 specifically recommends that there be at least two
> trust anchor keys and this document doesn't quite get th
On Mon, May 22, 2017 at 11:30 AM, Mirja Kühlewind wrote:
>
> Mirja Kühlewind has entered the following ballot position for
> draft-ietf-dnsop-nsec-aggressiveuse-09: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC li
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Domain Name System Operations of the IETF.
Title : Aggressive use of DNSSEC-validated Cache
Authors : Kazunori Fujiwara
Akir
Spencer Dawkins has entered the following ballot position for
draft-ietf-dnsop-nsec-aggressiveuse-09: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Pleas
I did a quick review - it's improving, but still is getting the basics
wrong.
This document is written with language that works only with the start
with one key/one key in/one key out/end with one key model for trust
anchor keys. 5011 specifically recommends that there be at least two
trust
I've read draft-tale-dnsop-serve-stale-00. Overall I think we need
something like this in practice. Even if, technically, it violates
the current protocol standards, the background motivation is a real
operational issue and I believe we should provide some
standard-compliant mitigation. Of cours
Joel, thank you for your review. I have balloted No Objection.
Alissa
> On Apr 30, 2017, at 10:44 PM, Joel Halpern wrote:
>
> Reviewer: Joel Halpern
> Review result: Ready with Issues
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IE
