Hi everybody here,
A new version of I-D, draft-zhang-dnsop-weak-trust-anchor-00.txthas been
successfully submitted and posted to the?IETF repository.?Name:
draft-zhang-dnsop-weak-trust-anchorRevision: 00Title: Weak Trust
Anchor IntroductionDocument date:
Hi,
Section 4:
If the resolver was
configured with a weak trust anchor and got nothing after sending a
request with DO bit set, then it should clear DO bit in the EDNS0 in
the query message and query again to the authoritative name server.
So it could receive a normal DNS
In message 5388821c.8000...@uni-due.de, =?ISO-8859-1?Q?Matth=E4us_Wander?= wr
ites:
Hi,
Section 4:
If the resolver was
configured with a weak trust anchor and got nothing after sending a
request with DO bit set, then it should clear DO bit in the EDNS0 in
the query message
On Fri, 30 May 2014, zhanghai...@cnnic.cn wrote:
Name: draft-zhang-dnsop-weak-trust-anchor
URL:
http://www.ietf.org/internet-drafts/draft-zhang-dnsop-weak-trust-anchor-00.txt
Status: https://datatracker.ietf.org/doc/draft-zhang-dnsop-weak-trust-anchor/
Htmlized:
On Fri, May 30, 2014 at 02:11:45PM -0400, Paul Wouters wrote:
Note also that for this problem, there is already a commonly deployed
solution at the application level that addresses this situation, such
as https://www.nlnetlabs.nl/projects/dnssec-trigger/ which will inform
the user the network
