requirement
Click on the red underlined text to get to the source
... the DNSSEC protocol modifications. Section 2 of this document
defines the concept of a signed zone and lists the requirements for
zone signing. Section 3 describes the modifications to authoritative
...
... RRset in a signed zone, there MUST be at least
one RRSIG record that meets the following requirements:
o The RRSIG ...
... security-aware authoritative name server has some of the same
requirements. Functions specific to security-aware recursive name
servers are described in Section 3.2; functions specific to
...
... DNSSEC does not change the DNS zone transfer protocol. Section 3.1.5
discusses zone transfer requirements.
...
... zone transfer if the zone fails to meet any of the signing
requirements described in Section 2. The primary objective of a zone
transfer is to ensure that all authoritative name servers have
identical copies of the zone. An authoritative name server ...
... name server, but a stand-alone
security-aware resolver has many of the same requirements. Functions
specific to security-aware recursive name servers are described in
...
... Once the RRSIG RR has met the validity requirements described in
Section 5.3.1, the validator has to reconstruct the original signed
data. The original signed data ...
... Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. ...
... DNSSEC and IPv6 A6 aware server/resolver message size requirements", RFC 3226prop, December 2001. ...
... Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose, "DNS Security Introduction and Requirements", RFC 4033prop, March 2005. ...