Architectural Considerations on Application Features in the DNS
draft-iab-dns-applications-03

The information below is for an old version of the document
Document Type None Internet-Draft
Last updated 2011-10-31 (latest revision 2011-07-11)
Stream IAB
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Additional URLs
Stream IAB state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-iab-dns-applications-03.txt

Abstract

A number of Internet applications rely on the Domain Name System (DNS) to support their operations. Many applications use the DNS to locate services for a domain, for example; more recently, some applications have begun transforming identifiers other than domain names into formats that the DNS can process. Proposals to incorporate more sophisticated application behavior into the DNS, however, have raised questions about the applicability and extensibility of the DNS. This document explores the architectural consequences of installing certain application features in the DNS, and provides guidance to future application designers as to the sorts of ways that application can make use of the DNS.

Authors

Olaf Kolkman (olaf@nlnetlabs.nl)
Jon Peterson (jon.peterson@neustar.biz)
Hannes Tschofenig (Hannes.Tschofenig@gmx.net)
Bernard Aboba (bernarda@microsoft.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)