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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-06-07
Stream (None)
Intended RFC status (None)
Formats pdf htmlized 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: November 27, 2016                                  May 26, 2016

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

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 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 November 27, 2016.

Copyright Notice

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

Blinn & Carney          Expires November 27, 2016               [Page 1]
Internet-Draft               Domain Connect                     May 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  The API . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Web-Based Authentication, Authorization & Template Action
           Flow  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     4.2.  OAuth Based Authentication and Authorization Flow . . . .   5
     4.3.  DNS Provider Initiated Flows  . . . . . . . . . . . . . .   6
     4.4.  DNS Provider Discovery  . . . . . . . . . . . . . . . . .   6
     4.5.  Domain Connect Endpoints  . . . . . . . . . . . . . . . .   7
       4.5.1.  Web Based Flow  . . . . . . . . . . . . . . . . . . .   8
       4.5.2.  OAuth Flow  . . . . . . . . . . . . . . . . . . . . .   9
         4.5.2.1.  Getting an Authorization Token  . . . . . . . . .  10
         4.5.2.2.  Requesting an Access Token  . . . . . . . . . . .  10
         4.5.2.3.  Making Requests with Access Tokens  . . . . . . .  11
         4.5.2.4.  Apply Template to Domain  . . . . . . . . . . . .  11
         4.5.2.5.  Revert Template . . . . . . . . . . . . . . . . .  13
         4.5.2.6.  Revoke Access . . . . . . . . . . . . . . . . . .  13
     4.6.  Domain Connect Objects and Templates  . . . . . . . . . .  13
     4.7.  Implementation Notes  . . . . . . . . . . . . . . . . . .  15
     4.8.  Operational and Implementation Considerations . . . . . .  18
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  19
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  19
   7.  Change History  . . . . . . . . . . . . . . . . . . . . . . .  19
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .  19
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  20

1.  Introduction

   Configuring a service at a Service Provider to work with a domain is
   a complex task and is difficult for users.

   Typically a customer will try to configure their service by entering
   their domain name with the Service Provider.  The Service Provider
   then uses a number of techniques to discover the DNS Provider.  This
   might include DNS queries to determine the registrar and/or the
   nameserver providing DNS.

   Once the Service Provider discovers the DNS Provider, they typically
   give the customer instructions for proper configuration of DNS.  This
   might include help text, screen shots, or even links to the
   appropriate tools.

   This often presents a number of technologies or processes to the user
   that they may not understand.  DNS record types, TTLs, Hostnames,
   etc. are all confusing to many users.  Instructions authored by the
Show full document text