Re: [DNSOP] Call for Adoption: Survey of Domain Verification Techniques using DNS
Michael StJohns <msj@nthpermutation.com> Tue, 12 July 2022 17:01 UTC
Return-Path: <msj@nthpermutation.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 8FF57C157903 for <dnsop@ietfa.amsl.com>; Tue, 12 Jul 2022 10:01:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nthpermutation-com.20210112.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NMbrw5-MHWA7 for <dnsop@ietfa.amsl.com>; Tue, 12 Jul 2022 10:01:09 -0700 (PDT)
Received: from mail-qk1-x72e.google.com (mail-qk1-x72e.google.com [IPv6:2607:f8b0:4864:20::72e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FE38C14F728 for <dnsop@ietf.org>; Tue, 12 Jul 2022 10:00:47 -0700 (PDT)
Received: by mail-qk1-x72e.google.com with SMTP id z11so5257983qkz.13 for <dnsop@ietf.org>; Tue, 12 Jul 2022 10:00:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20210112.gappssmtp.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to; bh=yChuRi+gaD0+GLwVIUfa2MC4wzk05ots12yYNxOU9ME=; b=7/2bGs+2ECjttESYyJNvLjpjmKzfdFuAkQ087V3STR5aPoZeFECJ9qyc0sAG51eoPv +9sSpWNRob14s4jTbtweRodIxzNNziJWssaOaLF9rdIcXa6FF5LsJ/KmPFbo2TfjiL4O t2ElG0IkyyHej3F2FJ2HANwStsW2GcuQCkEve3+C242g+gKfUxd8diziwYSoVd3zSQpq HOA82H839Tp6ORMpji0Qx6oes/5wA/kA7joa5TFk1WICoKLzaNYi2/YFAS1R+yMAGa3T 04w3mKIHo792uGluuOcGBlNAmO5uKKD7N21Sm3+KUiBeisU35u3UQcLXmtP2nrD1MFGx U7Zw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to; bh=yChuRi+gaD0+GLwVIUfa2MC4wzk05ots12yYNxOU9ME=; b=gut0gsL4HfSpDi7qtaQYiH6++vEGTdbw/Fg6orKj58Q640fpImqQrni/S40/t3nbM1 oNVLIyGYeEiyFqohB2DYHo2vo5tEhoufEWFt8uTJZNLF5U+wuW8FSau0Zt0T7qQXU3WT 2RwHqekdQ8UUesLVsAmibA8MrymfE0JZDEIl4OcmCrIBVkkoUt8dti1CFVcU5c7toSKG D+IfOrhrtOEsse3nru7HSEkblth8SJA0gpd56uk22pXsT5tkmuWrjyOUD3qG1CmAe8rs ohnrRyPyPHIQMR57QWTg42AsgeMgIgTyuBP7SySZnkYUxdArp2sYEa8GGcAJPGkpmGCX gtkw==
X-Gm-Message-State: AJIora8zl+RtzoTQdal9xg+NHBthIqUpVFyECYrGPilQViwA4UY4s6el zBHwyoRLHYvO7vUQNz+8alckaUR2zlnaXrah
X-Google-Smtp-Source: AGRyM1vNmVQeC9xOtB2PwAHXA4J4CY4R1ZAUIcuhE8ECqNeo8biu+1zkuxBzDlDsB1TZNXq6wZ08UA==
X-Received: by 2002:a05:620a:4405:b0:6af:2404:de4d with SMTP id v5-20020a05620a440500b006af2404de4dmr16295433qkp.308.1657645245338; Tue, 12 Jul 2022 10:00:45 -0700 (PDT)
Received: from [192.168.1.23] (pool-108-31-156-76.washdc.fios.verizon.net. [108.31.156.76]) by smtp.gmail.com with ESMTPSA id a10-20020ac844aa000000b003154e7466casm7503091qto.51.2022.07.12.10.00.43 for <dnsop@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 12 Jul 2022 10:00:44 -0700 (PDT)
Content-Type: multipart/alternative; boundary="------------qr5HGzzgJ0C73FfjffUUISaH"
Message-ID: <9386a34e-6b43-4de8-ed19-76dccfcd707f@nthpermutation.com>
Date: Tue, 12 Jul 2022 13:00:43 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
Content-Language: en-US
To: dnsop@ietf.org
References: <CADyWQ+FD9J-Wqr8rkgSMnb4+x9CRRKm=6cm6LBsw4F161QC4bg@mail.gmail.com>
From: Michael StJohns <msj@nthpermutation.com>
In-Reply-To: <CADyWQ+FD9J-Wqr8rkgSMnb4+x9CRRKm=6cm6LBsw4F161QC4bg@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/IrNtNL-q20kJpsLzF-9sF3kzjNk>
Subject: Re: [DNSOP] Call for Adoption: Survey of Domain Verification Techniques using DNS
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
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, 12 Jul 2022 17:01:13 -0000
Let's try and attach the comment to the right call... *sigh*. See below. On 7/12/2022 9:29 AM, Tim Wicinski wrote: > > This starts a Call for Adoption for Survey of Domain Verification > Techniques using DNS > > The draft is available here: > https://datatracker.ietf.org/doc/draft-sahib-domain-verification-techniques/ > > Please review this draft to see if you think it is suitable for adoption > by DNSOP, and send any comments to the list, clearly stating your view. > > Please also indicate if you are willing to contribute text, review, etc. > > This call for adoption ends: 26 July 2022 > > Thanks, > tim wicinski > For DNSOP co-chairs > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop Hi - I think this draft SHOULDN'T be adopted on a cost/benefit basis. My main issue is that it's not really clear who the audience for this might be. It's clearly not the developers. I doubt it's the customers as any customer is going to have to follow the guidance laid down by their provider. That leaves the providers as a possible target, but they've already implemented their solutions (as evidenced by the content of this document) and really aren't going to change things unless it saves or makes them money. So I question putting WG (or reviewer) time in on this document. Instead, see if ICANN might stand up a wiki page to memorialize this - at least that wiki might not be obsolete upon publication. Alternately, mostly deleting section 3 (the survey part), renaming the document and focusing on section 4 (the recommendations part) might be worthwhile, but that section is all about formatting TXT messages in a specific way and that's generally been considered anathema for DNS for oh so many reasons. So that may also not be a correct approach. If this does proceed, I'd revise it to not use the RFC 2119 constructs in section 4. Basically, use lower case, and avoid the "its is RECOMMENDED" passive structure. Most of these are targeted at people, not at implementations and people are not protocol elements. Instead, explain why doing it the way being suggested makes sense and leave it for the operator to do what works for them. Mike
- [DNSOP] Call for Adoption: Survey of Domain Verif… Tim Wicinski
- Re: [DNSOP] Call for Adoption: Survey of Domain V… Anthony Eden
- Re: [DNSOP] Call for Adoption: Survey of Domain V… Michael StJohns
- Re: [DNSOP] [Ext] Call for Adoption: Survey of Do… Paul Hoffman
- Re: [DNSOP] Call for Adoption: Survey of Domain V… John R. Levine
- Re: [DNSOP] Call for Adoption: Survey of Domain V… Shivan Kaul Sahib
- Re: [DNSOP] Call for Adoption: Survey of Domain V… Melinda Shore
- Re: [DNSOP] [Ext] Call for Adoption: Survey of Do… Paul Hoffman
- Re: [DNSOP] [Ext] Call for Adoption: Survey of Do… Shivan Kaul Sahib
- Re: [DNSOP] Call for Adoption: Survey of Domain V… Wessels, Duane
- Re: [DNSOP] Call for Adoption: Survey of Domain V… Tim Wicinski