Page History
RZERC002 was published on 25 January 2021. All RZERC publications can be found at https://www.icann.org/rzerc#documents.
...
...
RZERC002 was published on 25 January 2021. All RZERC publications can be found at https://www.icann.org/rzerc#documents.
View file | ||||
---|---|---|---|---|
|
Recommendation | Description | Current Phase |
---|---|---|
Recommendation |
...
1A | The |
...
RZERC recommends that ICANN org conduct the further studies called for in Recommendation 2 of RSSAC028 and focus on these aspects of the research: Revisit the options and consequences of having signed root zone name server data. |
| |||||||
The RZERC recommends that ICANN org conduct the further studies called for in Recommendation 2 of RSSAC028 and focus on these aspects of the research: Understand and document the behavior of authoritative DNS software currently in use by root server operators with respect to a signed priming response. This should include, but not necessarily be limited to, the size of a signed priming response. Would this result in a lot of UDP fragmentation? Should root server operators expect to see a significant increase in TCP traffic? |
| |||||||
Recommendation 1C | The RZERC recommends that ICANN org conduct the further studies called for in Recommendation 2 of RSSAC028 and focus on these aspects of the research: Understand and document the behavior of recursive name servers with respect to validating signed priming responses. Do they validate and detect incorrect data? What fraction of priming queries today have the DO bit set? |
| ||||||
Recommendation 2A | The RZERC recommends that ICANN org further explore the cost / benefit tradeoffs and risks of signed root zone name server data. |
| ||||||
Recommendation 2B | Do the risks of redirected query traffic outweigh the risks of increased operational complexity? |
|