I-D Action: draft-ietf-regext-dnsoperator-to-rrr-protocol-05.txt

internet-drafts@ietf.org Fri, 04 May 2018 15:22 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: regext@ietf.org
Subject: I-D Action: draft-ietf-regext-dnsoperator-to-rrr-protocol-05.txt
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152544733009.11721.17702991095036543588@ietfa.amsl.com>
Date: Fri, 04 May 2018 08:22:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/BcQ2d0F2lNDDb9DcChym6Km3zDA>

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Registration Protocols Extensions WG of the IETF.

        Title           : Third Party DNS operator to Registrars/Registries Protocol
        Authors         : Jacques Latour
                          Olafur Gudmundsson
                          Paul Wouters
                          Matthew Pounsett
	Filename        : draft-ietf-regext-dnsoperator-to-rrr-protocol-05.txt
	Pages           : 15
	Date            : 2018-05-04

Abstract:
   There are several problems that arise in the standard
   Registrant/Registrar/Registry model when the operator of a zone is
   neither the Registrant nor the Registrar for the delegation.
   Historically the issues have been minor, and limited to difficulty
   guiding the Registrant through the initial changes to the NS records
   for the delegation.  As this is usually a one time activity when the
   operator first takes charge of the zone it has not been treated as a
   serious issue.

   When the domain uses DNSSEC it necessary to make regular (sometimes
   annual) changes to the delegation, updating DS record(s) in order to
   track KSK rollover.  Under the current model this is prone to delays
   and errors, as the Registrant must participate in updates to DS
   records.

   This document describes a simple protocol that allows a third party
   DNS operator to: establish the initial chain of trust (bootstrap
   DNSSEC) for a delegation; update DS records for a delegation; and,
   remove DS records from a secure delegation.  The DNS operator may do
   these things in a trusted manner, without involving the Registrant
   for each operation.  This same protocol can be used by Registrants to
   maintain their own domains if they wish.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-regext-dnsoperator-to-rrr-protocol/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-regext-dnsoperator-to-rrr-protocol-05
https://datatracker.ietf.org/doc/html/draft-ietf-regext-dnsoperator-to-rrr-protocol-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-regext-dnsoperator-to-rrr-protocol-05


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

I-D Action: draft-ietf-regext-dnsoperator-to-rrr-… internet-drafts