[DNSOP] Semantics of draft-brotman-rdbd

Matthew Pounsett <matt@conundrum.com> Fri, 29 March 2019 09:19 UTC

Return-Path: <matt@conundrum.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 874DB12023E for <dnsop@ietfa.amsl.com>; Fri, 29 Mar 2019 02:19:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=conundrum-com.20150623.gappssmtp.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 vN5SjGpWfHvw for <dnsop@ietfa.amsl.com>; Fri, 29 Mar 2019 02:19:27 -0700 (PDT)
Received: from mail-it1-x134.google.com (mail-it1-x134.google.com [IPv6:2607:f8b0:4864:20::134]) (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 6180D12021E for <dnsop@ietf.org>; Fri, 29 Mar 2019 02:19:27 -0700 (PDT)
Received: by mail-it1-x134.google.com with SMTP id y204so2694041itf.3 for <dnsop@ietf.org>; Fri, 29 Mar 2019 02:19:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=conundrum-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=kfgyWz/CnK2kgEhyGUvAmRal+tFWaFR3DSNSyyMIIsU=; b=SndG+z+IjI3sY9oxh27BMP0LkPqYeBQNhxzgxWU8Qdd10mcCkIrbseAlApC6WxkczB IQpfEE1288XYJ/YL6zk/Y7t2AnqgOhRR3/gbPNmXZlkB3yc+s64RHha/6ZPV8Mk8S9P1 +gKV+rAUvcF5Ez7diiQ9HAbXhF/tecu4rnLKD90dAOHRfZ9Opp3USHtq50TePrMK8l16 7yXKHiTTuMpBgLhwD0VSOZqgYkKLPeXEkijVWR5QhcRuVJ/GIj4zdLPLjdxdl9Kl7Qzm bOYO7lbYXVbk31XyhCPXmf6UPf6k+hA2XhyNJWmcRg6dNKzn29wINcJo5iCb0s1b5bP2 Ea7g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=kfgyWz/CnK2kgEhyGUvAmRal+tFWaFR3DSNSyyMIIsU=; b=H7gUjVsOQ8DYN9ldDojXa0s5TdUzztzyziFlITaFcXnCvg8gIoB4JffAxOiTGOHVl9 sL7mLqkJ3e7WUz9QcqLkcxH5OUMDPfuf/AQhJSaxRRAEKNK1nOtI5X9XmWx2fZ5xHsNU DMV0H++Mh3WqgMxZ8c47GiPfkg5SQYCh4576SuMLdLcF7Is7ST5BdXMTHkgaFdwWPdVa 52xARJud/tHcTiJ4JLyAaN9bIpltCF3E0gD38oJVRJlgA4tWjMOqWkzYefWuS5IrbPgc DdS3kK36rE/caulzWndfzeQghp9utoA375CDvKaBRyHTgGtS4ElYbbhpDRNrOddUXPf8 SiMg==
X-Gm-Message-State: APjAAAUUeYkKbQI+JjWs6zmHdiI8E6mVGa4wqz+Uerru3IKK9GOnRbAo Q8D2jsTVwr2JcioLul/NNXQUfliD+oTezDHExcXXAFpiykejgw==
X-Google-Smtp-Source: APXvYqxvQ3mAP94yzcSguMuT817VJg1ojS6e8hVYiBCNfLc9UVP0aRtc7TU9QjzGUHNQdQQCLMozU87F1HCZ7t2SkEs=
X-Received: by 2002:a24:205:: with SMTP id 5mr3715869itu.150.1553851166409; Fri, 29 Mar 2019 02:19:26 -0700 (PDT)
MIME-Version: 1.0
From: Matthew Pounsett <matt@conundrum.com>
Date: Fri, 29 Mar 2019 10:19:11 +0100
Message-ID: <CAAiTEH8RinTjoqx6gyjj697nsoNFpvNzZvkOyyZvFxSy3Z55Tg@mail.gmail.com>
To: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ced9890585382ab9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/RKssVnXG7w403PkpQ8-XL9kkaZA>
Subject: [DNSOP] Semantics of draft-brotman-rdbd
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, 29 Mar 2019 09:19:30 -0000

I think the weak semantic definition of this record makes it either not
useful, or actively dangerous, depending on how the consumer of a record
chooses to interpret it.

As I mentioned at the mic in dnsop, it looks to me like the core motivation
of all of the described use cases are actually based around sending signals
to anti-abuse researchers.  If that is the case, then I think that should
be clear.  If those other use cases have other potential motivations for
deploying the record, then those should be more clearly articulated.

With the weak semantics I have concerns about how absent or unidirectional
mappings might be interpreted by researchers.  Where ignorance of the
existence of the record might injure the operations of a domain, or where
an attacker might gain advantage by associating themselves with a visually
similar domain with which they are not actually associated.

I think this needs to be thought about in a lot more detail, and at least
have the risks fleshed out in the draft.  Depending on the outcome of those
discussions I may prefer to see stronger semantics before supporting the
draft, or to see it abandoned entirely.