Re: [DNSOP] HTTPS and SVBC client support measurement.

Ben Schwartz <bemasc@google.com> Fri, 10 July 2020 01:06 UTC

Return-Path: <bemasc@google.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 43D023A0AA9 for <dnsop@ietfa.amsl.com>; Thu, 9 Jul 2020 18:06:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level:
X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 TAxamySVA0Xn for <dnsop@ietfa.amsl.com>; Thu, 9 Jul 2020 18:06:15 -0700 (PDT)
Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) (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 37C4B3A0AA7 for <dnsop@ietf.org>; Thu, 9 Jul 2020 18:06:15 -0700 (PDT)
Received: by mail-wr1-x42f.google.com with SMTP id q5so4165294wru.6 for <dnsop@ietf.org>; Thu, 09 Jul 2020 18:06:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=AkOOhIDN0ArWj0rUAjBkbWcUSK/RHk8uKeEuKZ9c4Fk=; b=qQCNAplaC3oSL2KGB5oKOTBk2YtpfuquHkP9+UrRpIpl2ILcewph+Opp6kL1YG9Z9G DbKOipiYGNhz7npnirvcTKNoJw3ug1LU0JT2UymjtsPFcBOIB+I8i61vR4hQXXcpi5iX eNytya87Uh85sE80QHnCuPQdMnMg8uOigFn43daVmtCPfd7u2GhD1Qm5SE9LXEvYJELX bNRl41aAf2ZUYVnMNdzMIbQqetQwmK+Ags8gEhZShEnA6yetjBplsS06gtzkVWuXXKN9 zEeFrRUQ8VCWX/mHkbOMLl7JxXfAHM/w3gH599rDUWyVOqE1GVrVDahuhC1eYVIPajMk 2RDw==
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=AkOOhIDN0ArWj0rUAjBkbWcUSK/RHk8uKeEuKZ9c4Fk=; b=bRuXjzDnsTTlC0tovURCKy/hDPyJCQhnw6CmhfGLR1Lurmoc0nHjjM9R0qSaEsrlD2 sGFxYg+MpfUYP5aLQzmRhEuTSkbykszbaGRQcgWC9cCHWxbjv1g8DIJMuqTTVhleP0Fa LOs4kIKMxNPr5wPUbtQhp0HyFPxb+Bj8cbUGtYmaABuLLU753c56ri9JnHCeTjtsbAat tCS4LmjcAQmBpo/1K7o/GyOfbAXkfVt2Ji5XOIcShy06p0Ab88fZnq5qpMwOObZlRZRj Hsr3texOD3lKaZ7PTz6qIgZhYRRCIGNJ3l5ilY0UkrveNSPq55elI8rpYwIs5HYiH9xP p5rg==
X-Gm-Message-State: AOAM532YABEfvosESOK7Fa84LGolJGlVs67EG8n04m66BFBtBj8VYEXg 6JXBeLMl4Rvw0ySTLP6Ep1tgNszCWjxlYIfZBZtCRQ==
X-Google-Smtp-Source: ABdhPJwqywOgXT4+fW3Yoag8H0sY8HbmhKLlmjsgKJh4xbrZNyuroC1n6G1NN9Xvm2Bjn47Ug1M3TE4ATxHVB5Ot/wY=
X-Received: by 2002:a5d:5381:: with SMTP id d1mr66364608wrv.177.1594343173307; Thu, 09 Jul 2020 18:06:13 -0700 (PDT)
MIME-Version: 1.0
References: <F63A6D01-56C9-439A-A4B8-4855AC7F7E93@isc.org> <CAHbrMsCwGjg9zaQXmWrsnQzrJq_2jtcx3CudCGazzMKXyefjLQ@mail.gmail.com> <242DC956-0B1A-48A2-9CCB-25B2A12625E7@isc.org>
In-Reply-To: <242DC956-0B1A-48A2-9CCB-25B2A12625E7@isc.org>
From: Ben Schwartz <bemasc@google.com>
Date: Thu, 09 Jul 2020 21:06:01 -0400
Message-ID: <CAHbrMsD80pmcC6qEm29G8bq2sewBOOnaHtLpOTHoSDNTGhO7-A@mail.gmail.com>
To: Mark Andrews <marka@isc.org>
Cc: dnsop WG <dnsop@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="0000000000008501d105aa0bf2f8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/VxhEdJOl3a-FI45f5SSoLuWkti8>
Subject: Re: [DNSOP] HTTPS and SVBC client support measurement.
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 10 Jul 2020 01:06:17 -0000

On Thu, Jul 9, 2020 at 8:51 PM Mark Andrews <marka@isc.org> wrote:

>
> > However, I think your purpose here is already well-served by the current
> draft.  If you publish SVCB records that point to a different server IP
> address or port from the non-SVCB connections, you can easily observe what
> fraction of users are SVCB-enabled.
>
> but those mechanisms don’t help people deciding whether to publish
> HTTPS/SVBC in the first place.
>

Publishing a SVCB record is free, and if the operator is considering
publishing _only_ a SVCB record, surely they should first be willing to
publish it in addition to their current configuration.

As in your example, the difficulty was not in publishing the MX record in
the first place, but in safely removing the apex address records.


> > --
> > Mark Andrews, ISC
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > PHONE: +61 2 9871 4742 <+61%202%209871%204742>              INTERNET:
> marka@isc.org
> >
> > _______________________________________________
> > DNSOP mailing list
> > DNSOP@ietf.org
> > https://www.ietf.org/mailman/listinfo/dnsop
>
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742 <+61%202%209871%204742>              INTERNET:
> marka@isc.org
>
>