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

2019-10-22 Thread Puneet Sood
On Wed, Oct 2, 2019 at 2:43 AM Vladimír Čunát wrote: > > On 9/30/19 11:47 PM, Warren Kumari wrote: > > On Mon, Sep 30, 2019 at 7:54 AM Tony Finch wrote: > >> Difficult. In general there will be multiple upstream servers, even in > >> the simplest case of a stub talking to a recursive server

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

2019-10-02 Thread Vladimír Čunát
On 9/30/19 11:47 PM, Warren Kumari wrote: > On Mon, Sep 30, 2019 at 7:54 AM Tony Finch wrote: >> 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

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

2019-09-30 Thread Warren Kumari
On Mon, Sep 30, 2019 at 7:54 AM Tony Finch wrote: > > Wes Hardaker 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

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

2019-09-30 Thread Tony Finch
Wes Hardaker 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

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

2019-09-27 Thread Wes Hardaker
I've gone through everyone's (wonderful) comments and have addressed almost all of them, and published a -10. Please let me know if you think I missed anything. Responses to the comments will be sent out shortly. (and sorry for the delay on this ; day-job hit me over the head hard in the last