Using Wildcard A and AAAA Resource Records in the DNS for Per-User Host- Based Services
draft-dukhovni-using-wildcard-a-rrsets-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Viktor Dukhovni , Nicolás Williams | ||
| Last updated | 2014-09-05 (Latest revision 2014-03-04) | ||
| RFC stream | (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 how the use of wildcard A and AAAA resource records (RRs) in the Domain Name System (DNS), optionally coupled with self-service key management for host names that match the wildcards, to create per-user services. This memo describes what should be a best current practice.
Authors
Viktor Dukhovni
Nicolás Williams
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)