DNSSEC Resolver Interface to Applications
draft-gieben-resolver-application-interface-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Miek Gieben , Gilles Guette , Olivier Courtay | ||
| Last updated | 2004-04-20 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes an interface between a DNSSEC aware resolver and an application. This interface will define which kind of information a DNSSEC aware resolver is able to send back to an application. The basic question we want to answer is: 'What does an application want to know from a secure aware resolver?'. In Section 4 we define an error bit array. The secure aware resolver will set specific bits in the array. With the added information in the error array, the application can have extra control on what to do with bogus data. When something goes wrong during the secure resolving process the application may also want to know where in the DNS tree this happened. With a simple error array one can not convey this information. A possibility might be to give the application the owner name of the DNS node where the validation failed. This document is written in the hope that it will lead to a discussion within the IETF on the resolver-application interaction(s).
Authors
Miek Gieben
Gilles Guette
Olivier Courtay
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)