IETF Logo Mail Archive

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

Ben Schwartz <bemasc@google.com> Fri, 10 July 2020 00:28 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 4079B3A0A5E for <dnsop@ietfa.amsl.com>; Thu, 9 Jul 2020 17:28:00 -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 OpJgLzv9ugVi for <dnsop@ietfa.amsl.com>; Thu, 9 Jul 2020 17:27:58 -0700 (PDT)
Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) (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 4245F3A0A49 for <dnsop@ietf.org>; Thu, 9 Jul 2020 17:27:58 -0700 (PDT)
Received: by mail-wm1-x329.google.com with SMTP id 22so3983458wmg.1 for <dnsop@ietf.org>; Thu, 09 Jul 2020 17:27:58 -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=kj1WHzd0bwaALcmBKZk6hMihQXLrfqVJXNXJEMHH8/c=; b=HQhNzUp/AGBvJLZIbQBKPGaPO1J2nhkPRiD9PLGziNFE8uRvvwcAfD67+cRcDkM1/N GGCnFBQIgzlQQa0KasdlROF2UiqmIodg6j6oMzxUXc6/pBoH1YLWvLZNzCxOq9ylEuAE V297iYSyZ1DfdW4wt3NmXBgdlpunEy61JUWB09q3c5Duycq8/6vuABev+QYU2w2Kd1nc JULOEcydiPo3WNIVg2XjastbIFgztVXxbGYkEzm2JB5WMxUrRu+nnbdCofHkJK2kmTJX R508Ou/cqIDoxAacUNZuBrpJ3SmXy9lurGuiUFtNwy5UPI2YDrJNjbxpZO/WT5X4rDlb HYJw==
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=kj1WHzd0bwaALcmBKZk6hMihQXLrfqVJXNXJEMHH8/c=; b=VsBD8zmx2j/++Q5jwqkINcASRL276SDWXHwvfu78+g9kR70XFUVou5UD2OazViWlRz dd8TjMlBClDy0mIgEPjmEvjc0qTVB7StxjjeWOFJ9WEn9zppjmyUYz/dd/llaZJjffKf 2D13CoE5z4Lpsv7hGiInLEwJdOoY4ONDU0l9Y4WbKooLRHmjbEatGfAG4z7iNZGTNCJt LhIBmHQTl/dzgnwM4AgJi2mFbYVnaJK8So/hy3bOeyc1YW8+5ISzQy/F3Ba5WcfRD22g 3PXhQnqLsh0d1yeCTv0CjvLAU+pL139p5M4I19nb4XngK9QRwG1Zjkb7zqGIFyOWMZTc Bjdg==
X-Gm-Message-State: AOAM530suB+e3CZFTfVlqeqDfXvi81+HZqxpgh9kFtE3jOXtcUrCvmcp zmAe0ApAWzTh2sFf21xCzxZ4Fhz/YP8baRYstzFnYw==
X-Google-Smtp-Source: ABdhPJwKYHP1CtQk32G9tuGatMVqJrPicEWRLgCJiVI8JSQgdWULbHF8LFNawfMz38vATSyK2lfYtRIKwubFFwagW/I=
X-Received: by 2002:a7b:c3c7:: with SMTP id t7mr2266478wmj.97.1594340876251; Thu, 09 Jul 2020 17:27:56 -0700 (PDT)
MIME-Version: 1.0
References: <F63A6D01-56C9-439A-A4B8-4855AC7F7E93@isc.org>
In-Reply-To: <F63A6D01-56C9-439A-A4B8-4855AC7F7E93@isc.org>
From: Ben Schwartz <bemasc@google.com>
Date: Thu, 09 Jul 2020 20:27:44 -0400
Message-ID: <CAHbrMsCwGjg9zaQXmWrsnQzrJq_2jtcx3CudCGazzMKXyefjLQ@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="0000000000009b72d405aa0b697e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/p-vENAMbee-ZSzX43q06GllLYz0>
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 00:28:00 -0000

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

> It would be useful if there was a way to measure client support for HTTPS
> and SVBC even when they are not in use.  Perhaps a HTTP header could be
> added to signal that the client supports HTTPS? This will provide server
> administrators information about their client population to decide when it
> is safe to remove support for legacy clients.


I don't foresee anyone removing support for non-SVCB-aware clients (I
wouldn't call them "legacy") any time soon.  That sounds like a change that
would take many decades, if it even proves desirable.

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.

-- 
> 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
>

v2.23.0 | Report a Bug | By Email