Using Wildcard A and AAAA Resource Records in the DNS for Per-User Host- Based Services
draft-dukhovni-using-wildcard-a-rrsets-00
| The information below is for an old version of the document | |||
|---|---|---|---|
| Document | Type | Expired Internet-Draft (individual) | |
| Authors | Viktor Dukhovni , Nicolás Williams | ||
| Last updated | 2014-09-05 (latest revision 2014-03-04) | ||
| 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-dukhovni-using-wildcard-a-rrsets-00.txt
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
(ietf-dane@dukhovni.org)
Nicolás Williams
(nico@cryptonector.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)