Paul Mockapetris (1987年11月). “RFC [https://datatracker.ietf.org/doc/html/rfc1035 1035: Domain Names - Implementation and Specification]”. Network Working Group of the IETF (Internet Engineering Task Force). p. 12. 2011年1月12日閲覧。
“RFC [https://datatracker.ietf.org/doc/html/rfc3596 3596: DNS Extensions to Support IP Version 6]”. The Internet Society (2003年10月). 2011年1月13日閲覧。
RFC2931, §2.4. "SIG(0) on the other hand, uses public key authentication, where the public keys are stored in DNS as KEY RRs and a private key is stored at the signer."
RFC3445, §1. "DNSSEC will be the only allowable sub-type for the KEY RR..."
RFC3755, §3. "DNSKEY will be the replacement for KEY, with the mnemonic indicating that these keys are not for application use, per [RFC3445]. RRSIG (Resource Record SIGnature) will replace SIG, and NSEC (Next SECure) will replace NXT. These new types completely replace the old types, except that SIG(0) [RFC2931] and TKEY [RFC2930] will continue to use SIG and KEY."
RFC4025, Abstract. "This record replaces the functionality of the sub-type #4 of the KEY Resource Record, which has been obsoleted by RFC3445."
The minimum field of SOA record is redefined to be the TTL of NXDOMAIN reply in RFC2308.
RFC2930, §6. "... the keying material is sent within the key data field of a TKEY RR encrypted under the public key in an accompanying KEY RR [RFC2535]."
