Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

, and we feel the document is ready for Working Group Last Call. This starts a Working Group Last Call for draft-ietf-dnsop-edns-chain-query Current versions of the draft is available here: https://datatracker.ietf.org/doc/draft-ietf-dnsop-edns-chain-query/ Please review the draft and offer

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

On Mon, 9 Nov 2015, Shumon Huque wrote: I've read this document and think it proposes a useful capability. Thanks for your feedback Shumon! (I think you read -03 and not -04) Some other quick comments: > This document specifies an EDNS0 extension that allows a validating > Resolver running

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

On 11/11/15, 5:01 PM, "Tony Finch" wrote: >Paul Vixie wrote: >> On Wednesday, November 11, 2015 04:41:27 PM Tony Finch wrote: >> > Paul Vixie wrote: >> > >> > > yes, that's flooding the channel. you're allowed one work-stream per >> > >

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

Viktor Dukhovni wrote: > > Except in the presence of CNAME (possibly via DNAME) records, which > might mean that the client needs more records to validate multiple > nodes in the DNS tree. > > So without nameserver assistance 1RTT via parallelism is not always > possible.

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

Tim Wicinski wrote: > Do we know of any implementations that have tried this? I mentioned in another message that I did a brief survey of validators. I was trying to see if there was one I could easily adapt to concurrent queries. Sadly I couldn't find one. A lot of

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

On Wednesday, November 11, 2015 04:41:27 PM Tony Finch wrote: > Paul Vixie wrote: > > > yes, that's flooding the channel. you're allowed one work-stream per > > query, in order that timeouts and other loss are only felt as > > backpressure by those apps who caused them. > >

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

Paul Vixie wrote: > > You get the entire CNAME chain in the first RTT so you can validate all > > the links in the chain in the second RTT. > > here, you appear to be planning for a stub validator, which makes RD=1 > queries. Yes, that's what edns-chain-query is for. > yes,

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

Paul Vixie wrote: > > if you mean label boundaries you have to say label boundaries, > because dots can appear inside labels. Yes. > second, you can't send a burst of queries, as a validator. even apart > from the fact that any CNAME (RFC 2317 style) can add delegation points

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

On Wednesday, November 11, 2015 03:56:31 PM Tony Finch wrote: > Paul Vixie wrote: > > > second, you can't send a burst of queries, as a validator. even apart > > from the fact that any CNAME (RFC 2317 style) can add delegation points > > that weren't at label boundaries in your

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

On Tuesday, November 10, 2015 09:29:30 PM Tony Finch wrote: > Paul Hoffman wrote: > > > With the current DNS protocol, a stub resolver can get all the records > > > it > > > needs to validate a response in 1RTT, by sending multiple concurrent > > > queries for all the

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

Paul Vixie wrote: > On Wednesday, November 11, 2015 04:41:27 PM Tony Finch wrote: > > Paul Vixie wrote: > > > > > yes, that's flooding the channel. you're allowed one work-stream per > > > query, in order that timeouts and other loss are only felt as > > >

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

On Wednesday, November 11, 2015 10:01:51 PM Tony Finch wrote: > Paul Vixie wrote: > > > > i have no objection to multiple parallel outstanding upstream queries > > > > over a TCP stream. > > > > > > Why is TCP special? > > > > because it has per-flow congestion control. > >

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

Paul Hoffman wrote: > > With the current DNS protocol, a stub resolver can get all the records it > > needs to validate a response in 1RTT, by sending multiple concurrent > > queries for all the possible delegation points in the QNAME. > > I'm confused. How does the stub

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

Ólafur Guðmundsson wrote: > On Mon, Nov 9, 2015 at 12:52 PM, Evan Hunt wrote: > > On Mon, Nov 09, 2015 at 04:55:24PM +, Tony Finch wrote: > > > > > > With the current DNS protocol, a stub resolver can get all the records it > > > needs to validate a

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

Do we know of any implementations that have tried this? >From my high tech gadget > On Nov 10, 2015, at 13:29, Tony Finch wrote: > > Paul Hoffman wrote: > >>> With the current DNS protocol, a stub resolver can get all the records it >>> needs to

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

On Tue, Nov 10, 2015 at 09:29:30PM +, Tony Finch wrote: > Paul Hoffman wrote: > > > > With the current DNS protocol, a stub resolver can get all the records it > > > needs to validate a response in 1RTT, by sending multiple concurrent > > > queries for all the

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

Tim Wicinski wrote: > > The authors have updated their document to address all outstanding > issues, and we feel the document is ready for Working Group Last Call. The rationale for this document is still completely wrong. It does not provide any reduction in latency compared

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

On Mon, Nov 9, 2015 at 12:52 PM, Evan Hunt wrote: > On Mon, Nov 09, 2015 at 04:55:24PM +, Tony Finch wrote: > > With the current DNS protocol, a stub resolver can get all the records it > > needs to validate a response in 1RTT, by sending multiple concurrent > > queries for all

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

Paul Hoffman wrote: > On 9 Nov 2015, at 5:02, Tony Finch wrote: > > > > The rationale for this document is still completely wrong. It does not > > provide any reduction in latency compared to the existing DNS protocol. > > Is that really true? That is, I assume that you

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

On 9 Nov 2015, at 8:55, Tony Finch wrote: Paul Hoffman wrote: On 9 Nov 2015, at 5:02, Tony Finch wrote: The rationale for this document is still completely wrong. It does not provide any reduction in latency compared to the existing DNS protocol. Is that really

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

On 9 Nov 2015, at 5:02, Tony Finch wrote: Tim Wicinski wrote: The authors have updated their document to address all outstanding issues, and we feel the document is ready for Working Group Last Call. The rationale for this document is still completely wrong. It does

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

On Mon, Nov 09, 2015 at 04:55:24PM +, Tony Finch wrote: > With the current DNS protocol, a stub resolver can get all the records it > needs to validate a response in 1RTT, by sending multiple concurrent > queries for all the possible delegation points in the QNAME. But has to retain state for

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

On Sun, Nov 1, 2015 at 5:36 PM, Tim Wicinski <tjw.i...@gmail.com> wrote: > Hi > > The authors have updated their document to address all outstanding issues, > and we feel the document is ready for Working Group Last Call. > > This starts a Working Group Last Call for &g

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

On 1 Nov 2015, at 3:36, Tim Wicinski wrote: This starts a Working Group Last Call for draft-ietf-dnsop-edns-chain-query Current versions of the draft is available here: https://datatracker.ietf.org/doc/draft-ietf-dnsop-edns-chain-query/ Please review the draft and offer relevant

[DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

Hi The authors have updated their document to address all outstanding issues, and we feel the document is ready for Working Group Last Call. This starts a Working Group Last Call for draft-ietf-dnsop-edns-chain-query Current versions of the draft is available here: https

[DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

The chairs feel that the Author has addressed all the comments that have been brought up on the mailing list and updated this draft to reflect this. We are ready to move forward with a Working Group Last Call. At this time, this starts a Working Group Last Call for draft-ietf-dnsop

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-chain-query

that the Author has addressed all the comments that have been brought up on the mailing list and updated this draft to reflect this. We are ready to move forward with a Working Group Last Call. At this time, this starts a Working Group Last Call for draft-ietf-dnsop-edns-chain-query Current