RFC 6014 actually discourage doing so :shrug: > During the early discussion of this document, it was proposed that > maybe there should be a small number of values reserved for > "experimental" purposes. This proposal was not included in this > document because of the long history in the IETF of experimental > values that became permanent. That is, a developer would release > (maybe "experimentally") a version of software that had the > experimental value associated with a particular extension, > competitors would code their systems to test interoperability, and > then no one wanted to change the values in their software to the > "real" value that was later assigned.
Also the problem is what "and algorithms" mean? In BIND 9, I do have an experimental implementation of: - FALCON-512 - HAWK-256 - HAWK-512 - SQIsign (NIST Level 1) - MAYO (NIST Level 1) - Antrag-512 And I expect there will be more experiments. If we need interoperability I rather had a temporary agreement between implementors rather than burning DNSSEC algorithm numbers for something that might not be used in the end. Because by the end of the experiment - what happens - do you return those numbers to the pool? Do you reuse them for different algorithm? Allocating numbers for "public" experiments doesn't really make this easier, but more murky. Ondrej -- Ondřej Surý (He/Him) ond...@isc.org My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours. > On 21. 3. 2025, at 15:14, Loganaden Velvindron <logana...@gmail.com> wrote: > > Hi All, > > Based on this experimental branch of PowerDNS: > https://github.com/nils-wisiol/dns-falcon/commit/3e0861cd2942f6a0ca938cf6a20104e450835fae > > Would it be possible to request codepoints for DNSSEC experiments with > Falcon, and algorithms ? > > https://www.iana.org/assignments/dns-sec-alg-numbers/dns-sec-alg-numbers.xhtml > > _______________________________________________ > DNSOP mailing list -- dnsop@ietf.org > To unsubscribe send an email to dnsop-le...@ietf.org
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
