wdiff draft-sury-deprecate-obsolete-resource-records-00.txt draft-sury-deprecate-obsolete-resource-records-01.txt


dnsop                                                            O. Sury
Internet-Draft                               Internet Systems Consortium                                                   E. Hunt
Updates: 1035 1035,3597,4035 (if approved)                               March 22, 2018        Internet Systems Consortium
Intended status: Standards Track                            May 13, 2019
Expires: September 23, 2018 November 14, 2019

            Deprecating obsolete DNS Resource Records
           draft-sury-deprecate-obsolete-resource-records-00 Types
           draft-sury-deprecate-obsolete-resource-records-01

Abstract

   This document deprecates Resource Records (RR) Types that are neither either
   not being used for anything meanigful nor meaningful or were been already made
   obsolete by other RFCs.  This document updates [RFC1035]. [RFC1035], [RFC1035],
   [RFC4034].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 23, 2018. November 14, 2019.

Copyright Notice

   Copyright (c) 2018 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Deprecating MD, MF, MB, MG, MF, MINFO MR, MINFO, MAILA, and WKS Resource Records MAILBRR
       Types . . . . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   2
   4.  Implementation Considerations . . . . . . . . . . . . . . . .   3
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   5.
   6.  Operational Considerations  . . . . . . . . . . . . . . . . .   3
   6.   4
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   3
   7.   4
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     7.1.   4
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   3
     7.2.   4
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   3
   Author's Address  .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   The

   [RFC1035] defines couple of old resource records that are not
   being used, and they other documents have defined some Resource Record (RR)
   Types that are causing operational no longer in common use, some of which have been
   rendered obsolete by subsequent standards, but have never been
   clearly deprecated in the context of the DNS.  In some cases there
   have been interoperability problems between DNS implementations that
   support them these types and those that don't supported them due do not - for example, because of
   DNS name compression on in the wire. wire format.  Continued support for these
   RR Types imposes a complexity cost on new implementations for little
   benefit.

   This document formally deprecates such records
   to allow the RR Types, allowing
   implementations to drop the specific support for such
   records. them.

2.  Deprecating MD, MF, MB, MG, MF, MINFO MR, MINFO, MAILA, and WKS Resource Records MAILBRR Types

   The MD, MF, MB, MG, MF, MR, MINFO, MAILA, and WKS Resource Records MAILB RR Types aren't used
   in any existing standards, and this documents deprecates the their usage.
   The DNS
   implementations compliant with MD, MF, MB, MG, MR, and MINFO RR Types RDATA contain a domain
   name that could be compressed in the RDATA section.

   As an update to [RFC3597] and [RFC4034] this document MUST NOT implement specifies that
   for MD, MF, MB, MG, MF, WKS, MR, and MINFO Resource Records RR types, the canonical form is
   such that no downcasing of embedded domain names takes place, and treat them as a generic
   type effectively disabling is
   otherwise identical to the compression canonical form specified in those types. [RFC4034]
   section 6.2.

3.  IANA Considerations

   This documents updates the IANA registry "Domain Name System (DNS)
   Parameters" ([DNS-IANA]).

   +-------+-------+-------------------------------------+-------------+

              +-------+-------+------------+---------------+
              | TYPE  | Value | Meaning    | Reference     |
   +-------+-------+-------------------------------------+-------------+
              +-------+-------+------------+---------------+
              | MB MD    | 7 3     | a mailbox domain name (OBSOLETE) DEPRECATED | This        |
   |       |       |                                     | document |
              | MG MF    | 8 4     | a mail group member (OBSOLETE) DEPRECATED | This        |
   |       |       |                                     | document |
              | MR MB    | 9 7     | a mail rename domain name DEPRECATED | This        |
   |       |       | (OBSOLETE)                          | document |
              | WKS MG    | 11 8     | a well known service description DEPRECATED | This document |
              | MR    | 9     | (OBSOLETE) DEPRECATED | This document |
              | MINFO | 14    | mailbox or mail list information DEPRECATED | This        |
   |       |       | (OBSOLETE)                          | document |
   +-------+-------+-------------------------------------+-------------+
              +-------+-------+------------+---------------+

4.  Implementation Considerations

   Types will be flagged as obsolete/deprecated in the IANA registry,
   and the following guidance is given to DNS implementors in the
   handling of obsolete/deprecated RR types:

   1.  Authoritative DNS Servers SHOULD issue a warning when loading
       zones that contain DEPRECATED RR Types;

   2.  DNS Servers MUST NOT compress RDATA when rendering DEPRECATED RR
       Types to wire format;

   3.  Recursive DNS Servers MAY support legacy compression in
       DEPRECATED RR Types for received data for backward compatibility
       if desired, but SHOULD warn if such information is received.
       Compressed RDATA in DEPRECATED RR Types MUST be uncompressed
       before sending and they MUST NOT be re-transmitted;

   4.  DNS Clients which receive DEPRECATED RR Types MAY interpret them
       as unknown RR types ([RFC3597]), and MUST NOT interfere with
       their transmission;

   5.  DNSSEC Validators and Signers SHOULD treat RDATA for DEPRECATED
       RR Types as opaque with respect to canonical RR ordering and
       deduplication;

   6.  DEPRECATED RR Types MUST never be treated as a known-type with
       respect to the wire protocol.

5.  Security Considerations

   This document has not no security considerations.

5.

6.  Operational Considerations

   The various status varying states of implementation of MD, MF, MB, MG, MR, MINFO, and WKS
   records is MINFO
   RR Types has already causing caused operational problems between DNS
   implementations that do implement the aforementioned types and those who
   that don't because of mandatory DNS compression on the wire.  This document
   aims to rectify the situation by removing the encouraging removal of support for
   all the these RR types in DNS implementations.  This should not cause any
   signficant operational problems because the these records aren't actually are not in wide
   use on the Internet.  [COMMENT: Some data?]

6.

7.  Acknowledgements

   Peter van Dijk for poking me to write the draft.  Daniel Salzman for
   reviewing the document.

7.  Evan Hunt and Michael Casadevall to write
   Implementation Considerations section.

8.  References

7.1.

8.1.  Normative References

   [RFC1035]  Mockapetris, P., "Domain names - implementation and
              specification", STD 13, RFC 1035, DOI 10.17487/RFC1035,
              November 1987, <https://www.rfc-editor.org/info/rfc1035>.

7.2.

   [RFC3597]  Gustafsson, A., "Handling of Unknown DNS Resource Record
              (RR) Types", RFC 3597, DOI 10.17487/RFC3597, September
              2003, <https://www.rfc-editor.org/info/rfc3597>.

   [RFC4034]  Arends, R., Austein, R., Larson, M., Massey, D., and S.
              Rose, "Resource Records for the DNS Security Extensions",
              RFC 4034, DOI 10.17487/RFC4034, March 2005,
              <https://www.rfc-editor.org/info/rfc4034>.

8.2.  Informative References

   [DNS-IANA]
              "Domain Name System (DNS) Parameters",
              <https://www.iana.org/assignments/dns-parameters/
              dns-parameters.xhtml>.

Author's Address

Authors' Addresses

   Ondrej Sury
   Internet Systems Consortium
   CZ

   EMail: ondrej@isc.org
   Evan Hunt
   Internet Systems Consortium
   US

   EMail: each@isc.org