New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[discussion] Force EDNS version negotiation #85

Open

pspacek opened this issue Apr 29, 2019 · 0 comments

Labels

next

Contributor

pspacek commented Apr 29, 2019

Specification: Send queries with EDNS version 255. https://tools.ietf.org/html/rfc6891#section-6.1.3

Expected advantage: Enforcing interoperability for EDNS version negotiation, thus allowing to deploy new versions of EDNS mechanism.

Expected disadvantage: Additional round-trip latency, possibly additional state in DNS resolvers.

Expected implementation complexity for software developers: Medium (largely optimizations)

Expected non-compliance: ? TBD. DNS flag day 2019 did not test for EDNS1+ compatibility because the breakage.

Research to confirm assumptions: TBD

pspacek added the next label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment