1. 1RFCUnbound

2. 2 : @ttkzw : 24365 MSP 3. 3 DNS Summer Days 2012DNSRFC RFC 4. 4RFC IETFInternet Engineering Task Force RFC"Request for Comments" RFCRFC 5. 5RFC RFCRFCNetwork Working Group R. Arends Request for Comments: 4033 Telematica Instituut Obsoletes: 2535, 3008, 3090, 3445, 3655, 3658, R. Austein 3755, 3757, 3845 ISC Updates: 1034, 1035, 2136, 2181, 2308, 3225, M. Larson 3007, 3597, 3226 VeriSignCategory: Standards Track D. MasseyRFC Colorado State University S. Rose NIST March 2005 RFC DNS Security Introduction and Requirements Status of This Memo This document specifies an Internet standards track protocol for the 6. 6RFC RFC "ERATTA" RFC"obsoletes" RFCRFC RFC RFC 1034RFC 2181 7. 7RFC RFC 1796 "Not All RFCs are Standards" RFC Infomational Experimental Standard Track Proposed Standard Draft Standard Internet Standard Historic 8. 8: Standard Track Proposed Standard Draft Standard RFC 6410201110"Internet Standard" Internet Standard STD xxx 9. 9: BCP Non-Standards Track Experimental Infomational Historic Best Current Practice BCP xxx 10. 10 RFCThe key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. RFC 2119 / BCP 14 "Key words for use in RFCs to Indicate Requirement Levels" RFC 11. 11 MUST REQUIREDSHALL MUST NOT SHALL NOTSHOULDRECOMMENDED SHOULD NOT NOT RECOMMEDED MAY OPTIONAL 12. 12RFC RFC Editor http://www.rfc-editor.org/ IETF TOOLS http://tools.ietf.org/html/ RFC JPRS DNS http://jprs.jp/tech/ DNSRFC DNSSEC http://dnssec.jp/ DNSSECRFC