idnits 2.17.1 draft-ietf-dnsext-interop3597-00.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.5 on line 190. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 174. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 180. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 196), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 34. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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. ** The document seems to lack an RFC 3979 Section 5, para. 1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? 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 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 (August 2, 2004) is 7179 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 132, but no explicit reference was found in the text Summary: 8 errors (**), 0 flaws (~~), 5 warnings (==), 6 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 August 2, 2004 3 Expires: January 31, 2005 5 RFC 3267 Interoperability Report 6 draft-ietf-dnsext-interop3597-00.txt 8 Status of this Memo 10 By submitting this Internet-Draft, I certify that any applicable 11 patent or other IPR claims of which I am aware have been disclosed, 12 and any of which I become aware will be disclosed, in accordance with 13 RFC 3667. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that other 17 groups may also distribute working documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference 22 material or to cite them other than as "work in progress." 24 The list of current Internet-Drafts can be accessed at http:// 25 www.ietf.org/ietf/1id-abstracts.txt. 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html. 30 This Internet-Draft will expire on January 31, 2005. 32 Copyright Notice 34 Copyright (C) The Internet Society (2004). All Rights Reserved. 36 Abstract 38 This memo documents the result from the RFC 3267 (Handling of Unknown 39 DNS Resource Record Types) interoperability testing. 41 Table of Contents 43 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 44 2. Implementations . . . . . . . . . . . . . . . . . . . . . . . 3 45 3. Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 46 3.1 Authoritative Primary Name Server . . . . . . . . . . . . . . 3 47 3.2 Authoritative Secondary Name Server . . . . . . . . . . . . . 3 48 3.3 Full Recursive Resolver . . . . . . . . . . . . . . . . . . . 3 49 3.4 Stub Resolver . . . . . . . . . . . . . . . . . . . . . . . . 3 50 3.5 DNSSEC Signer . . . . . . . . . . . . . . . . . . . . . . . . 4 51 4. Problems found . . . . . . . . . . . . . . . . . . . . . . . . 4 52 5. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 53 Normative References . . . . . . . . . . . . . . . . . . . . . 4 54 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 4 55 A. Test zone data . . . . . . . . . . . . . . . . . . . . . . . . 5 56 Intellectual Property and Copyright Statements . . . . . . . . 6 58 1. Introduction 60 This memo documents the result from the RFC 3267 (Handling of Unknown 61 DNS Resource Record Types) interoperability testing. The test was 62 performed during June and July 2004 by request of the IETF DNS 63 Extensions Working Group. 65 2. Implementations 67 The following is a list, in alphabetic order, of implementations for 68 compliance of RFC 3597: 70 DNSJava 1.6.4 71 ISC BIND 8.4.5rc4 72 ISC BIND 9.3.0rc2 73 NSD 2.1.1 74 Net::DNS 0.47 patchlevel 1 75 Nominum ANS 2.2.1.0.d 77 These implementations covers the following functions (number of 78 implementations tested for each function in paranthesis): 80 Authoritative Name Servers (4) 81 Full Recursive Resolver (2) 82 Stub Resolver (4) 83 DNSSEC Zone Signers (2) 85 3. Tests 87 3.1 Authoritative Primary Name Server 89 The test zone data (Appendix A) was loaded into the name server 90 implementation and the server was queried for the loaded information. 92 3.2 Authoritative Secondary Name Server 94 The test zone data (Appendix A) was transferred using AXFR from 95 another name server implementation and the server was queried for the 96 transferred information. 98 3.3 Full Recursive Resolver 100 A recursive resolver was queried for resource records from a domain 101 with the test zone data (Appendix A). 103 3.4 Stub Resolver 105 A stub resolver was used to query resource records from a domain with 106 the test zone data (Appendix A). 108 3.5 DNSSEC Signer 110 A DNSSEC signer was used to sign a zone with test zone data (Appendix 111 A). 113 4. Problems found 115 Two implementations had problems with text presentation of zero 116 length RDATA. 118 One implementation had problems with text presentation of RR type 119 code and classes >= 4096. 121 Bug reports were filed for problems found. 123 5. Summary 125 Unknown type codes works in the tested authoritative servers, 126 recursive resolvers and stub clients. 128 No changes are needed to advance RFC 3597 to draft standard. 130 Normative References 132 [1] Gustafsson, A., "Handling of Unknown DNS Resource Record (RR) 133 Types", RFC 3597, September 2003. 135 Author's Address 137 Jakob Schlyter 139 EMail: jakob@rfc.se 141 Appendix A. Test zone data 143 ; A-record encoded as TYPE1 144 a TYPE1 \# 4 7f000001 145 a TYPE1 192.0.2.1 146 a A \# 4 7f000002 148 ; draft-ietf-secsh-dns-05.txt 149 sshfp TYPE44 \# 22 01 01 c691e90714a1629d167de8e5ee0021f12a7eaa1e 151 ; bogus test record (from RFC 3597) 152 type731 TYPE731 \# 6 abcd ( 153 ef 01 23 45 ) 155 ; zero length RDATA (from RFC 3597) 156 type62347 TYPE62347 \# 0 158 Intellectual Property Statement 160 The IETF takes no position regarding the validity or scope of any 161 Intellectual Property Rights or other rights that might be claimed to 162 pertain to the implementation or use of the technology described in 163 this document or the extent to which any license under such rights 164 might or might not be available; nor does it represent that it has 165 made any independent effort to identify any such rights. Information 166 on the IETF's procedures with respect to rights in IETF Documents can 167 be found in BCP 78 and BCP 79. 169 Copies of IPR disclosures made to the IETF Secretariat and any 170 assurances of licenses to be made available, or the result of an 171 attempt made to obtain a general license or permission for the use of 172 such proprietary rights by implementers or users of this 173 specification can be obtained from the IETF on-line IPR repository at 174 http://www.ietf.org/ipr. 176 The IETF invites any interested party to bring to its attention any 177 copyrights, patents or patent applications, or other proprietary 178 rights that may cover technology that may be required to implement 179 this standard. Please address the information to the IETF at 180 ietf-ipr@ietf.org. 182 Disclaimer of Validity 184 This document and the information contained herein are provided on an 185 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 186 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 187 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 188 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 189 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 190 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 192 Copyright Statement 194 Copyright (C) The Internet Society (2004). This document is subject 195 to the rights, licenses and restrictions contained in BCP 78, and 196 except as set forth therein, the authors retain all their rights. 198 Acknowledgment 200 Funding for the RFC Editor function is currently provided by the 201 Internet Society.