Dear WG,
This ends the WGLC for draft-ietf-dnsop-dns-error-reporting.
The last call has been extended a bit longer than initially planned, but
valuable feedback has been received from the WG on the the draft. Thank
you very much.
The authors published a -05 revision a week ago that
On Mon, Jul 10, 2023 at 10:27:45PM +0100, Roy Arends wrote:
> > Right, but surely the monitoring agent can decide whether to solicit
> > such a prefix label or not. That is whether an "_er" prefix label is
> > signalled is a *local matter* betweent the authoritative server
> > signalling the
Hi Viktor,
Again, thank you for your detailed, in-depth and insightful response. My
comments are inline, and I’ve removed the parts in agreement.
> On 10 Jul 2023, at 17:58, Viktor Dukhovni wrote:
>
> On Wed, Jul 05, 2023 at 12:17:34PM +0100, Roy Arends wrote:
>
>>> The proposed qname
Chairs
Subject: Re: [DNSOP] Working Group Last call for
draft-ietf-dnsop-dns-error-reporting
!---|
This Message Is From an External Sender
|---!
Ben,
Thanks
e authoritative server
SHOULD respond with TC bit set to force a re-query over TCP.
Hope this suffices.
Warmly,
Roy
> --Ben SchwartzFrom: DNSOP on behalf of Benno
> Overeinder
> Sent: Thursday, June 8, 2023 5:59 AM
> To: DNSOP Working Group
> Cc: DNSOP
On Wed, Jul 05, 2023 at 12:17:34PM +0100, Roy Arends wrote:
> > I would prefer to require resolvers to be more tolerant of unexpected
> > options, and would have servers report the channel without explicit
> > solicitation.
>
> That is indeed the plan. I shall make that explicit in the new
Viktor, thanks for your feedback. Comments inline.
> On 26 Jun 2023, at 22:13, Viktor Dukhovni wrote:
>
> On Thu, Jun 08, 2023 at 11:59:59AM +0200, Benno Overeinder wrote:
>
>> This starts a two week Working Group Last Call process, and ends on:
>> June 22nd, 2023.
>
> I hope my feedback is
On Thu, Jun 08, 2023 at 11:59:59AM +0200, Benno Overeinder wrote:
> This starts a two week Working Group Last Call process, and ends on:
> June 22nd, 2023.
I hope my feedback is not too late. There are a few important elements
of the draft that could use some changes.
On Tue, Jun 20, 2023 at
_
From: DNSOP on behalf of Benno Overeinder
Sent: Thursday, June 8, 2023 5:59 AM
To: DNSOP Working Group
Cc: DNSOP Chairs
Subject: [DNSOP] Working Group Last call for
draft-ietf-dnsop-dns-error-reporting
!---|
This Messa
On Jun 20, 2023, at 16:40, Dick Franks wrote:
>
>
> WGLC is supposed to be a review, nit-picking and clarification process.
A “review” can have results requiring major changes. But your use here seems to
imply “only small changes”. This is incorrect.
Documents in WGLC could be found to
> On 20 Jun 2023, at 23:35, Dick Franks wrote:
>
> On Tue, 20 Jun 2023 at 22:20, Roy Arends wrote:
>> 8
>
>>
>> The change was from -03 to -04 and discussed in the WG IIRC. The specific
>> sentence your refer to was a lingering oversight in the changes from -03 to
>> -04. I have
On Tue, 20 Jun 2023 at 22:20, Roy Arends wrote:
>8
>
> The change was from -03 to -04 and discussed in the WG IIRC. The specific
> sentence your refer to was a lingering oversight in the changes from -03 to
> -04. I have consulted many developers on this, and so far I had no push back.
>
> >
Correction
Deleting that one sentence changes the meaning of the proposal from
explicitly querying the authoritative server for the appropriate
report channel to a dependence on authoritatives attaching an
-(unsolicited) EDNS0 report channel option to each and every query.
> On 20 Jun 2023, at 21:39, Dick Franks wrote:
>
> On Tue, 20 Jun 2023 at 12:21, Roy Arends wrote:
>> 8
>
>>> On 20 Jun 2023, at 12:14, Willem Toorop wrote:
>> 8
>
>>> I have one nit.
>>>
>>> In the Example in section 4.2., a request still "includes an empty ENDS0
>>> report channel".
On Tue, 20 Jun 2023 at 12:21, Roy Arends wrote:
>8
> > On 20 Jun 2023, at 12:14, Willem Toorop wrote:
>8
> > I have one nit.
> >
> > In the Example in section 4.2., a request still "includes an empty ENDS0
> > report channel". The third paragraph of that same section states something
> >
On Tue, 20 Jun 2023 at 12:14, Willem Toorop wrote:
>8
> In the Example in section 4.2., a request still "includes an empty ENDS0
> report channel". The third paragraph of that same section states
> something similar: "As support for DNS error reporting was indicated by
> a empty EDNS0 report
Thank Dick!
> On 16 Jun 2023, at 18:33, Dick Franks wrote:
>
> All
>
> I have reviewed the document which appears to be almost ready for
> submission to IESG.
>
>
> Subsection 6.1.1 uses QNAME to refer to two different entities.
> The opening sentence needs to say nothing more than that the
gt;>
>> This starts a Working Group Last Call for:
>> draft-ietf-dnsop-dns-error-reporting.
>
> Dear all,
>
> I find this is a very valuable addition to the DNS protocol for zone owners
> and authoritative operators. It also opens up potential for valuable future
Op 08-06-2023 om 11:59 schreef Benno Overeinder:
Dear DNSOP WG,
The authors and the chairs feel this document has reached the stage
where it's ready for Working Group Last Call.
This starts a Working Group Last Call for:
draft-ietf-dnsop-dns-error-reporting.
Dear all,
I find
All
I have reviewed the document which appears to be almost ready for
submission to IESG.
Subsection 6.1.1 uses QNAME to refer to two different entities.
The opening sentence needs to say nothing more than that the report
query is a concatenation of the listed items.
The conflicting usage is
Call for:
draft-ietf-dnsop-dns-error-reporting.
Current versions of the draft is available here:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-dns-error-reporting/.
The Current Intended Status of this document is: Standards Track.
Please review the draft and offer relevant comments
the stage where
> it's ready for Working Group Last Call.
>
> This starts a Working Group Last Call for:
> draft-ietf-dnsop-dns-error-reporting.
>
> Current versions of the draft is available here:
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-dns-error-reportin
Dear DNSOP WG,
The authors and the chairs feel this document has reached the stage
where it's ready for Working Group Last Call.
This starts a Working Group Last Call for:
draft-ietf-dnsop-dns-error-reporting.
Current versions of the draft is available here:
https://datatracker.ietf.org
23 matches
Mail list logo
