draft-ietf-dnsext-obsolete-iquery-01.txt   draft-ietf-dnsext-obsolete-iquery-02.txt 
DNSEXT Working Group David C Lawrence DNSEXT Working Group David C Lawrence
INTERNET-DRAFT Nominum INTERNET-DRAFT Nominum
<draft-ietf-dnsext-obsolete-iquery-01.txt> June 2001 <draft-ietf-dnsext-obsolete-iquery-02.txt> December 2001
Updates: RFC 1035 Updates: RFC 1035
Obsoleting IQUERY Obsoleting IQUERY
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at page 1, line 33 skipping to change at page 1, line 33
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
Comments should be sent to the authors or the DNSEXT WG mailing list Comments should be sent to the authors or the DNSEXT WG mailing list
namedroppers@ops.ietf.org. namedroppers@ops.ietf.org.
This draft expires on December 20, 2001. This draft expires on 14 June 2002.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2001). All rights reserved. Copyright (C) The Internet Society (2001). All rights reserved.
Abstract Abstract
Based on a lack of working implementations of the IQUERY method Based on a lack of working implementations of the IQUERY method
of performing inverse DNS lookups, and because an alternative of performing inverse DNS lookups, and because an alternative
mechanism for doing inverse queries of address records has been mechanism for doing inverse queries of address records has been
skipping to change at page 1, line 99 skipping to change at page 3, line 7
Based on all of these factors, this draft proposes that the IQUERY Based on all of these factors, this draft proposes that the IQUERY
operation for DNS servers be officially obsoleted. operation for DNS servers be officially obsoleted.
1.1 - Requirements 1.1 - Requirements
The key words "MUST NOT", "SHOULD", "SHOULD NOT", and "MAY" in this The key words "MUST NOT", "SHOULD", "SHOULD NOT", and "MAY" in this
document are to be interpreted as described in RFC2119. document are to be interpreted as described in RFC2119.
1.2 - Updated documents and sections 1.2 - Updated documents and sections
RFC 1035 sections 4.1.1 and 6.4 are changed. In RFC 1035, sections 4.1.1 is updated in part and section 6.4 is
entirely superseded.
2 - New text for RFC 1035. 2 - New text for RFC 1035.
Section 4.1.1 has the following text to describe opcode 1: Section 4.1.1 has the following text to describe opcode 1:
"1 an inverse query (IQUERY)" "1 an inverse query (IQUERY)"
Is is amended to read: It is now considered to read as follows:
"1 an inverse query (IQUERY) (obsolete)" "1 an inverse query (IQUERY) (obsolete)"
Section 6.4, including all subsections, of RFC 1035 should be Section 6.4, including all subsections, of RFC 1035 should be
considered obsolete and not to be implemented. It is changed to considered obsolete and not to be implemented. The section
read as follows: effectively now reads as follows:
"Inverse queries using the IQUERY opcode were originally described "Inverse queries using the IQUERY opcode were originally described
as the ability to look up the names that are associated with a as the ability to look up the names that are associated with a
particular RR. Their implementation was optional and never particular RR. Their implementation was optional and never
achieved widespread use. Therefore IQUERY is now obsolete, and achieved widespread use. Therefore IQUERY is now obsolete, and
name servers SHOULD return a "Not Implemented" error when an IQUERY name servers SHOULD return a "Not Implemented" error when an IQUERY
request is received." request is received."
4 - Security Considerations: 4 - Security Considerations:
skipping to change at page 1, line 143 skipping to change at page 3, line 52
DNSSEC is extremely difficult without out-on-the-fly digital signing. DNSSEC is extremely difficult without out-on-the-fly digital signing.
5 - IANA Considerations: 5 - IANA Considerations:
The IQUERY opcode of 1 should be permanently retired, not to be The IQUERY opcode of 1 should be permanently retired, not to be
assigned to any future opcode. assigned to any future opcode.
6 - Acknowledgments: 6 - Acknowledgments:
Olafur Gudmundsson was the instigator for this action. Olafur Gudmundsson was the instigator for this action.
Matt Crawford contributed some improved wording to the Introduction. Matt Crawford contributed some improved wording.
References: References:
[RFC1035] P. Mockapetris, ``Domain Names - Implementation and [RFC1035] P. Mockapetris, ``Domain Names - Implementation and
Specification'', STD 13, RFC 1035, November 1987. Specification'', STD 13, RFC 1035, November 1987.
7 - Author's Address 7 - Author's Address
David Lawrence David Lawrence
Nominum, Inc. Nominum, Inc.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/