Re: [DNSOP] Reminder: WGLC for draft-ietf-dnsop-nsec-aggressiveuse ends Tonight

Warren Kumari <warren@kumari.net> Wed, 12 October 2016 17:23 UTC

Return-Path: <warren@kumari.net>
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 AD8481293E0 for <dnsop@ietfa.amsl.com>; Wed, 12 Oct 2016 10:23:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.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 UVkNBv-sdsd0 for <dnsop@ietfa.amsl.com>; Wed, 12 Oct 2016 10:23:49 -0700 (PDT)
Received: from mail-qt0-x22e.google.com (mail-qt0-x22e.google.com [IPv6:2607:f8b0:400d:c0d::22e]) (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 0F167129558 for <dnsop@ietf.org>; Wed, 12 Oct 2016 10:23:49 -0700 (PDT)
Received: by mail-qt0-x22e.google.com with SMTP id q7so23516994qtq.1 for <dnsop@ietf.org>; Wed, 12 Oct 2016 10:23:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Zi77yzUsfvTKDZQ4zu0DzA++YQ1UTUCIKLpJOuK8LaA=; b=oF+W/AUfMbrdRByGvZV7X5PSjcnVmf6Z10PybMZtZT+hNY5XR/+VBpaMbWkUQOO/kX VFz8vQa6PeBRG3nYf6JOSsv/QGRWJVlKmjAEQylo6gCbo02HsB7Oc42dwQNuKEGjBkxu Ve5hIBPob9TgCmoBbfbTavUTWNhQcOO7I3RE1vcie2XBu2+poVYIfnRirjGthv66xF+F kWwRFvHyRlVKJg5FaphDe9RONL7HJ7zodgeFlnYhCBDuVsVidjjfFNOgR1RE1jQI3Axd 3r5XgkCtKp+sLJ9YtYbAoxzNMOHFeJh/LdZUGPLuwgC+t7uCSh9AzNrlfd5NpI6zvfET IIKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Zi77yzUsfvTKDZQ4zu0DzA++YQ1UTUCIKLpJOuK8LaA=; b=Js08yI1Tf+2eQcsGRK2RRBE8NbGxhd/eOXUsYhHe4ogYqMyXV035NDV5mBOEkL6ibj UGzpRQaVkJ4sLaD0GXm1Iw0jGi+6iTckNZ0cjeYf3oMY78DqatRfxfzf9rSlMXRfE4+K 68EL3MhEbvMn4OeczIuUpKC4P2HL0UQTv7+XmjoQ093gbIMzDlUKbM3eeIPrwkhbVMqK qp2UjspM+soWyRYAyw9grd9bP+KnbsKf4jZGrMrZQVcGhjlwRSrWU3z3J7RnYY0X7CaA C58MEMInOD0E/HQzAzpSmwy7o3HveV0NX51JBdJiq8lVFjpPQN4asK2ytH7eXF3H4Z4m orsA==
X-Gm-Message-State: AA6/9RmtBOVf3kzQyzwXEOYql78yNPg0J7Ce06E6QA7mWKbPkWi5jcL/pm3MCdYjN62UGV08gW/Wphs5e6FcX04V
X-Received: by 10.200.40.197 with SMTP id j5mr2354708qtj.43.1476293028110; Wed, 12 Oct 2016 10:23:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.55.147.196 with HTTP; Wed, 12 Oct 2016 10:23:17 -0700 (PDT)
In-Reply-To: <CAHw9_iJ-0v09zByyJYQEESeUBOWLRojBKsYyMoA+qLHRAwDh2g@mail.gmail.com>
References: <1fc274b9-2164-1933-54e3-ce47ff48c8a3@gmail.com> <CA+nkc8AGhhLX6517TKs+zyghm5NUipU6Xff_WHM6my-Mu3JARA@mail.gmail.com> <CAHw9_iJ-0v09zByyJYQEESeUBOWLRojBKsYyMoA+qLHRAwDh2g@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
Date: Wed, 12 Oct 2016 13:23:17 -0400
Message-ID: <CAHw9_i+d0D=xVc=2WbSeGa3VZexmvkw01Q4EU-0B+e++TrG9kQ@mail.gmail.com>
To: Bob Harold <rharolde@umich.edu>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/tlDBsmCcPnY1GoDJvo54HNO0rCI>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] Reminder: WGLC for draft-ietf-dnsop-nsec-aggressiveuse ends Tonight
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 12 Oct 2016 17:23:51 -0000

On Mon, Oct 10, 2016 at 12:27 PM, Warren Kumari <warren@kumari.net> wrote:
> UI
>
> On Monday, October 10, 2016, Bob Harold <rharolde@umich.edu> wrote:
>>
>>
>> On Thu, Oct 6, 2016 at 2:53 AM, Tim Wicinski <tjw.ietf@gmail.com> wrote:
>>>
>>>
>>> Just a reminder that the WGLC for  draft-ietf-dnsop-nsec-aggressiveuse
>>> will end later today (barring any stuck issues).  The authors appear to have
>>> addressed all open issues (except JINMEI's last comments).  Please read the
>>> current version here:
>>>
>>> https://datatracker.ietf.org/doc/draft-ietf-dnsop-nsec-aggressiveuse/
>>>
>>> and speak up with any final questions, concerns, etc.
>>>
>> (Reading the version at
>> https://github.com/wkumari/draft-ietf-dnsop-nsec-aggressiveuse in case it is
>> different)
>>
>> Section "3. Problem Statement"
>> The example domain includes a wildcard, but the text reads as though the
>> answer to "cat.example.com" would be that is does not exist.  Should the
>> wildcard be removed for this example?
>
>
>
> Doh!
> Yes, yes it should.
> I was trying to avoid having two separate example zones, but, well,
> premature optimization and all that.. The way it is now is, um, just wrong.
>

... and I have just broken the example into two zones to address this
(example.com, example.org), and checked it into Github - please see
https://github.com/wkumari/draft-ietf-dnsop-nsec-aggressiveuse

I'd really like some help writing / expanding the wildcard text -- I'd
initially removed the "positive" side because I wasn't sure how to
concisely / clearly describe it[0].

If anyone has text which they'd be willing to contribute, it would be
gratefully accepted.

W
[0]: Ok, I'll be completely honest - this was also way easier :-P

> W
>
>
>
>>
>>
>> --
>> Bob Harold
>>
>
>
> --
> I don't think the execution is relevant when it was obviously a bad idea in
> the first place.
> This is like putting rabid weasels in your pants, and later expressing
> regret at having chosen those particular rabid weasels and that pair of
> pants.
>    ---maf



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf