"Michael J. Sheldon" writes:
Brian and Michael both,
> > Rationale : the current text seems to imply this code is only when
> > there is no DNSKEY at all.
> I disagree. There are going to be cases where DS and DNSKEY are not
> fully in sync due to key rollovers, prestaging, etc. This is not a
Hi Stephane,
Thanks for your great review (and support of the draft). We've made a
number of changes based on your suggestions, and I'm including a more
detailed accounting below of steps taken based on your review. Sorry
for the delay in getting a response back to you.
6 Stephane Bortzmeyer
Hi Petr,
Sorry for the delay in responding to your excellent review. You raised
a large number of good suggestions and clarifications. Attached are my
more detailed actions and responses to your points. Look for "results:"
and "response:" for my/our responses to each item. [Warren and I
On Wed, 20 Feb 2019 at 11:27, Petr Špaček wrote:
8<
> Yet another code propodsl:
> * answer with stale data
>
>The resolver was unable to resolve answer within its time limits and
>decided to answer with stale data instead of answering with an error.
>This is typically caused by
On 07. 02. 19 16:47, Petr Špaček wrote:
> --- New code points ---
>
> I propose to add couple more codes:
Yet another code propodsl:
* answer with stale data
The resolver was unable to resolve answer within its time limits and
decided to answer with stale data instead of answering with an
On Fri, Feb 15, 2019 at 09:34:16AM +,
Jim Reid wrote
a message of 19 lines which said:
> Why? From the client's perspective, there's no effective difference
> between these.
In the first case, you can talk with someone which you have some
relationship with (the ISP, typically).
> Their
> On 15 Feb 2019, at 09:02, Stephane Bortzmeyer wrote:
>
> I really think it is important to make the difference between:
>
> * I blocked your request because that's _my_ policy
> * I blocked your request because I'm compelled to do so, don't
> complain, it would be useless.
Why? From the
On Thu, Feb 14, 2019 at 08:51:25PM +0100,
Stephane Bortzmeyer wrote
a message of 101 lines which said:
> Otherwise, I suggest to add an error code:
Ooops, I forgot one:
SERVFAIL Extended DNS Error Code 8 - No reachable authority
The resolver could not reach any of the authoritative
On Thu, Feb 14, 2019 at 03:33:23PM -0500,
Warren Kumari wrote
a message of 388 lines which said:
> but how about:
> "The majority of these extended error codes are primarily useful for
> resolvers, to return to stub resolvers or to downstream
> resolvers. Authoritative servers may also use
On Thu, Feb 14, 2019 at 12:34 PM Warren Kumari wrote:
>
>
> On Thu, Feb 14, 2019 at 2:53 PM Stephane Bortzmeyer
> wrote:
>
>> On Mon, Jan 07, 2019 at 12:30:10PM -0800,
>> internet-dra...@ietf.org wrote
>> a message of 44 lines which said:
>>
>> > Title : Extended DNS Errors
On Thu, Feb 14, 2019 at 2:53 PM Stephane Bortzmeyer
wrote:
> On Mon, Jan 07, 2019 at 12:30:10PM -0800,
> internet-dra...@ietf.org wrote
> a message of 44 lines which said:
>
> > Title : Extended DNS Errors
> > Authors : Warren Kumari
> >
On 2/14/19 12:51 PM, Stephane Bortzmeyer wrote:
> On Mon, Jan 07, 2019 at 12:30:10PM -0800,
> internet-dra...@ietf.org wrote
> a message of 44 lines which said:
>
>> Title : Extended DNS Errors
>> Authors : Warren Kumari
>> Evan Hunt
On Mon, Jan 07, 2019 at 12:30:10PM -0800,
internet-dra...@ietf.org wrote
a message of 44 lines which said:
> Title : Extended DNS Errors
> Authors : Warren Kumari
> Evan Hunt
> Roy Arends
>
On Thu, Feb 07, 2019 at 04:47:01PM +0100,
Petr Špaček wrote
a message of 129 lines which said:
> > 4.1.1. NOERROR Extended DNS Error Code 1 - Unsupported DNSKEY Algorithm
> >
> >The resolver attempted to perform DNSSEC validation, but a DNSKEY
> >RRSET contained only unknown
On 08. 01. 19 17:30, Wes Hardaker wrote:
> internet-dra...@ietf.org writes:
>
>> Title : Extended DNS Errors
>> Filename: draft-ietf-dnsop-extended-error-04.txt
>
> FYI, updates from 03 to 04 include:
>
> 1. moving the unsupported algorithm codes to "NOERROR"
> 2.
internet-dra...@ietf.org writes:
> Title : Extended DNS Errors
> Filename: draft-ietf-dnsop-extended-error-04.txt
FYI, updates from 03 to 04 include:
1. moving the unsupported algorithm codes to "NOERROR"
2. changing the text encoding to UTF-8 (was ASCII)
The
16 matches
Mail list logo
