INTERNET-DRAFT                                                Bill Manning
Intended Status: Proposed Standard                               zDNS Ltd.
Expires: 2015-10-15                                             2015-05-27

                              RFC2181 to Historic
                   draft-pfrc-rfc2181-historic-issues-00
Abstract

   RFC 2181 is an amalgamation of eight independent components that were 
   lumped together into a single document, ostensibly because none were of
   enough interest to create a standalone reference for each idea.  After 
   nearly two decades, and a number of RFCs that update portions of RFC 2181,
   it seems reasonable to move RFC 2181 to historic status and focus on each
   idea independentally.  This document introduces eight standalone docuements,
   one for each of the ideas collected in RFC 2181 and allows for examination
   of each idea independently.   In doing so, this document moves RFC 2181
   to historic status.

Status of this Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Copyright and License Notice

   Copyright (c) 2015 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
   (http://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  . . . . . . . . . . . . . . . . . . . . . . . . .  1
   2  Terminology . . . . . . . . . . . . . . . . . . . . . . . . . .  1
   3  RFC 2181 as Historic . . . . . . . .  . . . . . . . . . . . . .  1
   4  Security Considerations . . . . . . . . . . . . . . . . . . . .  1
   5  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .   2
   6  References  . . . . . . . . . . . . . . . . . . . . . . . . . .  2
   7  Authors' Addresses . . . . . . . . . . . . . . . . . . . . .

1  Introduction

   [RFC2181] discusses eight independent protocol specification ambiguities 
   and suggests normalized or clarified responses to resolve the concerns
   and lead to better interoperablity for the servers and resolvers using the
   Internet's domain name system (DNS) protocol [RFC1035].  Since its publication, 
   both protocol and operational considerations have evolved.  It makes more 
   sense now to separate the eight items into separate documents.  The eight
   elements requirements are defined in [DRAFT001-008] and are taken verbatum 
   from [RFC2181].  This document introduces these new specifications.
   
2  Terminology

   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 RFC 2119.

3   RFC 2181 as Historic

   This document obsoletes and reclassifies [RFC2181] as Historic.

   This document and [DRAFT001-008] together functionally replace
   [RFC2181].

4  Security Considerations

   It is not believed that anything in this document adds to any
   security issues that may exist with the DNS, nor does it do anything
   to that will necessarily lessen them.  Correct implementation of the
   DNS specifications might play some small part in a robust, reliable 
   naming system, but as with all tools, they are intrinsically neutral.
   Security is always in the perception of the beholder.

5   IANA Considerations

   This document has no action for IANA.

6  References

   [RFC2181]  Elz, R., Bush, R., ,
              RFC 2181, July 1997.
 
   [RFC1034]  Mockapetris, P., "Domain names - concepts and facilities",
              STD 13, RFC 1034, November 1987.

   [RFC1035]  Mockapetris, P., "Domain names - implementation and
              specification", STD 13, RFC 1035, November 1987.

   [DRAFT-001] Ma, D. Ed., draft-pfrc-2181-soa-records-00, May 2015

   [DRAFT-002] Ma, D. Ed., draft-pfrc-2181-handling-zone-cuts-00, May 2015

   [DRAFT-003] Ma, D. Ed., draft-pfrc-2181-ttl-00, May 2015

   [DRAFT-004] Ma, D. Ed., draft-pfrc-2181-tc-bit-00, May 2015

   [DRAFT-005] Ma, D. Ed., draft-pfrc-2181-resource-record-sets-00, May 2015

   [DRAFT-006] Ma, D. Ed., draft-pfrc-2181-name-syntax-00, May 2015

   [DRAFT-007] Ma, D. Ed., draft-pfrc-2181--naming-issues-00,, May 2015

   [DRAFT-008] Ma, D. Ed., draft-pfrc-2181-source-address-selection-00, May 2015
   

7  Authors' Addresses

   Bill Manning
   PO Box 12317,	Marina del Rey, CA 90295