Multi Provider DNSSEC models
draft-huque-dnsop-multi-provider-dnssec-04
| Document | Type | Replaced Internet-Draft (dnsop WG) | |
|---|---|---|---|
| Last updated | 2019-01-06 | ||
| Replaced by | RFC 8901 | ||
| Stream | IETF | ||
| Intended RFC status | Informational | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-dnsop-multi-provider-dnssec | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-huque-dnsop-multi-provider-dnssec-04.txt
Abstract
Many enterprises today employ the service of multiple DNS providers to distribute their authoritative DNS service. Deploying DNSSEC in such an environment may present some challenges depending on the configuration and feature set in use. This document will present several deployment models that may be suitable.
Authors
Shumon Huque
(shuque@gmail.com)
Pallavi Aras
(paras@salesforce.com)
John Dickinson
(jad@sinodun.com)
Jan Včelák
(jvcelak@ns1.com)
David Blacka
(davidb@verisign.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)