Re: [DNSOP] DNSOP Call for Adoption: draft-hardaker-rfc5011-security-considerations

Ondřej Surý <ondrej.sury@nic.cz> Mon, 27 March 2017 21:09 UTC

Return-Path: <ondrej.sury@nic.cz>
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 9CCEE127601 for <dnsop@ietfa.amsl.com>; Mon, 27 Mar 2017 14:09:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level:
X-Spam-Status: No, score=-7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 dzLYeR__iJ_M for <dnsop@ietfa.amsl.com>; Mon, 27 Mar 2017 14:09:41 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 581FB127076 for <dnsop@ietf.org>; Mon, 27 Mar 2017 14:09:40 -0700 (PDT)
Received: from zimbra.rfc1925.org (calcifer.labs.nic.cz [217.31.192.138]) by mail.nic.cz (Postfix) with ESMTP id 1DE5D608B4; Mon, 27 Mar 2017 23:09:39 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1490648979; bh=CyULP78EF4K5UfnA+VKcWlsd+j7eCH6X6pvJkYxCHT0=; h=Date:From:To; b=DRTV7MIfybAIPNokqUlxtRBckEYQjEaZDoDuP5+Idga9p3urd76Vtw9jmY94+sFss +gux7kiOcnj1vaPXWATjkQWif5oefQMBrQl0EZX7ROMfMhwmdAAljrX9G+qWzW8/sw nC18207lpoUnK79lPOUHBO+TE8y/Dqpvj5BP9RLw=
Date: Mon, 27 Mar 2017 23:09:38 +0200 (CEST)
From: =?utf-8?Q?Ond=C5=99ej_Sur=C3=BD?= <ondrej.sury@nic.cz>
To: tjw ietf <tjw.ietf@gmail.com>
Cc: dnsop <dnsop@ietf.org>
Message-ID: <437602266.5443.1490648978900.JavaMail.zimbra@nic.cz>
In-Reply-To: <CADyWQ+ECthEmWxDbc717BMQo_=PMxz9M0vthDxjOpNW_M7XPTw@mail.gmail.com>
References: <CADyWQ+ECthEmWxDbc717BMQo_=PMxz9M0vthDxjOpNW_M7XPTw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Originating-IP: [217.31.192.138]
X-Mailer: Zimbra 8.7.0_GA_1659 (ZimbraWebClient - SAF10 (Linux)/8.7.0_GA_1659)
Thread-Topic: DNSOP Call for Adoption: draft-hardaker-rfc5011-security-considerations
Thread-Index: pS90vk0g6Itu8oaTr1eTDWZwAgN9Jw==
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/krbmX3C_AY6PwW8QV0MEx9SSCrk>
Subject: Re: [DNSOP] DNSOP Call for Adoption: draft-hardaker-rfc5011-security-considerations
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 27 Mar 2017 21:09:44 -0000

I support this.

And found a nit, the document says:

   The most confusing element of the above equation comes from the "3 *
   (DNSKEY RRSIG Signature Validity) / 2"

but the formula just before doesn't include "3 *" anywhere in it.

Cheers,
Ondrej

--
 Ondřej Surý -- Technical Fellow
 --------------------------------------------
 CZ.NIC, z.s.p.o.    --     Laboratoře CZ.NIC
 Milesovska 5, 130 00 Praha 3, Czech Republic
 mailto:ondrej.sury@nic.cz    https://nic.cz/
 --------------------------------------------

----- Original Message -----
> From: "tjw ietf" <tjw.ietf@gmail.com>
> To: "dnsop" <dnsop@ietf.org>
> Sent: Thursday, 16 March, 2017 08:16:50
> Subject: [DNSOP] DNSOP Call for Adoption: draft-hardaker-rfc5011-security-considerations

> All
> 
> We've had a lot of WG discussion on this, and it seems relevant to do a formal
> call for adoption. If there are outstanding issues raised during the CfA, time
> in Chicago will be set aside to have those discussions.
> 
> 
> This starts a Call for Adoption for:
> draft-hardaker-rfc5011-security-considerations
> 
> The draft is available here:
> [
> https://datatracker.ietf.org/doc/draft-hardaker-rfc5011-security-considerations/
> |
> https://datatracker.ietf.org/doc/draft-hardaker-rfc5011-security-considerations/
> ]
> 
> Please review this draft to see if you think it is suitable for adoption by
> DNSOP, and comments to the list, clearly stating your view.
> 
> Please also indicate if you are willing to contribute text, review, etc.
> 
> If there are
> 
> This call for adoption ends: 30 March 2017
> 
> Thanks,
> tim wicinski
> DNSOP co-chair
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop