-
Notifications
You must be signed in to change notification settings - Fork 26
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
Add support for ILNP records #20
Comments
A bit difficult to test correctness of wire format representation (and signatures) for ILNP records without BIND not supporting them even in snapshot releases... :-/ |
I tested it and it seems OK, thanks. Two more tests could be added: NodeID with more than 4 hex digits in a group are accepted: error5 IN NID 1 00ff:ff2056:ee64:67 LP pointing to the owner name are accepted even with -p all (the RFC says it must not be done) 👍 error2 IN LP 1 error2 |
On Sat, Nov 17, 2012 at 08:53:46AM -0800, Stéphane Bortzmeyer wrote:
Thanks! Should be fixed now. BTW, what do you use to sign zones with NID/LP and friends? \Anton.Our society can survive even a large amount of irrational regulation. |
I do not sign these zones yet. |
The codes for the four ILNP records (NID, L64, L32 and LP) have been added to the IANA registry http://www.iana.org/assignments/dns-parameters. The future RFC is in the RFC Editor Queue http://www.rfc-editor.org/internet-drafts/draft-irtf-rrg-ilnp-dns-06.txt
It would be cool to have validns support for them.
The text was updated successfully, but these errors were encountered: