-
Notifications
You must be signed in to change notification settings - Fork 2
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
Request RR Types #22
Comments
Sounds fine to me |
Dave - did you submit something already? I didn't see this earlier, but I've been working with Tim Wicinski and we've already written templates for the 3 NSEC5 RRs and were planning to submit them later this week. We also need 2 new DNSSEC algorithm numbers (for the aliased algs), but it looks like those are 'RFC Required' so we won't be able to get early allocations for those :-) |
I haven't done anything yet, pending the go/no-go from the group. |
Shumon any updates on getting the algorithm numbers? |
Hi folks, I haven't submitted anything yet - I was a bit discouraged when I found out that algorithm number assignment is gated on published RFCs. That means a wrench was thrown in my plan to get out running code in the community (that won't need to be modified later). The RR type assignments can be done under early allocation (for which I have the templates) - so I might as well submit them. And maybe we can discuss with IANA folks during IETF is there any other way we can get early assignments for the algorithm numbers. |
Things are in a sufficient state that we could go ahead and ask IANA for allocations for the RR Types we need under Expert Review per RFC 5395.
https://tools.ietf.org/html/rfc5395#section-3.1.1
Shall I?
The text was updated successfully, but these errors were encountered: