An IXFR Fallback to AXFR Case
draft-song-dnsop-ixfr-fallback-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Linjian Song | ||
| Last updated | 2016-11-18 (Latest revision 2016-05-17) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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 memo introduces an IXFR issue observed during a multiple signers experiment conducted in Yeti DNS project. In the experiment IXFR client is designed to pull the zone from three IXFR servers who used their own key to sign the zone and produce different RRSIG records intentionally. The configuration of multiple signers cause the failure of IXFR in client side. REMOVE BEFORE PUBLICATION: The source of the document is currently placed at GitHub [xml-file]. Comments and pull request are welcome.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)