Re: [DNSOP] Second Working Group Last Call for draft-ietf-dnsop-extended-error

[Puneet Sood <[e-mail]>]

I got around to review the draft only recently and have made an
attempt to avoid points of discussion that have been resolved since
IETF Prague. Apologies in advance for any duplicates.

1. Introduction and background
Para 2: "A good example of issues that would benefit ..."
Comment: The paragraph leads up to the conclusion that the EDE codes
will be helpful to a client to decide between retry and stopping.
Since the consensus is that the EDEs are purely diagnostic, it would
be good to reiterate that at the end of this paragraph.

Eric Orth's comment from Sept 17 is also relevant here (no one has
responded to it yet). Quoting the last bullet from his response here
for reference:
https://mailarchive.ietf.org/arch/msg/dnsop/GTg8wa7lQ-VoBFcp_P5tT4VuQhE
*Something like "applications MUST NOT act on EDE" or "applications
MUST NOT change rcode processing" does not seem reasonable to me.  Way
too unclear what "diagnostic" processing is reasonable and allowed or
not.  And potentially limits applications from doing processing based
on very reasonable or obvious interpretations of the received
rcode/EDE combinations."

2. Extended Error EDNS0 option format
Final para: "The Extended DNS Error (EDE) option can be included in
any response (SERVFAIL, NXDOMAIN, REFUSED, and even NOERROR, etc) to a
query that includes OPT Pseudo-RR [RFC6891]. ..."

Comment: Given the level of discussion around behavior when
sending/receiving the EDE option, there should be some more text
giving guidance on behavior.

a. For recursive resolvers, it may be worth pointing that it is not
expected to copy/forward EDE values received from authoritative
nameservers to their clients.
b. What is the expectation on caching for the EDE code generated by a
recursive resolver in response to a query? My expectation is that it
will be cached (if the answer itself is cached) so the next response
has the same EDE code.
c. Truncation: In case a response including the EDE option with
EXTRA-TEXT filled in exceeds the effective UDP payload size, what is
the desired behavior for the EDE option? Should the EXTRA-TEXT field
be left empty in favor of filling in other RR types? Should the
response be marked truncated to require a re-query over TCP?

This is unlikely for failures but could happen when DNSSEC validation
could not be performed due to unsupported digest type.

3.14 Extended DNS Error Code 13 - Cached Error
The resolver has cached SERVFAIL for this query.

Comment: To match the text the name should be "Cached SERVFAIL".

5. Security Considerations
Para 2: "This information is unauthenticated information, and an attacker (e.g
   a MITM or malicious recursive server) could insert an extended error
   response into already untrusted data ..."
Comment: Agree with some other comments that this is not relevant
since no action is expected to be taken based on EDEs.
Comment: There are ideas in the thread to have links to info in the
EXTRA-TEXT and possibly display it to users. I guess the usual
warnings to not click on potentially unsafe links apply.

Thanks,
Puneet

On Thu, Sep 12, 2019 at 9:52 AM Tim Wicinski <[e-mail]> wrote:
>
> All
>
> We had such great comments the first time we did a Working Group
> Last Call for draft-ietf-dnsop-extended-error, that the chairs decided
> a second one would be even better.
>
> Before we start, a few comments:
>
> - Viktor's comments from 11 September will be rolled into the WGLC
>   comments, which means I'll be tracking them with the authors.
>
> - The chairs are not doing to add more codes to the IANA registry
>   in the document.  However, the process is laid out in section 5.2,
>   with three different ranges (Expert Review; First Come, First Serve;
>   and Experimental).
>
> - We're pretty sure all comments have been addressed one way or another,
>   but we still may have missed some.  Please speak up if that is the case.
>
>
> This starts a Working Group Last Call for draft-ietf-dnsop-extended-error
>
> Current versions of the draft is available here:
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-extended-error/
>
> The Current Intended Status of this document is: Standards Track
>
> Please review the draft and offer relevant comments.
> If this does not seem appropriate please speak out.
> If someone feels the document is *not* ready for publication, please speak out with your reasons.
>
> This starts a two week Working Group Last Call process, and ends on:  26 September 2019.
>
> thanks
> tim
> _______________________________________________
> DNSOP mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/dnsop