IETF Logo Mail Archive

Re: [DNSOP] new dnsop related draft: RFC5011 security considerations

"Wessels, Duane" <dwessels@verisign.com> Mon, 01 August 2016 22:29 UTC

Return-Path: <dwessels@verisign.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 C827912D7B4 for <dnsop@ietfa.amsl.com>; Mon, 1 Aug 2016 15:29:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verisign-com.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 lv1FISt4xFes for <dnsop@ietfa.amsl.com>; Mon, 1 Aug 2016 15:29:55 -0700 (PDT)
Received: from mail-oi0-x264.google.com (mail-oi0-x264.google.com [IPv6:2607:f8b0:4003:c06::264]) (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 575A812B035 for <dnsop@ietf.org>; Mon, 1 Aug 2016 15:29:55 -0700 (PDT)
Received: by mail-oi0-x264.google.com with SMTP id l9so8412626oih.2 for <dnsop@ietf.org>; Mon, 01 Aug 2016 15:29:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verisign-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language:content-id :content-transfer-encoding:mime-version; bh=3sNm5f9Y8T+CUrVDNvxIcYAzEgQ05K9RKkolWJfMncc=; b=AgrfQu4MbhLBDOkrFGhV4OwFag4v7HTZOjMaEOCSfs7HKK8LvOZqZbbKaxWq+N3N0b l1AuJcUTfaVh4wI+iHcuRNLRiVQHWUv6FIMk56qSTiGRlFmaAKfCEcO7GygLr5gbhfvs OyUS6hxCMbabs+o9jAB9cbugewmP2912Zt5VCKbEY8Mw4CPF5w+dG5V1bWW0BixALO44 Svma/DT2ZySjkRxDUOYDhkU/4ZanLruWeGsoDUq3o7vR46ZRv/ZXUls5yMLyxsHEC19R ROXZjFf/qWdLw8337gbPh9k1GPFY/yVkXIHPIADJhB2BM57ASINN1csUQw4Sv+seWfv3 npUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:content-id:content-transfer-encoding:mime-version; bh=3sNm5f9Y8T+CUrVDNvxIcYAzEgQ05K9RKkolWJfMncc=; b=IUIQdMz0tMTQfJon//yUjqndQUCEZi5np7H2QgM7TtbsWlfjGU//crq1loG8T4JLaQ kcRaPQMUDUJnTnXOtTpieHigqfVsJ7YnsSvfvG2VKG7eSL051d5/ULMwmL/HRT0wDVP/ LlBXhAzeOvIVHpCAhCjnHrGz3r/lwtVymIvQxCUi6dj5/lpGoWfLLutf3UwXyPwmvr+V tTIFR6q04VbvMPKnr2/F8BdTb1tAIzsBoQtnBboITnNw6c/8jGLQbJMo8tST3mPL1rGU bD3VL2oDy0O5c4AhaUj0+fmZ7+FT/ROoZLGVuSJG1bWdjFxrwnFZdsQp8k/GsqV4IWKC DWoQ==
X-Gm-Message-State: AEkoouuBYm8XArLp+f1kGG6/0DN3jsOL3lLN30W6pN5jNtsNFB5tyLQNIVk1krzOJMycC/Gf9bN1GmNsqDV0rQapDDAcQFGf
X-Received: by 10.37.214.18 with SMTP id n18mr3104568ybg.57.1470090593762; Mon, 01 Aug 2016 15:29:53 -0700 (PDT)
Received: from brn1lxmailout02.verisign.com (brn1lxmailout02.verisign.com. [72.13.63.42]) by smtp-relay.gmail.com with ESMTPS id i200sm5160074qke.10.2016.08.01.15.29.53 (version=TLS1 cipher=AES128-SHA bits=128/128); Mon, 01 Aug 2016 15:29:53 -0700 (PDT)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01 [10.173.152.205]) by brn1lxmailout02.verisign.com (8.13.8/8.13.8) with ESMTP id u71MTqwP006442 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 1 Aug 2016 18:29:53 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Mon, 1 Aug 2016 18:29:52 -0400
From: "Wessels, Duane" <dwessels@verisign.com>
To: Wes Hardaker <wjhns1@hardakers.net>, "wkumari@google.com" <wkumari@google.com>
Thread-Topic: [DNSOP] new dnsop related draft: RFC5011 security considerations
Thread-Index: AQHR7EA0so5y4OemSEyAd+6PqLuL0aA08v2A
Date: Mon, 01 Aug 2016 22:29:51 +0000
Message-ID: <414228DF-9C59-467A-8DA0-0EE98B03BDFD@verisign.com>
References: <0lfuqoqhd7.fsf@wjh.hardakers.net>
In-Reply-To: <0lfuqoqhd7.fsf@wjh.hardakers.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F7680BD34256954D90D2F921D1A02135@verisign.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/dkbb5Nn09Hfaayelpod9e_0tWXU>
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] new dnsop related draft: RFC5011 security considerations
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: Mon, 01 Aug 2016 22:29:57 -0000

Very nice draft.


>    RRSIG Signature Validity  10 days

Here I think you probably want to say DNSKEY RRSIG signature validity, because thats the only RRset whose validity period matters, right?


>  Zone Maintainer  The owner of a zone intending to publish a new Key-
>     Signing-Keys (KSKs) that will become a trust anchor by validators
>     following the RFC5011  process.

Could I convince you to use another term?  Maybe just Zone Owner?  I worry that when people read Zone Maintainer they would subconsciously put "Root" in front of it and your abstract notes that this isn't really a concern for (current) root zone plans. 

DW

v2.23.0 | Report a Bug | By Email