draft-ietf-dnsext-obsolete-iquery-02.txt   draft-ietf-dnsext-obsolete-iquery-03.txt 
DNSEXT Working Group David C Lawrence DNSEXT Working Group David C Lawrence
INTERNET-DRAFT Nominum INTERNET-DRAFT Nominum
<draft-ietf-dnsext-obsolete-iquery-02.txt> December 2001 <draft-ietf-dnsext-obsolete-iquery-03.txt> January 2002
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 14 June 2002. This draft expires on 14 July 2002.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2001). All rights reserved. Copyright (C) The Internet Society (2002). All rights reserved.
Abstract Abstract
Based on a lack of working implementations of the IQUERY method The IQUERY method of performing inverse DNS lookups, specified in
of performing inverse DNS lookups, and because an alternative RFC 1035, has not been generally implemented and has usually been
mechanism for doing inverse queries of address records has been operationally disabled where it has been implemented. Both reflect
successfully used operationally for well over a decade, this a general view in the community that the concept was unwise and
draft proposes that the IQUERY operation be entirely obsoleted. that the widely-used alternate approach of using PTR queries and
reverse-mapping records is preferable. Consequently, this document
deprecates the IQUERY operation and updates RFC 1035 to declare it
entirely obsolete.
1 - Introduction 1 - Introduction
As specified in RFC 1035 (section 6.4), the IQUERY operation for As specified in RFC 1035 (section 6.4), the IQUERY operation for
DNS queries is used to look up the name(s) which are associated DNS queries is used to look up the name(s) which are associated
with the given value. The value being sought is provided in the with the given value. The value being sought is provided in the
query's answer section and the response fills in the question query's answer section and the response fills in the question
section with one or more 3-tuples of type, name and class. section with one or more 3-tuples of type, name and class.
As noted in [RFC1035], section 6.4.3, inverse query processing can As noted in [RFC1035], section 6.4.3, inverse query processing can
skipping to change at page 2, line 52 skipping to change at page 2, line 52
only common reverse mapping support on the Internet, mapping only common reverse mapping support on the Internet, mapping
address records to names, is provided through the use of PTR address records to names, is provided through the use of PTR
records in the in-addr.arpa tree and has served the community well records in the in-addr.arpa tree and has served the community well
for many years. for many years.
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", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" 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
In RFC 1035, sections 4.1.1 is updated in part and section 6.4 is In RFC 1035, sections 4.1.1 is updated in part and section 6.4 is
entirely superseded. 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:
skipping to change at page 3, line 52 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. Matt Crawford, John Klensin and Erik Nordmark 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.
[RFC2119] S. Bradner, ``Key Words for Use in RFCs to Indicate
Requirement Levels'', BCP 14, RFC 2119, March 1997.
7 - Author's Address 7 - Author's Address
David Lawrence David Lawrence
Nominum, Inc. Nominum, Inc.
950 Charter St 950 Charter St
Redwood City CA 94063 Redwood City CA 94063
USA USA
Phone: +1.650.779.6042 Phone: +1.650.779.6042
EMail: tale@nominum.com EMail: tale@nominum.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
 End of changes. 

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