[dbound] Re: Related origins in Webauthn

John Levine <johnl@ietf.email> Fri, 24 April 2026 17:19 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: dbound@mail2.ietf.org
Delivered-To: dbound@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id DF770E2881B7 for <dbound@mail2.ietf.org>; Fri, 24 Apr 2026 10:19:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1777051160; bh=rojtBkhszL1DpvHa0wZmu/YSNE1pYq0zLusV3cSx5W4=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=o/hsUQncPFX3sBOO+qQhBdVS59EyAKvqzOJuZMLm5JR1e/KgQLSuewWqWPfbOkY77 G8/jSV8sxk2Fh5lpRN1xL4nO5I+jrSve0ENGM2kgKQRMns3TqGF7K10XUaEuV1h2sB slobl18fqmbRVUmLfuFaE2rtruBfdAFnXuuoNRJ8=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.4
X-Spam-Level:
X-Spam-Status: No, score=-4.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b="h8iFv/F6"; dkim=pass (2048-bit key) header.d=ietf.email header.b="Cek5Jks+"
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eloQQLG7kcXI for <dbound@mail2.ietf.org>; Fri, 24 Apr 2026 10:19:18 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 9C315E288017 for <dbound@ietf.org>; Fri, 24 Apr 2026 10:18:18 -0700 (PDT)
Received: (qmail 49641 invoked from network); 24 Apr 2026 17:18:17 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding:cleverness; s=c1e569eba5d9.k2604; t=1777051087; x=1777396687; bh=rojtBkhszL1DpvHa0wZmu/YSNE1pYq0zLusV3cSx5W4=; b=h8iFv/F6ouP1Y/XaBvG6ZbPRbTEBsYOKF8+J9IAsC/CxF/ZfwqcduK/lIEWORimRkTglNrbzLw2TSOizofVhn5AQ0nAAaky7kigltlHxdJdLSfbjsuZpN0mMDwonSksM8D8PEM/XYaP8No7gW453ObXXAMn00wSPS//7rxiW35gCjrOIXU79ALUTIaVJQ1L9IRA2bNH/WWCiDeIwNymAD6RFnSr+jaZ6I+Sij2AlHtnkMuaBz9NLV0E8XD4N7hOrflr0XkiLECs+62mZgq4aoHjgtQ5pqHLDfNOOpoRziOS1lNFxs8j6qKgxfUosgW3VA1NeKWAweZA32VA6hvWxmQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=ietf.email; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding:cleverness; s=c1e569eba5d9.k2604; bh=rojtBkhszL1DpvHa0wZmu/YSNE1pYq0zLusV3cSx5W4=; b=Cek5Jks+WyRbqzQ+gO3mEfbuSrUyql8XQWtzhf4BYCajdp0mcLeHgbmxPzlR1yYUkSf3ab41y7T03NuH3wFw/5RjNtqxDUFNpu+1AAZYVnyUN9Xt7+z/a6WHfOMbBAz35XxR8R0gh7ttDG31XMKcYDh0AygUvDX8kbOfTspkzMYJOZIk0qK0Zbyy2j4Cw3bT46aLBCZOE1Ouv3RlntfEaIHaoer9YaDVN2LJHomCNYGrmIJDtN6A+THPBo7fY0MvAYtJwyArhqOqJLAbm+O8Hp8jbUblXRpu8f9lREIre2CMuaIupXxey+Yj8rYmcZurRiC11PdDVNGLkoCIah7Dbw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126:0:78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126:0:78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 24 Apr 2026 17:18:17 -0000
Received: by ary.qy (Postfix, from userid 501) id A8D921059B233; Fri, 24 Apr 2026 13:18:16 -0400 (EDT)
Date: Fri, 24 Apr 2026 13:18:16 -0400
Message-Id: <20260424171816.A8D921059B233@ary.qy>
From: John Levine <johnl@ietf.email>
To: dbound@ietf.org
In-Reply-To: <aerVrfmoPPDi0Icc@crankycanuck.ca>
Organization: Taughannock Networks
References: <CAH8yC8=Ma2R9ht+RzwhD_AFifJb0sMXOPuH0M1mKE9-QZdKLRA@mail.gmail.com> <aerVrfmoPPDi0Icc@crankycanuck.ca>
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Message-ID-Hash: 54GT3G4O2FXKCJVD7N6MNLPSYOF3EPKD
X-Message-ID-Hash: 54GT3G4O2FXKCJVD7N6MNLPSYOF3EPKD
X-MailFrom: johnl@iecc.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dbound.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: ajs@anvilwalrusden.com
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [dbound] Re: Related origins in Webauthn
List-Id: DNS tree bounds <dbound.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dbound/RczdNCK3OcO_bnYPoKZBtnVL60M>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dbound>
List-Help: <mailto:dbound-request@ietf.org?subject=help>
List-Owner: <mailto:dbound-owner@ietf.org>
List-Post: <mailto:dbound@ietf.org>
List-Subscribe: <mailto:dbound-join@ietf.org>
List-Unsubscribe: <mailto:dbound-leave@ietf.org>

It appears that Andrew Sullivan  <ajs@anvilwalrusden.com> said:
>On Thu, Apr 23, 2026 at 01:52:00PM -0500, Jeffrey Walton wrote:
>>well known url.  I think dbound attempted to partition the set of all
>>domains (and not just group related ones).  Corrections, please.
>
>I don't think DBOUND was able to agree on what it was doing.

Agreed.  I saw at least three things:

1.  Formalize whatever the PSL does.

B.  Formalize boundaries of "same owner" for web cookies and/or wildcard certificates and/or DMARC policy

III.  Some kind of grand statement about public and private subtrees and their boundaries.

> For reasons I don't fully understand, the mail case didn't get any traction anyway.

We went off and did something else. The new version of DMARC lets people publish
_dmarc records anywhere in the DNS tree. If you don't find one for the name
you're looking for, you walk up the tree until you find one or don't. We looked
at a lot of domains and found that you'll rarely walk more than two levels, the
results of the tree walk were almost always the same as with the PSL, and in the
few cases where they were different, the current behavior often looks like it's
a mistake.

Back in the day, the DNS crowd insisted a tree walk would bring the DNS to its
knees. (This was roughly the same era that they insisted that adding new RRTYPEs
was trivial and anyone who disagreed was stupid.) But somehow someone snuck in
the CAA record which uses a tree walk, the knees-bringing didn't happen, so we
could use a tree walk, too.

An even more important point was that the people who wrote web browsers made it
quite clear that they have no interest in adding another DNS lookup to find the
cookie boundaries, and bundling a static copy of the PSL into each browser
release works for them.

R's,
John