idnits 2.17.1 draft-ietf-dnsext-interop3597-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 13. -- Found old boilerplate from RFC 3978, Section 5.5 on line 197. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 174. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 181. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 187. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 6 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There are 26 instances of too long lines in the document, the longest one being 1 character in excess of 72. == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. -- The document has examples using IPv4 documentation addresses according to RFC6890, but does not use any IPv6 documentation addresses. Maybe there should be IPv6 examples, too? Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (May 19, 2005) is 6910 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '1' is defined on line 139, but no explicit reference was found in the text Summary: 6 errors (**), 0 flaws (~~), 5 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 DNS Extensions Working Group J. Schlyter 2 Internet-Draft May 19, 2005 3 Expires: November 20, 2005 5 RFC 3597 Interoperability Report 6 draft-ietf-dnsext-interop3597-02.txt 8 Status of this Memo 10 By submitting this Internet-Draft, each author represents that any 11 applicable patent or other IPR claims of which he or she is aware 12 have been or will be disclosed, and any of which he or she becomes 13 aware will be disclosed, in accordance with Section 6 of BCP 79. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that 17 other groups may also distribute working documents as Internet- 18 Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference 23 material or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt. 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 This Internet-Draft will expire on November 20, 2005. 33 Copyright Notice 35 Copyright (C) The Internet Society (2005). 37 Abstract 39 This memo documents the result from the RFC 3597 (Handling of Unknown 40 DNS Resource Record Types) interoperability testing. 42 Table of Contents 44 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 45 2. Implementations . . . . . . . . . . . . . . . . . . . . . . . 3 46 3. Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 47 3.1 Authoritative Primary Name Server . . . . . . . . . . . . 3 48 3.2 Authoritative Secondary Name Server . . . . . . . . . . . 3 49 3.3 Full Recursive Resolver . . . . . . . . . . . . . . . . . 4 50 3.4 Stub Resolver . . . . . . . . . . . . . . . . . . . . . . 4 51 3.5 DNSSEC Signer . . . . . . . . . . . . . . . . . . . . . . 4 52 4. Problems found . . . . . . . . . . . . . . . . . . . . . . . . 4 53 5. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 54 6. Normative References . . . . . . . . . . . . . . . . . . . . . 4 55 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 4 56 A. Test zone data . . . . . . . . . . . . . . . . . . . . . . . . 5 57 Intellectual Property and Copyright Statements . . . . . . . . 6 59 1. Introduction 61 This memo documents the result from the RFC 3597 (Handling of Unknown 62 DNS Resource Record Types) interoperability testing. The test was 63 performed during June and July 2004 by request of the IETF DNS 64 Extensions Working Group. 66 2. Implementations 68 The following is a list, in alphabetic order, of implementations 69 tested for compliance with RFC 3597: 71 DNSJava 1.6.4 72 ISC BIND 8.4.5 73 ISC BIND 9.3.0 74 NSD 2.1.1 75 Net::DNS 0.47 patchlevel 1 76 Nominum ANS 2.2.1.0.d 78 These implementations covers the following functions (number of 79 implementations tested for each function in paranthesis): 81 Authoritative Name Servers (4) 82 Full Recursive Resolver (2) 83 Stub Resolver (4) 84 DNSSEC Zone Signers (2) 86 All listed implementations are genetically different. 88 3. Tests 90 The following tests was been performed to validate compliance with 91 RFC 3597 section 3 ("Transparency"), 4 ("Domain Name Compression") 92 and 5 ("Text Representation"). 94 3.1 Authoritative Primary Name Server 96 The test zone data (Appendix A) was loaded into the name server 97 implementation and the server was queried for the loaded information. 99 3.2 Authoritative Secondary Name Server 101 The test zone data (Appendix A) was transferred using AXFR from 102 another name server implementation and the server was queried for the 103 transferred information. 105 3.3 Full Recursive Resolver 107 A recursive resolver was queried for resource records from a domain 108 with the test zone data (Appendix A). 110 3.4 Stub Resolver 112 A stub resolver was used to query resource records from a domain with 113 the test zone data (Appendix A). 115 3.5 DNSSEC Signer 117 A DNSSEC signer was used to sign a zone with test zone data 118 (Appendix A). 120 4. Problems found 122 Two implementations had problems with text presentation of zero 123 length RDATA. 125 One implementation had problems with text presentation of RR type 126 code and classes >= 4096. 128 Bug reports were filed for problems found. 130 5. Summary 132 Unknown type codes works in the tested authoritative servers, 133 recursive resolvers and stub clients. 135 No changes are needed to advance RFC 3597 to draft standard. 137 6. Normative References 139 [1] Gustafsson, A., "Handling of Unknown DNS Resource Record (RR) 140 Types", RFC 3597, September 2003. 142 Author's Address 144 Jakob Schlyter 146 Email: jakob@rfc.se 148 Appendix A. Test zone data 150 ; A-record encoded as TYPE1 151 a TYPE1 \# 4 7f000001 152 a TYPE1 192.0.2.1 153 a A \# 4 7f000002 155 ; draft-ietf-secsh-dns-05.txt 156 sshfp TYPE44 \# 22 01 01 c691e90714a1629d167de8e5ee0021f12a7eaa1e 158 ; bogus test record (from RFC 3597) 159 type731 TYPE731 \# 6 abcd ( 160 ef 01 23 45 ) 162 ; zero length RDATA (from RFC 3597) 163 type62347 TYPE62347 \# 0 165 Intellectual Property Statement 167 The IETF takes no position regarding the validity or scope of any 168 Intellectual Property Rights or other rights that might be claimed to 169 pertain to the implementation or use of the technology described in 170 this document or the extent to which any license under such rights 171 might or might not be available; nor does it represent that it has 172 made any independent effort to identify any such rights. Information 173 on the procedures with respect to rights in RFC documents can be 174 found in BCP 78 and BCP 79. 176 Copies of IPR disclosures made to the IETF Secretariat and any 177 assurances of licenses to be made available, or the result of an 178 attempt made to obtain a general license or permission for the use of 179 such proprietary rights by implementers or users of this 180 specification can be obtained from the IETF on-line IPR repository at 181 http://www.ietf.org/ipr. 183 The IETF invites any interested party to bring to its attention any 184 copyrights, patents or patent applications, or other proprietary 185 rights that may cover technology that may be required to implement 186 this standard. Please address the information to the IETF at 187 ietf-ipr@ietf.org. 189 Disclaimer of Validity 191 This document and the information contained herein are provided on an 192 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 193 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 194 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 195 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 196 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 197 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 199 Copyright Statement 201 Copyright (C) The Internet Society (2005). This document is subject 202 to the rights, licenses and restrictions contained in BCP 78, and 203 except as set forth therein, the authors retain all their rights. 205 Acknowledgment 207 Funding for the RFC Editor function is currently provided by the 208 Internet Society.