Next step for DPRIVE: resolver-to-auth link
draft-bortzmeyer-dprive-step-2-05
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Stéphane Bortzmeyer | ||
| Last updated | 2017-06-23 (Latest revision 2016-12-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 examines the possible future work for the DPRIVE (DNS privacy) working group, specially in securing the resolver-to- authoritative name server link with TLS under DNS. It is not intended to be published as a RFC. REMOVE BEFORE PUBLICATION: this document should be discussed in the IETF DPRIVE group, through its mailing list. The source of the document, as well as a list of open issues, is currently kept at Github [1].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)