Re: [dns-privacy] Call for Adoption: draft-hal-adot-operational-considerations

Brian Dickson <brian.peter.dickson@gmail.com> Wed, 28 August 2019 18:22 UTC

Return-Path: <brian.peter.dickson@gmail.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8412C120803 for <dns-privacy@ietfa.amsl.com>; Wed, 28 Aug 2019 11:22:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 y-0e0tCq-mIy for <dns-privacy@ietfa.amsl.com>; Wed, 28 Aug 2019 11:22:35 -0700 (PDT)
Received: from mail-vs1-xe31.google.com (mail-vs1-xe31.google.com [IPv6:2607:f8b0:4864:20::e31]) (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 1AA5F120801 for <dns-privacy@ietf.org>; Wed, 28 Aug 2019 11:22:34 -0700 (PDT)
Received: by mail-vs1-xe31.google.com with SMTP id b20so658238vso.1 for <dns-privacy@ietf.org>; Wed, 28 Aug 2019 11:22:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DLg7blu+0yW0W6YcfPXIS8jfWbmIqtPfueQ9K4VjftU=; b=u7RhS5Pz6FUZKHyC92a+sH62Ru8N2p1B5ND0NRkFa08cdmeeDSLqAVv3+9cCpUYmmo WxIf+dpfAPSaXJ6KPrF6Cvef801FaYbL41cdTOgV6VASVj98aaX/yVSslmiRtmo33SEH qC2iT/RuOayhfNknu2C4VuzsIrHadxKR7qfxScDLXOyPfoBYwKjROQ48OwknGVKzrXxa n4JvY9AsCcRLAc3+Yt5m3bak3PHNGTeYvD6Wi2Sdje58VnyPw+Ix3YbTyH899hde9usk YzSkVOsj3a3pvFUeXx+3jIkw6ckKoOGoEvp3EeoGg6CBTlVqHafMGfm6iNjABdaFXzUe nILQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=DLg7blu+0yW0W6YcfPXIS8jfWbmIqtPfueQ9K4VjftU=; b=mWi1TJD8iynRFTXrSMg8gECsGs2DxCmAGIuCR0IYOcr6TB+cdoNFpQeZT397zCN8Ao MCV6JTvNRT9XeZ2rS30uBneRTqhw/pQ/x6hnIrI0nrzUOugbr0vmHYiYQJ4gKQxMdndx JdvqX2sHWl6DpdJSRRj/5XcCxJluLORLSdRimIkh5nnBqJfCQFXo68WPTj62IbPE4MDX ytWbtwkRFLFUHzPvESAJrCDCyfmssouhf6gXdjYleLf23ufOu9xxy8+oaHcQAC++EwxR kz8PSENr9aellbu3ZmgaGqS+XFjFUpYTm+xFo69qa05KC5HZyXN751FNVjA2pqfZ3rdi XOvg==
X-Gm-Message-State: APjAAAUI09jDoUt4MaHcc2ns18K3/3nAT4sN5XYXf2Hw1wACXtOF9quJ Nnki3JNVnraJgTMzAEHjDL+ThSttJbZ9+cTLsb8=
X-Google-Smtp-Source: APXvYqx9rxoNCzw7Zn7//ODLlH+norCOlHrvtnhRSm+iy5HA2WR816aWhmRJR43KQdavFei/f/cikchr+KPjZTDsQ4Q=
X-Received: by 2002:a67:d812:: with SMTP id e18mr3228423vsj.199.1567016553157; Wed, 28 Aug 2019 11:22:33 -0700 (PDT)
MIME-Version: 1.0
References: <5352e08c-3280-999c-0c3f-d15a9f02a7b4@innovationslab.net> <CAH1iCio5UaXtVXzui4nLtd_e7D1whRbwC886YWMgVLEJ-xKhhQ@mail.gmail.com>
In-Reply-To: <CAH1iCio5UaXtVXzui4nLtd_e7D1whRbwC886YWMgVLEJ-xKhhQ@mail.gmail.com>
From: Brian Dickson <brian.peter.dickson@gmail.com>
Date: Wed, 28 Aug 2019 11:22:20 -0700
Message-ID: <CAH1iCiqZeBe0bnLTqchOz9-SPUEXa8J6c=M2Cec+_5rM5B8QAA@mail.gmail.com>
To: Brian Haberman <brian@innovationslab.net>
Cc: dns-privacy@ietf.org
Content-Type: multipart/alternative; boundary="0000000000000217e7059131793e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/89iTJ__21Qvl0PAooiBUaEfyHZo>
Subject: Re: [dns-privacy] Call for Adoption: draft-hal-adot-operational-considerations
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Aug 2019 18:22:38 -0000

Top reply to my own post, sorry.

Even if *THIS* document is in DPRIVE (which I think it should be), it does
not necessarily imply that ADoT development itself has to be done in
DPRIVE; I think where ADoT development actually happens is a separate
question/discussion.

Brian

On Wed, Aug 28, 2019 at 11:20 AM Brian Dickson <
brian.peter.dickson@gmail.com>; wrote:

>
>
> On Wed, Aug 14, 2019 at 1:40 PM Brian Haberman <brian@innovationslab.net>;
> wrote:
>
>> This starts a Call for Adoption for
>> draft-hal-adot-operational-considerations
>>
>> The draft is available here:
>>
>> https://datatracker.ietf.org/doc/draft-hal-adot-operational-considerations/
>>
>> Please review this draft to see if you think it is suitable for adoption
>> by DPRIVE, and comment to the list, clearly stating your view.
>>
>>
> I am in favor of adoption of this draft by DPRIVE.
>
> My view is as follows:
> - DNS is an ecosystem which by definition requires interoperability.
> - Authority operators are a distinct subset of the participants in the DNS
> ecosystem
> - Authority operators of registered domains (as distinct from
> delegation-only domains) have operational concerns (including scaling
> issues and performance issues) that are appropriate to consider BEFORE the
> development of ADoT itself.
> - I.e. The draft should be input to the ADoT development process, similar
> to a requirements document.
> - Doing development of ADoT without this would be another example of IETF
> "paper engineering", which while attractive to some participants, is very
> harmful to reasonably mature ecosystems. (The "paper engineering" practice
> is harmful even in green-field, IMHO.)
> - Operational considerations != deployment guidelines. This is basically a
> pre-emptive feedback to the standards design, based on known issues that
> will affect any flavor of ADoT, no matter what it looks like.
> - Deployment guidelines to operators would follow implementations, which
> would follow standard development, which *should* take into consideration a
> variety of factors, which this document covers.
> - There is work to be done on the document, but it is a great start.
>
>
>> Please also indicate if you are willing to contribute text, review, etc.
>>
>
> All of the above.
>
> Brian Dickson
> (Speaking for myself, but with the viewpoint of someone doing both
> authority server operation and software development on authority server
> software, intending to implement ADoT.)
>
>
>>
>> This call for adoption ends: 28 August 2019
>>
>> Thanks,
>> Brian & Tim
>>
>> _______________________________________________
>> dns-privacy mailing list
>> dns-privacy@ietf.org
>> https://www.ietf.org/mailman/listinfo/dns-privacy
>>
>