This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
98hackathon [2017/03/26 17:01] eckelcu_cisco.com |
98hackathon [2017/03/29 15:06] bortzmeyer Typo |
||
---|---|---|---|
Line 142: | Line 142: | ||
* DBUS API and nss-resolv support for Stubby [[https://getdnsapi.net/presentations/stubby-nanog68.pdf]] | * DBUS API and nss-resolv support for Stubby [[https://getdnsapi.net/presentations/stubby-nanog68.pdf]] | ||
* Asyncio support in getdns Python binding | * Asyncio support in getdns Python binding | ||
- | * DNS-over-TLS service monitoring (e.g. [[https://www.monitoring-plugins.org/|Nagios]] plug-in). Using [[https://getdnsapi.net/|getdns]] seems a reasonable choice (or the [[https://miek.nl/2014/August/16/go-dns-package/|Go DNS librray]] since Go has a good TLS package?). Must be able to specify: expiration date for the cert (like the check_http plugin), the qname, qtype, the pinned key... Bonus: being able to test the TLS configuration (no weak cipher, etc) | + | * DNS-over-TLS service monitoring (e.g. [[https://www.monitoring-plugins.org/|Nagios]] plug-in). Using [[https://getdnsapi.net/|getdns]] seems a reasonable choice (or the [[https://miek.nl/2014/August/16/go-dns-package/|Go DNS librray]] since Go has a good TLS package?). Must be able to specify: expiration date for the cert (like the check_http plugin), the qname, qtype, the pinned key... Bonus: being able to test the TLS configuration (no weak cipher, etc) [[http://www.bortzmeyer.org/monitor-dns-over-tls.html|this article]] summarizes the result of this sub-project. |
* TLS chain extension (draft-ietf-tls-dnssec-chain-extension-01) | * TLS chain extension (draft-ietf-tls-dnssec-chain-extension-01) | ||
* IPv6-only prefix discovery for DNS64 (RFC 7050) | * IPv6-only prefix discovery for DNS64 (RFC 7050) |