IETF Logo Mail Archive

Re: [Secdispatch] Please help dispatch "Dangerous Labels"

Carsten Bormann <cabo@tzi.org> Wed, 27 July 2022 10:10 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 773E4C13CCD5 for <secdispatch@ietfa.amsl.com>; Wed, 27 Jul 2022 03:10:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XdZc5Rsia0vb for <secdispatch@ietfa.amsl.com>; Wed, 27 Jul 2022 03:10:01 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04838C13CCEA for <secdispatch@ietf.org>; Wed, 27 Jul 2022 03:09:59 -0700 (PDT)
Received: from [192.168.217.136] (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Lt8fG3nHJzDCc3; Wed, 27 Jul 2022 12:09:58 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <87tu73q5c6.fsf@fifthhorseman.net>
Date: Wed, 27 Jul 2022 12:09:58 +0200
Cc: secdispatch@ietf.org
X-Mao-Original-Outgoing-Id: 680609397.2459919-fd74e6f4c92cb722489ea3ccd1e054df
Content-Transfer-Encoding: quoted-printable
Message-Id: <0EADDE18-9F93-4B97-A1DF-8773F922A00B@tzi.org>
References: <87tu73q5c6.fsf@fifthhorseman.net>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/rw-WIFRwaaJhdd20wWso1qcaptw>
Subject: Re: [Secdispatch] Please help dispatch "Dangerous Labels"
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2022 10:10:05 -0000

On 2022-07-26, at 17:08, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:
> 
> The not-so-secret goal of the document is to *discourage* creation of
> new labels like this.  Or, rather, to discourage the creation of systems
> that treat certain "magic" labels as having special properties.

Do we need a draft-___-dns-get-off-my-lawn (analog to what is now BCP 190, RFC 8820)?

Grüße, Carsten

v2.23.0 | Report a Bug | By Email