Re: [Danish] Proposed WG Charter

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 15 June 2021 17:22 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: danish@ietfa.amsl.com
Delivered-To: danish@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 630EB3A371F for <danish@ietfa.amsl.com>; Tue, 15 Jun 2021 10:22:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 mu9SQO8Pail2 for <danish@ietfa.amsl.com>; Tue, 15 Jun 2021 10:21:56 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A6D83A3724 for <danish@ietf.org>; Tue, 15 Jun 2021 10:21:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 6B44338C13 for <danish@ietf.org>; Tue, 15 Jun 2021 13:23:05 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id zQvFS--vgM0n for <danish@ietf.org>; Tue, 15 Jun 2021 13:23:05 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id DF78438C06 for <danish@ietf.org>; Tue, 15 Jun 2021 13:23:04 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 5359E240 for <danish@ietf.org>; Tue, 15 Jun 2021 13:21:54 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: danish@ietf.org
In-Reply-To: <YMgDpgoFw/7YS5zn@straasha.imrryr.org>
References: <CAEfM=vRA4P7As25Krc64Q5QTEuQZidpmzWgXWivOxOm8x-9ZAw@mail.gmail.com> <YMZwG/l/pne2tHJF@straasha.imrryr.org> <4978.1623625466@localhost> <A0ECC05F-14D3-4370-B3CF-B27DCE94F613@vpnc.org> <CAEfM=vRO6MuirYSBnD+1UeAjKycaPXaJBSrmmRUB5y9x_fX_oQ@mail.gmail.com> <YMftxgW6NhcKfhZV@straasha.imrryr.org> <CAHPuVdVA40xVt49C5vjz=30fYkj1EUHAQrw2X5F9mrEt6_=bTA@mail.gmail.com> <YMgDpgoFw/7YS5zn@straasha.imrryr.org>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 15 Jun 2021 13:21:54 -0400
Message-ID: <9617.1623777714@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/danish/1SCTNSIOjXtyMYr8-1SZkjlMBtI>
Subject: Re: [Danish] Proposed WG Charter
X-BeenThere: danish@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <danish.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/danish>, <mailto:danish-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/danish/>
List-Post: <mailto:danish@ietf.org>
List-Help: <mailto:danish-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/danish>, <mailto:danish-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jun 2021 17:22:02 -0000

Viktor Dukhovni <ietf-dane@dukhovni.org> wrote:
    >> I can also say from personal experience that deploying DNSSEC in
    >> a large complex enterprise remains extremely challenging. Some of the
    >> largest commercial DNS providers in the world have had constant
    >> challenges handling the scale of my employer's signed DNS (ask me
    >> offline sometime and I'll spill the beans). And just a few weeks ago, I
    >> found another critical DNSSEC bug in one of the major open source
    >> DNS implementations.

    > For new applications one need not sign an existing legacy domain,
    > it is easy to register a new dedicated domain that's signed from
    > the getgo.

I was going to say the same thing.
It also has the advantage of not having to deal with the marketing department.

{However, it's a shame that example.com can't register devices.example.com
directly.... or rather that DNSSEC can't jump over the insecured
example.com.}
So one winds up with devices-example.com or some such situation.

    > There may be some minor obstacles along the way, but it rather looks
    > like the software stacks are or will soon be ready to meet them head on.

    > The specs produced by DANISH will not change the world overnight, the
    > design should not be anchored in the past.

We are in agreement here:  that's why I removed the mitigation as a work item
from the initial charter.  I think that we should still think about it though.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide