RFC 4033:DNS Security Introduction and Requirement...
RFC-Ref

algorithm


Click on the red underlined text to get to the source

... data, but multiple keys are possible. For example, there may be keys for each of several different digital signature algorithms. If a security-aware resolver reliably learns a zone's public key ...


... expired signatures, signatures with unsupported algorithms, data missing that the relevant NSEC RR says should be present, and so ...


... functions necessary to verify digital signatures using at least the mandatory-to-implement algorithm(s). Security-aware resolvers must also be capable of forming an authentication ...


... The "Digital Signature Algorithm Specification" document set refers to the group of documents that describe how specific digital signature ...
... to the group of documents that describe how specific digital signature algorithms should be implemented to fit the DNSSEC resource record format. Each document in this set deals with a specific ...
... resource record format. Each document in this set deals with a specific digital signature algorithm. Please see the appendix on "DNSSEC Algorithm and Digest Types" in [RFC4034 ...
... digital signature algorithm. Please see the appendix on "DNSSEC Algorithm and Digest Types" in [RFC4034] for a list of the algorithms ...
... DNSSEC Algorithm and Digest Types" in [RFC4034] for a list of the algorithms that were defined when this core specification was written. ...



Google
Web
RFC-Ref