Re: [dns-privacy] [Ext] next steps for draft-opportunistic-adotq

Brian Haberman <brian@innovationslab.net> Tue, 23 March 2021 14:16 UTC

Return-Path: <brian@innovationslab.net>
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 3DA783A0E77 for <dns-privacy@ietfa.amsl.com>; Tue, 23 Mar 2021 07:16:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=innovationslab-net.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 Y_zmUl4RCiOX for <dns-privacy@ietfa.amsl.com>; Tue, 23 Mar 2021 07:16:07 -0700 (PDT)
Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (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 3253F3A0E68 for <dns-privacy@ietf.org>; Tue, 23 Mar 2021 07:16:07 -0700 (PDT)
Received: by mail-qt1-x82c.google.com with SMTP id g24so14966651qts.6 for <dns-privacy@ietf.org>; Tue, 23 Mar 2021 07:16:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=innovationslab-net.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=Y5IWfQ5EC0Z3Te+72ciK4ushqwj1wF6Nfa39BlzI5T0=; b=x6132KKE5+qSsJ0q+lKIEJ+BqMIDVngP0dBtkGy9BoRHaUWHDXRwq+XsXR5a7NG4ra d41rOH20S4uwmbMzwo0dfL+Wqeh4WDZP9QD0+7dH+ymIxwu158OOD1hQVlwATq0CPyg2 qKcgh+KBvTomrlWUDmXFYg2v8XhYCRUi9uGOiZyqWjd0l587QsADyW8rfzYXcgnFnGqX vTHFgnNF/wFk+TJTD+FHx8umsBcULQuesQcSHFkNKFV0ojtG0g7TUuB9nlIqcECJuZKW QXNYSnKcSVThvPqGRp5QFvAm6ih5faRpvO0TasoMoM7pXfDzD11be51uFf0PByjaBMq9 +aqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Y5IWfQ5EC0Z3Te+72ciK4ushqwj1wF6Nfa39BlzI5T0=; b=pTx5obn0CekGf6RlGa47rn0JTox4/83rRlJ8bP6+7l/Smq8FD5WTtV012pYE+/7Nsr IiLB9v4KXQ4uURMOYB5FlVUu71jkHbLntDPx2BLaaT8NuMSinGERgUQtlTQMZonIoPAr BZQc6uyUAOho2zjBZH2Ek6eEcmOOzPmeWAcqK4ql9FVbTf67J4QK7ZmDbS8GTs/qyUk+ weSEBqrapWZ2mMI43oOZ5aKiJriLmny1Tk7UK3BQ/trq1HR0O+XYk2deaQlPuavysep8 3lMCrMfdLRxxDeo0OJ6lVMcGvA7cGMCTSPV8dLwzAChcZQmpHefv7CrFCA4m5DR4+BrR 8Q5w==
X-Gm-Message-State: AOAM531ddSZtziFblvoZo5sfVErfIHj4e2Obgm6igPGOa9SWJV/OveJr VBWFP0Tb60BOydqfqDZ14QBOpbHQn3h/60vA
X-Google-Smtp-Source: ABdhPJwEzZ1pUKxrT9SQk+bUUCMACn2TYywVwbsO6/nVAQRm+vGqke7QkmXNw1HwbUSJULsXCGIqIA==
X-Received: by 2002:ac8:109a:: with SMTP id a26mr4452313qtj.156.1616508965987; Tue, 23 Mar 2021 07:16:05 -0700 (PDT)
Received: from clemson.local ([2601:5ce:300:84e:2098:a680:2bea:11c]) by smtp.gmail.com with ESMTPSA id n6sm5888161qtx.22.2021.03.23.07.16.05 for <dns-privacy@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 23 Mar 2021 07:16:05 -0700 (PDT)
To: dns-privacy@ietf.org
References: <2ba5ac12c24eaee4c51de2cd2c1693e9bd1fd8b2.camel@powerdns.com> <4bc96140-454e-0746-83b3-bb1331cf7cce@cs.tcd.ie> <ADB00FD5-A6EA-4D05-84E8-A44A2E40BE7C@icann.org>
From: Brian Haberman <brian@innovationslab.net>
Message-ID: <8363070a-8fc5-2d20-a9aa-45673d1515ac@innovationslab.net>
Date: Tue, 23 Mar 2021 10:16:04 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.8.1
MIME-Version: 1.0
In-Reply-To: <ADB00FD5-A6EA-4D05-84E8-A44A2E40BE7C@icann.org>
Content-Type: text/plain; charset="windows-1252"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/QO9aTmHdRANNR0cKddI4y9zrBUg>
Subject: Re: [dns-privacy] [Ext] next steps for draft-opportunistic-adotq
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: Tue, 23 Mar 2021 14:16:12 -0000

Hey Paul,
     Clarifying question about SVCB...

On 3/22/21 5:10 PM, Paul Hoffman wrote:
> On Mar 22, 2021, at 1:59 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
>> I think that makes sense with one caveat: I don't interpret
>> these changes as representing a consensus to not use TLSA - I
>> think such a decision is still down the road some, after we
>> have some better ideas as to the practicality or otherwise
>> of the various approaches one might adopt.
>>
>> I know none of these are WG drafts yet but I'd be a bit
>> worried that your changing to use SVCB now might be
>> intrepreted in that way.
> 
> Good point. As we revise this draft, we can put a note in about us needing a signal, and use SCVB as the signal, but the signal might change.
> 

Is there an issue with putting SVCB info in the TLD zones? If I
interpret this ICANN document correctly
(https://newgtlds.icann.org/sites/default/files/agreements/agreement-approved-31jul17-en.html#exhibitA.1),
there are strict limitations on the info that can be put in the TLD zones.

Regards,
Brian