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

Bob Harold <rharolde@umich.edu> Tue, 02 August 2016 13:44 UTC

Return-Path: <rharolde@umich.edu>
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 205CA12D5EB for <dnsop@ietfa.amsl.com>; Tue, 2 Aug 2016 06:44:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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=umich.edu
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 0QPSSZiRr6B3 for <dnsop@ietfa.amsl.com>; Tue, 2 Aug 2016 06:44:10 -0700 (PDT)
Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002:c05::22b]) (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 B1A9C12D5C9 for <dnsop@ietf.org>; Tue, 2 Aug 2016 06:44:10 -0700 (PDT)
Received: by mail-yw0-x22b.google.com with SMTP id r9so198281166ywg.0 for <dnsop@ietf.org>; Tue, 02 Aug 2016 06:44:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=google-2016-06-03; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=GF/+1U0xOBF3Y+uH/HoFRnv7j23F8re2ETfP7xZ0m+c=; b=PRqL1npKk0j9oIC80enDB/TD9waVTXEpy5sQxoXxuzv9nySp1hMNPOjkXHCwmpOFMM Ann4X2WoSd8ckUruoATdRwi5GZYJmt0bIoOZRoEowHyFgYWC6g5SMeszksTeUEj0tDSG l4tnYFH9Sw1OEhhqrRwwsI5gwc78G/WNSkGB0SfloviJ1IqqtPFG50wHAP5F/o4orsUd 2+B1UgKBkQhYfJbXa5ObVgb68OD/Fgo7Xy+E7Tiq9tQW0EPn4w9Uc58sxEoxfeMAx6F2 qISNoJCWQTLCR11iGOJQcTKhWOhu3J74pGCzKbxlaLPN70Nt7PQesywWOqwRS+j1GJMw sCiw==
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=GF/+1U0xOBF3Y+uH/HoFRnv7j23F8re2ETfP7xZ0m+c=; b=Qvl8nC8sC3LM2jyhzrORkrIaOUJXq6owlr+lblfERIMJEEJZhCeMYMIbi3v7r1wVSz nXckUHnjkmdISJHQ8LMIF3nNSwGr+kNyYHDfiFlsfN37zDMYSA/cO4EwIzIdcvVghjhf 7PZbVB9MNuWv0nF6T5AER1r89lpQXc8F3ZrTrlo2m56PbzBZYfyBODmTcwmWU7Vm2OW2 VNHunMEK/HnzgJtxHuJAnSE++XvtF7QadpKlqNb6++SUh/SNP2VX9i4KyvChKPPE2VWQ 2n7OqNuhk3T6DoszLOxI5AIgvglog/uj8uIlA1ZXadZ+J5nsgRwXuErHEYbhjbjrqNHJ 4Jjw==
X-Gm-Message-State: AEkoousnf3fQIaQCrr2Rtdair8dUZRgjBCFwSMn+zTJWqykHzbJ5SsDJL6OxxtECzEgUenSwr4KEql811IG3JwBg
X-Received: by 10.129.165.68 with SMTP id c65mr47177163ywh.165.1470145449549; Tue, 02 Aug 2016 06:44:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.13.255.3 with HTTP; Tue, 2 Aug 2016 06:44:09 -0700 (PDT)
In-Reply-To: <0lwpk0p0c6.fsf@wjh.hardakers.net>
References: <0lfuqoqhd7.fsf@wjh.hardakers.net> <414228DF-9C59-467A-8DA0-0EE98B03BDFD@verisign.com> <0lwpk0p0c6.fsf@wjh.hardakers.net>
From: Bob Harold <rharolde@umich.edu>
Date: Tue, 02 Aug 2016 09:44:09 -0400
Message-ID: <CA+nkc8DuE-5r-njhbJ2PUQdy9T1-r_ma3FTJcq+wKm8zTBXHfw@mail.gmail.com>
To: Wes Hardaker <wjhns1@hardakers.net>
Content-Type: multipart/alternative; boundary="94eb2c12941a49f4a8053916e986"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/er0EELjooe8oZR9rI9nvdwZ-XdA>
Cc: "wkumari@google.com" <wkumari@google.com>, dnsop <dnsop@ietf.org>, "Wessels, Duane" <dwessels@verisign.com>
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: Tue, 02 Aug 2016 13:44:13 -0000

On Mon, Aug 1, 2016 at 6:54 PM, Wes Hardaker <wjhns1@hardakers.net> wrote:

> "Wessels, Duane" <dwessels@verisign.com> writes:
>
> >>    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?
>
> Very good point.  Changed for our next publication.
>
> >>  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.
>
> Sure.  Though there is always an issue with coming up with terms to
> describe who controls various bits of a zone these days.  It's not the
> content owner, as that's often separated from the security dude that
> signs the content (as you well know).  We need a suitable term for that
> role generally.  I particularly like a suggestion by thesaurus.com, and
> sadly it's actually the better of many of the choices: "zone right-hand
> person".
>
> Any other suggestions?
> --
> Wes Hardaker
> Parsons
>
>
> "zone signer" for that role?

Some typos:

 1.  Introduction
"indented"  should be "intended"

5.  Denial of Service Attack Considerations
"validataor" should be "validator"

-- 
Bob Harold