Design Choices When Expanding DNS
draft-ymbk-dns-choices-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Patrik Fältström , Rob Austein | ||
| Last updated | 2004-05-14 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ymbk-dns-choices-00.txt
Abstract
This note discusses how to extend the DNS with new data, for a new application. A discussion which too often circulate around reuse of the TXT record. It lists different mechanisms to accomplish the extension to DNS, and comes to the conclusion use of a new RR Type is the best solution.
Authors
Patrik Fältström
(paf@cisco.com)
Rob Austein
(sra@hactrn.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)