Re: [DNSOP] draft-ietf-dnsop-extended-error status

Tony Finch <dot@dotat.at> Mon, 30 September 2019 11:54 UTC

Date: Mon, 30 Sep 2019 12:54:08 +0100
From: Tony Finch <dot@dotat.at>
To: Wes Hardaker <wjhns1@hardakers.net>
cc: dnsop@ietf.org
In-Reply-To: <ybly2y9z4v4.fsf@w7.hardakers.net>
Message-ID: <alpine.DEB.2.20.1909301247550.11804@grey.csi.cam.ac.uk>
References: <ybly2y9z4v4.fsf@w7.hardakers.net>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/t5b85LnokCKgyiPjMRPcJkP33hk>
Subject: Re: [DNSOP] draft-ietf-dnsop-extended-error status
Precedence: list

Wes Hardaker <wjhns1@hardakers.net> wrote:
>
> 2) One outstanding topic of discussion that I think we need to decide to
> handle or table till a future document: how do we handle forwarding,
> chained resolvers, and caching.

Difficult. In general there will be multiple upstream servers, even in
the simplest case of a stub talking to a recursive server talking directly
to authoritative servers. So there can be an arbitrary combination of
upstream errors, and they might not relate directly to the QNAME, (e.g.
problems with a parent zone, problems chasing down nameserver addresses).

Perhaps if the upstream problems are consistent with each other, the
resolver can return a single extended error code to its client; otherwise
fall back to a "multiple errors" catch-all?

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Malin: East backing northeast 5 to 7. Moderate or rough. Showers. Good.

[DNSOP] draft-ietf-dnsop-extended-error status Wes Hardaker
Re: [DNSOP] draft-ietf-dnsop-extended-error status Tony Finch
Re: [DNSOP] draft-ietf-dnsop-extended-error status Warren Kumari
Re: [DNSOP] draft-ietf-dnsop-extended-error status Vladimír Čunát
Re: [DNSOP] draft-ietf-dnsop-extended-error status Puneet Sood