Domain Connect API - Communications between DNS Provider and Services
draft-carney-regext-domainconnect-03

Document Type Active Internet-Draft (individual)
Last updated 2018-01-18
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Registration Protocols Extensions                               A. Blinn
Internet-Draft                                                 R. Carney
Intended status: Informational                              GoDaddy Inc.
Expires: July 22, 2018                                  January 18, 2018

 Domain Connect API - Communications between DNS Provider and Services
                  draft-carney-regext-domainconnect-03

Abstract

   This document provides information related to the Domain Connect API
   that was built to support communications between DNS Providers and
   Service Providers (hosting, social, email, hardware, etc.).

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 July 22, 2018.

Copyright Notice

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

Blinn & Carney            Expires July 22, 2018                 [Page 1]
Internet-Draft               Domain Connect                 January 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  The API . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  The Synchronous Flow  . . . . . . . . . . . . . . . . . .   5
     4.2.  The Asynchorous Flow  . . . . . . . . . . . . . . . . . .   6
     4.3.  DNS Provider Initiated Flows  . . . . . . . . . . . . . .   6
     4.4.  DNS Provider Discovery  . . . . . . . . . . . . . . . . .   7
     4.5.  Domain Connect Details  . . . . . . . . . . . . . . . . .   8
       4.5.1.  Synchronous Flow  . . . . . . . . . . . . . . . . . .   9
         4.5.1.1.  Query Supported Template  . . . . . . . . . . . .   9
         4.5.1.2.  Apply Template  . . . . . . . . . . . . . . . . .   9
         4.5.1.3.  Security Considerations . . . . . . . . . . . . .  10
       4.5.2.  Asynchronous Flow: OAuth  . . . . . . . . . . . . . .  12
         4.5.2.1.  Getting an Authorization Code . . . . . . . . . .  12
         4.5.2.2.  Requesting an Access Token  . . . . . . . . . . .  13
         4.5.2.3.  Making Requests with Access Tokens  . . . . . . .  14
         4.5.2.4.  Apply Template to Domain  . . . . . . . . . . . .  15
         4.5.2.5.  Revert Template . . . . . . . . . . . . . . . . .  16
         4.5.2.6.  Revoke Access . . . . . . . . . . . . . . . . . .  17
     4.6.  Domain Connect Objects and Templates  . . . . . . . . . .  17
     4.7.  Operational and Implementation Considerations . . . . . .  19
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  23
     5.1.  XML Namespace . . . . . . . . . . . . . . . . . . . . . .  23
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  23
   7.  Change History  . . . . . . . . . . . . . . . . . . . . . . .  23
     7.1.  Change from 02 to 03  . . . . . . . . . . . . . . . . . .  23
     7.2.  Change from 01 to 02  . . . . . . . . . . . . . . . . . .  23
     7.3.  Change from 00 to 01  . . . . . . . . . . . . . . . . . .  23
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .  23
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  24

1.  Introduction

   Configuring a service at a Service Provider to work with a domain has
   historically been a complex task that is difficult for users.

   Typically, a customer would try to configure their service by
   entering their domain name with the Service Provider.  The Service
   Provider then used a number of techniques with mixed reliability to
   discover the DNS Provider.  This might include DNS queries for
   nameservers, queries to whois, and mapping tables to determine the
   registrar or the company providing DNS.
Show full document text