Re: [DNSOP] Review of edns-tcp-keepalive-01

2015-01-22 Thread Andrew Sullivan
On Thu, Jan 22, 2015 at 12:06:44PM -0500, Tim Wicinski wrote: > > The two options are alternative proposals - there should never be a reality > where both proposals exist as supported options. Right. The question is whether you think people are going to behave well (which is more or less what Ra

Re: [DNSOP] Review of edns-tcp-keepalive-01

2015-01-22 Thread Tim Wicinski
On 1/22/15 10:54 AM, Alexander Mayrhofer wrote: * PROTOCOL: Is the expected behaviour (MUST) from both client and server that they should add the Option to every single request / response during a keepalive session? Please clarify the intended behaviour.. Two final comments, sorry: * EDITORI

Re: [DNSOP] Review of edns-tcp-keepalive-01

2015-01-22 Thread Alexander Mayrhofer
> * PROTOCOL: Is the expected behaviour (MUST) from both client and server > that they should add the Option to every single request / response during a > keepalive session? Please clarify the intended behaviour.. Two final comments, sorry: * EDITORIAL/PROTOCOL: Shouldn't the option (as well as t

[DNSOP] Review of edns-tcp-keepalive-01

2015-01-22 Thread Alexander Mayrhofer
Hi, I've reviewed the keepalive draft. Generally, i do like the concept a lot because: a) there's certainly a use case that covers real operational issues b) it's a space-efficient and c) unobstrusive. However, i think the document could improve on clarity in certain aspects - see below for d