We've written a draft that is intended to describe ways that a
validating host resolver can test a nearby resolver for use as a caching
resource if it is DNSSEC-aware. The document describes tests that can
be done, as well as mitigation techniques that can be used in "less than
ideal situations" (*cough* hotels *cough*).
Our goal is to document how various test suites act, and how various
avoidance techniques are used in various libraries in order to document
existing practice and help future implementations.
--- Begin Message ---
A new version of I-D, draft-hardaker-dnsop-dnssec-roadblock-avoidance-00.txt
has been successfully submitted by Wes Hardaker and posted to the
IETF repository.
Filename: draft-hardaker-dnsop-dnssec-roadblock-avoidance
Revision: 00
Title: DNSSEC Roadblock Avoidance
Creation date: 2013-07-15
Group: Individual Submission
Number of pages: 16
URL:
http://www.ietf.org/internet-drafts/draft-hardaker-dnsop-dnssec-roadblock-avoidance-00.txt
Status:
http://datatracker.ietf.org/doc/draft-hardaker-dnsop-dnssec-roadblock-avoidance
Htmlized:
http://tools.ietf.org/html/draft-hardaker-dnsop-dnssec-roadblock-avoidance-00
Abstract:
This document describes problems that a DNSSEC aware resolver/
application might run into to non-compliant infrastructure. It poses
potential detection and mitigation techniques. The scope of the
document is to create a shared approaches to detect and overcome
network issues that a DNSSEC software/system may face.
The IETF Secretariat
--- End Message ---
--
Wes Hardaker
Parsons
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
