IETF Logo Mail Archive

[DNSOP] Re: AD review of draft-ietf-dnsop-structured-dns-error-19

Lars Eggert <lars@eggert.org> Tue, 26 May 2026 07:08 UTC

Return-Path: <lars@eggert.org>
X-Original-To: dnsop@mail2.ietf.org
Delivered-To: dnsop@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id B7F5AF4FBE1A for <dnsop@mail2.ietf.org>; Tue, 26 May 2026 00:08:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1779779311; bh=gE+I7kAbKHc4+acU4SQum93+hgz9xiPD3/2xRoFvOAw=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=ClMjcbC5IBlh1zplXqEa6zFgtdDeRj4Wk7YWb5Ba4X2bx3SVOtLvvYpqiIk1T/A+7 H2dtXxvursOCgNYuViOTUeA8akO06sepl/0GjH0/wrK2DAp8vrSc01/sHGDFN5MQKy wvrVXz51nwdSTmmLmyMrC5cgRcSkIdjC00EsRzVY=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=eggert.org
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 Gvoy5HjIxu8f for <dnsop@mail2.ietf.org>; Tue, 26 May 2026 00:08:31 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [89.167.44.90]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 6833CF4FBE15 for <dnsop@ietf.org>; Tue, 26 May 2026 00:08:31 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id A87825D98E; Tue, 26 May 2026 10:08:26 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eggert.org; s=dkim; t=1779779307; h=from:subject:date:message-id:to:cc:mime-version:content-type: content-transfer-encoding:in-reply-to:references; bh=gE+I7kAbKHc4+acU4SQum93+hgz9xiPD3/2xRoFvOAw=; b=Ad9GEpwmM8dx7Z9Kmi6g8pJ+VhZ5J9xhapt/cSrPozpUGSBqr+6XcAbpTRxW0L/l57pH8W pZooTeyJb9fZDJl6MdTqTR53Wh9CBrdSVW7aEAlQ/Ws0n8cPKVcRkyz7xubu3KUuITqwzt Su+/p2SPn7lVodevEzsx6+Mor5UiCFl9HvPuZIosJrthobnYfhd0zGSnjOBlb/tIqteoLt zgwLUM2eqt6mDrbHzJEapR7X4p0tj0v1UBOUiM6RQjTbmm24yMOCFEG8Usnat4GcqPdL62 Qi+0dU1pp/hs7axgDDWInPYBM7d+xrSJC8DMNOE4ita8buXeCkXna545Z2DOVg==
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.600.51.1.1\))
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <7CC7A2A9-9D42-4944-BA11-94793FAA13AD@eggert.org>
Date: Tue, 26 May 2026 10:08:15 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <3C56663C-E8B6-4B93-BC0F-448BFBC75EED@eggert.org>
References: <PH0PR11MB49665D117EA1C0C920A1ED0FA93E2@PH0PR11MB4966.namprd11.prod.outlook.com> <CAFpG3geNkMs=_HeeirUcRX2-GXW5wEHZiYTLUj0Q_5CYVeVmWQ@mail.gmail.com> <SA2PR11MB4972BEA47D1E95384D5A82AFA93D2@SA2PR11MB4972.namprd11.prod.outlook.com> <af4QDrlZ-5hCfL_c@p5> <af4S9qW-LHOdQwQF@p5> <af4a6Hm9Eaql7qS9@p5> <PH0PR11MB4966FD11066304902E30BCB9A93A2@PH0PR11MB4966.namprd11.prod.outlook.com> <B98883D5-B6A9-4039-9C9D-B1BCEAE7E46D@mnot.net> <af_v9m2ZZPBiBxtP@p5> <EEE4DC6E-8A80-4268-869E-028FC14E7D8F@mnot.net> <7CC7A2A9-9D42-4944-BA11-94793FAA13AD@eggert.org>
To: Mark Nottingham <mnot=40mnot.net@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3864.600.51.1.1)
X-Last-TLS-Session-Version: TLSv1.2
Message-ID-Hash: OZVVXHCLA4OEK7IMKMEAZOLW7MO5ZFCP
X-Message-ID-Hash: OZVVXHCLA4OEK7IMKMEAZOLW7MO5ZFCP
X-MailFrom: lars@eggert.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsop.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Mukund Sivaraman <muks@mukund.org>, "Eric Vyncke (evyncke)" <evyncke@cisco.com>, tirumal reddy <kondtir@gmail.com>, "dnsop@ietf.org WG" <dnsop@ietf.org>, Dan Wing <danwing@gmail.com>, "neil.cook@noware.co.uk" <neil.cook@noware.co.uk>, Mohamed Boucadair <mohamed.boucadair@orange.com>, Benno Overeinder <benno@nlnetlabs.nl>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: AD review of draft-ietf-dnsop-structured-dns-error-19
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/xOc73mdEqGqo_MjKVccZYlTUTOM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Owner: <mailto:dnsop-owner@ietf.org>
List-Post: <mailto:dnsop@ietf.org>
List-Subscribe: <mailto:dnsop-join@ietf.org>
List-Unsubscribe: <mailto:dnsop-leave@ietf.org>

Hi,

On May 26, 2026, at 10:00, Lars Eggert <lars@eggert.org> wrote:
> Mark is right. I can’t envision any scenario where I wouldn’t want the browser to be in full control of that is shown to the user (incl. localization).

To be more direct: Adding localization at this layer is IMO a terrible idea. There is a lot of complexity added here that still isn't nearly solved by what the doc currently says AND I fail to understand who even needs this in the first place. I mean, the WG can choose to go down this path, but don’t expect browsers to implement any of this.

Lars

v2.46.0 | Report a Bug | By Email | System Status