Parameterized Nameserver Delegation with NS2 and NS2T
draft-tapril-ns2-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Tim April | ||
| Last updated | 2021-01-14 (Latest revision 2020-07-13) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
html
xml
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-tapril-ns2-01.txt
Abstract
Within the DNS, there is no mechanism for authoritative servers to advertise which transport methods they are capable of. If secure transport methods are adopted by authoritative operators, transport signaling would be required to negotiate how authoritative servers would be contacted by resolvers. This document provides two new Resource Record Types, NS2 and NS2T, to facilitate this negotiation by allowing zone owners to signal how the authoritative nameserver(s) for their zone(s) may accept queries.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)