Re: [DNSOP] [Ext] I-D Action: draft-ietf-dnsop-serve-stale-03.txt [and 1 more messages]

2019-03-07 Thread Dave Lawrence
Jinmei: > I also found it confusing on my fresh re-read of serve-stale-03 in > that the "example method" section contains normative descriptions > using RFC2119 keywords. You're in good company in that co-author Puneet has voiced the same opinion. My own take is that it's appropriate because

Re: [DNSOP] [Ext] I-D Action: draft-ietf-dnsop-serve-stale-03.txt [and 1 more messages]

2019-03-06 Thread 神明達哉
At Fri, 1 Mar 2019 15:54:39 -0500, Dave Lawrence wrote: > > I'm not sure a standards track document that updates RFC 1034/1035 > > should be recommending a minimum TTL. > > As previously noted, we're making no such recommendation and that will > be clarified. The first definition of "resolution

Re: [DNSOP] [Ext] I-D Action: draft-ietf-dnsop-serve-stale-03.txt [and 1 more messages]

2019-03-01 Thread Paul Hoffman
> On Mar 1, 2019, at 12:54 PM, Dave Lawrence wrote: > > Paul Hoffman writes: >> I'm not sure a standards track document that updates RFC 1034/1035 >> should be recommending a minimum TTL. > > As previously noted, we're making no such recommendation and that will > be clarified. "Attempts

Re: [DNSOP] [Ext] I-D Action: draft-ietf-dnsop-serve-stale-03.txt [and 1 more messages]

2019-03-01 Thread Dave Lawrence
Paul Hoffman writes: > I'm not sure a standards track document that updates RFC 1034/1035 > should be recommending a minimum TTL. As previously noted, we're making no such recommendation and that will be clarified. The first definition of "resolution recheck timer" in section 5 does already say