Just quickly go through the draft.
One question: Is it worthwhile to let sub-resolver to know that the answer is
stale. It is true that “stale bread is better than no bread” on the recursive
server’s point of view. But it may be not true for sub-resolver or measurement
probes .
The user
August is over and my self-imposed holiday is over, so it's time to get
busy again. We have this document marked as a candidate for adoption.
This starts a formal Call for Adoption for draft-tale-dnsop-serve-stale
The draft is available here:
https://datatracker.ietf.org/doc/draft-tale-dnsop-serv
Dear David C Lawrence, Warren Kumari:
An IPR disclosure that pertains to your Internet-Draft entitled "Serving
Stale Data to Improve DNS Resiliency" (draft-tale-dnsop-serve-stale) was
submitted to the IETF Secretariat on and has been posted on the "IETF Page
of Intellectual Property Rights Discl
On 5 September 2017 at 00:01, Walter H. wrote:
>
> > The keyword above was examples which they clearly were. Most of
> > 1.0.0.0/8 is in use today despite those examples. The use of local
> > test were also clearly examples. The Microsoft page above advocated
> > the use literal use of .local
On Tue, September 5, 2017 09:04, Stephane Bortzmeyer wrote:
> On Tue, Sep 05, 2017 at 06:09:06AM +0200,
> Walter H. wrote
> a message of 20 lines which said:
>
>> I see it exact this, and it would be fair to prevent future bugs with
>> defining one or two FAKE TLDs (e.g. .corp, .lan) for exact t
On Tue, Sep 05, 2017 at 06:09:06AM +0200,
Walter H. wrote
a message of 20 lines which said:
> I see it exact this, and it would be fair to prevent future bugs with
> defining one or two FAKE TLDs (e.g. .corp, .lan) for exact this use
> case;
Why does it need to be a TLD (see all the discussio
