[DNSOP] Mirja Kühlewind's No Objection on draft-ietf-dnsop-nsec-aggressiveuse-09: (with COMMENT)

Mirja Kühlewind <ietf@kuehlewind.net> Mon, 22 May 2017 15:30 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: dnsop@ietf.org
Delivered-To: dnsop@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B41F01200CF; Mon, 22 May 2017 08:30:44 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-dnsop-nsec-aggressiveuse@ietf.org, Tim Wicinski <tjw.ietf@gmail.com>, dnsop-chairs@ietf.org, tjw.ietf@gmail.com, dnsop@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.51.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149546704472.24735.15566276762755962935.idtracker@ietfa.amsl.com>
Date: Mon, 22 May 2017 08:30:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/oltNS1zaiX9k41VUo3RvdFFo6wY>
Subject: [DNSOP] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-?= =?utf-8?q?ietf-dnsop-nsec-aggressiveuse-09=3A_=28with_COMMENT=29?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 22 May 2017 15:30:45 -0000

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 lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-nsec-aggressiveuse/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

One smallish, unimportant editorial comment:
In section 5, e.g.: "If the negative cache of the validating resolver has
sufficient
   information to validate the query, the resolver SHOULD use NSEC,
   NSEC3 and wildcard records aggressively."
it seems like the word "aggressive" has some meaning which was at least
not clear to me. Is there a difference in negative caching and aggressive
negative caching? If this word should provide any additional information
on what to do could you maybe further explain?