[DNSOP] DNS Error Reporting

Roy Arends <roy@dnss.ec> Fri, 30 October 2020 17:03 UTC

Return-Path: <roy@dnss.ec>
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 9FEBD3A10C4 for <dnsop@ietfa.amsl.com>; Fri, 30 Oct 2020 10:03:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dnss.ec
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 xYWzhs8I8URj for <dnsop@ietfa.amsl.com>; Fri, 30 Oct 2020 10:03:09 -0700 (PDT)
Received: from mail-qv1-xf2e.google.com (mail-qv1-xf2e.google.com [IPv6:2607:f8b0:4864:20::f2e]) (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 BC4313A10A0 for <dnsop@ietf.org>; Fri, 30 Oct 2020 10:03:05 -0700 (PDT)
Received: by mail-qv1-xf2e.google.com with SMTP id i17so1008904qvp.11 for <dnsop@ietf.org>; Fri, 30 Oct 2020 10:03:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dnss.ec; s=google; h=from:mime-version:subject:message-id:date:cc:to; bh=vtcAFoBT9OicCWF4EjKJ43QB01AGk0o3RDt4CaUNz4Q=; b=hdLfzwIYOhAZEj/65pKz/PD/27rHg4L+ajZ40oK5MiPinBSMUEW23adfQT24Lxv5GW uPHW+AUh/otoSBuF+XgAOrztZOX9yXY7/bSKDqQq84EtYKBWF5lL0P+vXywPkIir8o7H AtscXIOdfYS1yf67yQJks1k4eSpbcZBwNV73Y=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:date:cc:to; bh=vtcAFoBT9OicCWF4EjKJ43QB01AGk0o3RDt4CaUNz4Q=; b=THOKDo4PoKf5rRYFBoUD3CvvE1zDXkRIxYbR4p4exT4Q9DLWnp7RbtXVWrswK3ynH5 bgMDEbpEdyPWLPc/f/1uiWMsQs5rfTrBQCB3tfNOTYXUg1AKujTtalRu4k6075gSNfGJ pll5YOk2ujLDH07RlJ2T28XJONmA5cynJ6EiJHn+fUjtz73j5NRDJ3fi0gBTa1kCFFQf EgtyeAIUjWrTQ9eMffATx9iJbKcMTT8oiX5GpCj2Ms63lXrHZDRY8ie3Pn9Vkog8SZMr vajCwJlH9Y57RtKsBCh8rUtKtsnZ0tCrI6JqHicQpRZ36WVVQ3q99f92brEJSe2J7g2M lNRg==
X-Gm-Message-State: AOAM530BCTnJgBS7QqFGl69RKd842L09Im4UO7pPM0/AG1PbPTXJEOwY RdGX2wBFfPmIunmDVkQY7srxWaGKgG84Veva
X-Google-Smtp-Source: ABdhPJyHOW0KbgVHtDKCPm3j1Vius/+P922E5nB1WcxAb/dzGgrb2saDZo/QPGp4Kkdm9FVsQEZhCg==
X-Received: by 2002:a0c:9e53:: with SMTP id z19mr10160484qve.23.1604077383122; Fri, 30 Oct 2020 10:03:03 -0700 (PDT)
Received: from [192.168.0.51] (cpc69046-oxfd25-2-0-cust568.4-3.cable.virginm.net. [81.109.86.57]) by smtp.gmail.com with ESMTPSA id q3sm2940610qkf.24.2020.10.30.10.03.01 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 30 Oct 2020 10:03:02 -0700 (PDT)
From: Roy Arends <roy@dnss.ec>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3CBACFA9-50FE-4650-9792-D04499A8A3B3"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Message-Id: <130FD763-B510-4034-9057-5BEC4C5B2E83@dnss.ec>
Date: Fri, 30 Oct 2020 17:03:00 +0000
Cc: Matt Larson <matt.larson@icann.org>
To: dnsop <dnsop@ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Pddd7H0Lb5GCdC0EZ7k598Fig7c>
Subject: [DNSOP] DNS Error Reporting
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, 30 Oct 2020 17:03:17 -0000

Dear DNS Operations folk,

Matt Larson and I wrote up a method that warns a domain owner of an issue with their configuration. The idea is loosely based on DMARC (RFC7489), and on Trust Anchor signalling (RFC8145). 

The method involves an EDNS0 exchange, containing an “agent” domain, send by the authoritative server  that the resolver can send reports to in case of a failure.

Please see https://tools.ietf.org/html/draft-arends-dns-error-reporting-00 <https://tools.ietf.org/html/draft-arends-dns-error-reporting-00>

I will ask the DNSOP chairs for a slot during IETF109 to present the idea. 

Warmly,

Roy