--- 1/draft-ietf-dnsop-no-response-issue-11.txt	2018-11-04 15:13:13.784326936 -0800
+++ 2/draft-ietf-dnsop-no-response-issue-12.txt	2018-11-04 15:13:13.836328194 -0800
@@ -1,18 +1,18 @@
 
 Network Working Group                                         M. Andrews
 Internet-Draft                                                 R. Bellis
 Intended status: Best Current Practice                               ISC
-Expires: January 28, 2019                                  July 27, 2018
+Expires: May 8, 2019                                    November 4, 2018
 
    A Common Operational Problem in DNS Servers - Failure To Respond.
-                 draft-ietf-dnsop-no-response-issue-11
+                 draft-ietf-dnsop-no-response-issue-12
 
 Abstract
 
    The DNS is a query / response protocol.  Failing to respond to
    queries, or responding incorrectly, causes both immediate operational
    problems and long term problems with protocol development.
 
    This document identifies a number of common kinds of queries to which
    some servers either fail to respond or else respond incorrectly.
    This document also suggests procedures for TLD and other zone
@@ -29,21 +29,21 @@
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF).  Note that other groups may also distribute
    working documents as Internet-Drafts.  The list of current Internet-
    Drafts is at https://datatracker.ietf.org/drafts/current/.
 
    Internet-Drafts are draft documents valid for a maximum of six months
    and may be updated, replaced, or obsoleted by other documents at any
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
 
-   This Internet-Draft will expire on January 28, 2019.
+   This Internet-Draft will expire on May 8, 2019.
 
 Copyright Notice
 
    Copyright (c) 2018 IETF Trust and the persons identified as the
    document authors.  All rights reserved.
 
    This document is subject to BCP 78 and the IETF Trust's Legal
    Provisions Relating to IETF Documents
    (https://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
@@ -840,21 +840,21 @@
    supported):
 
    dig +nocookie +edns=1 +noednsneg +noad +norec +ednsopt=100 soa \
        $zone @$server
 
    expect: status: BADVERS
    expect: SOA record to NOT be present
    expect: an OPT record to be present in the additional section
    expect: OPT=100 to NOT be present
    expect: EDNS Version 0 in response
-   expect: flag: aa to be present
+   expect: flag: aa to NOT be present
    expect: flag: ad to NOT be present
 
 8.2.7.  Testing Truncated Responses
 
    Ask for the DNSKEY records of the configured zone, which must be a
    DNSSEC signed zone.  This query is made with no DNS flag bits set.
    EDNS version 0 is used without any EDNS options.  The only EDNS flag
    set is DO.  The EDNS UDP buffer size is set to 512.  The intention of
    this query is to elicit a truncated response from the server.  Most
    signed DNSKEY responses are bigger than 512 bytes.  This test will