Paul, Thanks for the update... comment below:
On Aug 4, 2016, at 12:48 PM, Paul Hoffman <[email protected]<mailto:[email protected]>> wrote: Our intention for this month is to add a bunch of other terms from RFCs. I'll also start some threads about terms that we should probably define but that are not in RFCs. In writing the draft about crypto algorithm agility ( https://tools.ietf.org/html/draft-york-dnsop-deploying-dnssec-crypto-algs-01 ) we ran into an issue where we needed to talk about "signing software". (section 2.3) This is software such as OpenDNSSEC that is used in the current DNS infrastructure to do the actual signing of zones. I seem to recall various vendors also having services that would do the signing on the fly for you. This software is of course part of an "authoritative server" defined in your section 5 - https://tools.ietf.org/html/draft-ietf-dnsop-terminology-bis-02#section-5 - but also can be operated on a separate server. I don't know if you / others feel this warrants having an entry in the DNS terminology, but I thought I would point it out. We're also definitely open to adjusting the crypto agility draft to use another term if someone has a better suggestion than "signing software". Dan -- Dan York Senior Content Strategist, Internet Society [email protected]<mailto:[email protected]> +1-802-735-1624 Jabber: [email protected]<mailto:[email protected]> Skype: danyork http://twitter.com/danyork http://www.internetsociety.org/
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
