Re: [DNSOP] Implementations of extended error?

Shane Kerr <shane@time-travellers.org> Fri, 01 February 2019 17:39 UTC

Return-Path: <shane@time-travellers.org>
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 1853A13110E for <dnsop@ietfa.amsl.com>; Fri, 1 Feb 2019 09:39:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 vKCStWdNhgyi for <dnsop@ietfa.amsl.com>; Fri, 1 Feb 2019 09:39:09 -0800 (PST)
Received: from time-travellers.org (c.time-travellers.nl.eu.org [IPv6:2a02:2770::21a:4aff:fea3:eeaa]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42C3113110C for <dnsop@ietf.org>; Fri, 1 Feb 2019 09:39:08 -0800 (PST)
Received: from [188.207.74.243] (helo=[100.122.245.40]) by time-travellers.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <shane@time-travellers.org>) id 1gpcnY-0001lb-1d for dnsop@ietf.org; Fri, 01 Feb 2019 17:40:16 +0000
Date: Fri, 01 Feb 2019 18:38:54 +0100
User-Agent: K-9 Mail for Android
In-Reply-To: <ybl5zu3qurr.fsf@w7.hardakers.net>
References: <ybl5zu3qurr.fsf@w7.hardakers.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----T9H4C93XI58KOTRY6P0FIB4PFFYMPV"
Content-Transfer-Encoding: 7bit
To: dnsop@ietf.org
From: Shane Kerr <shane@time-travellers.org>
Message-ID: <ECA3ECFA-852B-47EE-8162-7ADD6D8EF288@time-travellers.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/s_HaJwlfDMRmtjXHl4QN_obciSs>
Subject: Re: [DNSOP] Implementations of extended error?
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, 01 Feb 2019 17:39:11 -0000

Wes,

I was thinking about adding some support for this at the IETF hackathon, but I'll be meeting with some of the open source DNS folks this weekend at FOSDEM, and seeing if that collides with their existing plans. 

On 1 February 2019 18:32:40 CET, Wes Hardaker <wjhns1@hardakers.net> wrote:
>
>Folks,
>
>We (some definite of we, possibly including you) are curious who is
>planning (or has already) implemented the Extended Error EDNS0
>extension [1]?
>As DNSOP is preferring RFCs that have been implemented already, it
>would
>be good to know what plans exist or have been completed.
>
>[1]: https://datatracker.ietf.org/doc/draft-ietf-dnsop-extended-error/
>
>-- 
>Wes Hardaker
>USC/ISI
>
>_______________________________________________
>DNSOP mailing list
>DNSOP@ietf.org
>https://www.ietf.org/mailman/listinfo/dnsop

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.