IETF Logo Mail Archive

Re: [DNSOP] Second Working Group Last Call - draft-ietf-dnsop-nsec-aggressiveuse

tjw ietf <tjw.ietf@gmail.com> Wed, 14 December 2016 12:58 UTC

Return-Path: <tjw.ietf@gmail.com>
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 D901F12959A for <dnsop@ietfa.amsl.com>; Wed, 14 Dec 2016 04:58:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.439
X-Spam-Level:
X-Spam-Status: No, score=-2.439 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 lU691LwEKQ-F for <dnsop@ietfa.amsl.com>; Wed, 14 Dec 2016 04:58:40 -0800 (PST)
Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (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 10631129623 for <dnsop@ietf.org>; Wed, 14 Dec 2016 04:58:39 -0800 (PST)
Received: by mail-io0-x231.google.com with SMTP id p42so38414554ioo.1 for <dnsop@ietf.org>; Wed, 14 Dec 2016 04:58:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xnqxfb2X2BBU/dMWEm76X8DU3EIAma8u8ES/vhvVwEw=; b=u37TgAjvQvuByGRtpvI4hqhIc/X/q53deTD0J40y8oaM9MIPA4E+mqVz87Rvlh8Yio +UsyVego9XGmCvai0j21F6KIRuSYcUcVCZ03bIpHOQMNW+GSqvAr/lUZQ6EiX2hNSCUk bMJSDbh4+u7JZpZLF6Er7MFJ3FImMnwvZFpHHCQfvwCSkx3xA8z1ejmKDHriL4Vle+26 gXaXpgEvbvUlYiXXiTfcuZY26LdTtI1MmDxNUgjpkTNq+z6Hq0YNWvmQ+gqWUSWg42o5 0d0vCgu8DwFDOzxZ1AR96igi7MjVgnsMuZ6qrEK1dihLPEw9q4zryE7PgjxPZOx9lAWJ cGjw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xnqxfb2X2BBU/dMWEm76X8DU3EIAma8u8ES/vhvVwEw=; b=fjCz92ueci6Ac8HwqO5lLC9ZNZ/kBZrhrKAvRRRpBLWY2dMk94HYUYxRSlMVYosZkh ZTj+LSqKwgE6A8njRPFCJw7osbbouLpatopd2y8wvTxwUk8vae3dSJUHiThqfFh+MstI BRZpqM8Mole/B20WoDp/N8vmp1HAu70WZk8x0YDompQNNRaEwuWcWQnkn5obDngZ+CZM vdvHyHIv//JI5YKGBxuuZaoNp+N3ivu1HvJiGzUeFomuw0SE8ZC+yHYiGpSjQ/EsQvCW di1v46LNF18xQvPuShrVCi7CCm3WZ46IGSkdOTQB6lRitBlbBfWeVNQYY8JzYdqtCF6h DXGw==
X-Gm-Message-State: AKaTC005tk1Gfe42CCkg13YcGMKcGoao+UN24KFkVJVKPndRcSDpdlOmxjHyDlbTpX2VyNzYwKrYnM0Y2XtbBA==
X-Received: by 10.107.182.70 with SMTP id g67mr91267285iof.120.1481720318979; Wed, 14 Dec 2016 04:58:38 -0800 (PST)
MIME-Version: 1.0
Received: by 10.79.163.19 with HTTP; Wed, 14 Dec 2016 04:58:38 -0800 (PST)
In-Reply-To: <be2b3d9f-5081-bcd3-5b85-1d9075883f7e@pletterpet.nl>
References: <CADyWQ+EJ0LO=pU-yUdEHwC3aP5KdXxsnD9kEvmmTeAoe0BxK3A@mail.gmail.com> <be2b3d9f-5081-bcd3-5b85-1d9075883f7e@pletterpet.nl>
From: tjw ietf <tjw.ietf@gmail.com>
Date: Wed, 14 Dec 2016 07:58:38 -0500
Message-ID: <CADyWQ+FY6zr2L5+TO331VwjJsN1EaGEUh1vaj_520b_X_MC8Qw@mail.gmail.com>
To: Matthijs Mekking <matthijs@pletterpet.nl>
Content-Type: multipart/alternative; boundary="001a114abc804556a905439de5bb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/DWRqvN2apZ_BkhDSo7ZjZfTqC5Q>
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] Second Working Group Last Call - draft-ietf-dnsop-nsec-aggressiveuse
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, 14 Dec 2016 12:58:42 -0000

Sigh, I did.

Thank you Matthijs for keeping me honest.

tim


On Wed, Dec 14, 2016 at 7:46 AM, Matthijs Mekking <matthijs@pletterpet.nl>
wrote:

> Tim,
>
> On 13-12-16 20:13, tjw ietf wrote:
>
>> All
>>
>> The process of WGLC for this document engaged the working group and
>> there was much discussion and several different versions.  It seems that
>> the authors have addressed everything that has been brought up.
>>
>> We felt another formal Working Group Last call was needed, though
>> hopefully shorter.
>>
>> This starts a Working Group Last Call for:
>>         "Aggressive use of NSEC/NSEC3"
>>       draft-ietf-dnsop-nsec-aggressiveuse
>>
>> Current versions of the draft is available here:
>>    https://datatracker.ietf.org/doc/draft-ietf-dnsop-nsec-aggressiveuse/
>> <https://datatracker.ietf.org/doc/draft-ietf-dnsop-nsec-aggressiveuse/>
>>
>> For those looking for the differences, these are the differences between
>> the document submitted, and the current one:
>>
>> https://www.ietf.org/rfcdiff?url1=draft-ietf-dnsop-nsec-aggr
>> essiveuse-02&url2=draft-ietf-dnsop-nsec-aggressiveuse-03
>>
>
>
> I think you meant:
>
> https://www.ietf.org/rfcdiff?url1=draft-ietf-dnsop-nsec-aggr
> essiveuse-02&url2=draft-ietf-dnsop-nsec-aggressiveuse-07
>
> Best regards,
>   Matthijs
>
>
>
>> Please review the draft and offer relevant comments. Also, if someone
>> feels the document is *not* ready for publication, please speak out with
>> your reasons.
>>
>>
>> This starts a *one* week Working Group Last Call process, and ends at
>> midnight 20  December  2016 UTC.
>>
>>
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
>>
>>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

v2.23.0 | Report a Bug | By Email