Discovery of Designated Resolvers in the Presence of Legacy Forwarders
draft-schwartz-add-ddr-forwarders-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Benjamin M. Schwartz , Chris Box | ||
| Last updated | 2022-05-05 (Latest revision 2021-10-22) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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 draft describes how the Discovery of Designated Resolvers (DDR) standard interacts with legacy DNS forwarders, including potential incompatibilities and relevant mitigations. Discussion Venues This note is to be removed before publishing as an RFC. Discussion of this document takes place on the mailing list (add@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/add/. Source for this draft and an issue tracker can be found at https://github.com/bemasc/ddr-forwarders.
Authors
Benjamin M. Schwartz
Chris Box
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)