datatracker.ietf.org
Sign in
Version 5.6.2.p3, 2014-07-31
Report a bug

Changing DNS Operators for DNSSEC signed Zones
draft-koch-dnsop-dnssec-operator-change-06

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2014-02-14
Intended RFC status: Unknown
Other versions: plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Network Working Group                                            P. Koch
Internet-Draft                                                   M. Sanz
Intended status: Standards Track                                DENIC eG
Expires: August 18, 2014                               A.L.J. Verschuren
                                                               SIDN Labs
                                                       February 14, 2014

             Changing DNS Operators for DNSSEC signed Zones
               draft-koch-dnsop-dnssec-operator-change-06

Abstract

   Changing the DNS delegation for a DNS zone is quite involved if done
   by the books, but most often handled pragmatically in today's
   operational practice at the top level with registries and registrars.
   This document describes a delegation change procedure that maintains
   consistency and validation under DNSSEC.

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 http://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 August 18, 2014.

Copyright Notice

   Copyright (c) 2014 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

Koch, et al.            Expires August 18, 2014                 [Page 1]
Internet-Draft           DNSSEC Operator Change            February 2014

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Purpose of this Document  . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Requirements and Assumptions for Seamless Operator Change . .   4
     2.1.  Requirements for Seamless Operator Change . . . . . . . .   4
     2.2.  Assumptions for Seamless Operator Change  . . . . . . . .   5
   3.  Executing the Change  . . . . . . . . . . . . . . . . . . . .   7
     3.1.  Changing DNS operator only  . . . . . . . . . . . . . . .   7
     3.2.  Changing DNS operator and registrar . . . . . . . . . . .   9
     3.3.  Losing operator not participating . . . . . . . . . . . .  10
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  12
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Appendix A.  Document Revision History  . . . . . . . . . . . . .  13
     A.1.  -00 . . . . . . . . . . . . . . . . . . . . . . . . . . .  13
     A.2.  -01 . . . . . . . . . . . . . . . . . . . . . . . . . . .  13
     A.3.  -02 . . . . . . . . . . . . . . . . . . . . . . . . . . .  13
     A.4.  -03 . . . . . . . . . . . . . . . . . . . . . . . . . . .  14
     A.5.  -04 . . . . . . . . . . . . . . . . . . . . . . . . . . .  14
     A.6.  -05 . . . . . . . . . . . . . . . . . . . . . . . . . . .  14
     A.7.  -06 . . . . . . . . . . . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   When the NS RRSet in a DNS delegation is to be changed from one to a
   disjoint other, the most conservative approach would be to add the
   new servers as (stealth) secondary servers, then add them to the NS
   RRSet, change the primary master (that is, change the AXFR/IXFR
   source for all the secondary servers), remove the old name servers'
   names from the NS RRSet and finally cease service on those former
   name servers.  This would involve two changes to the zone file for

[include full document text]