DNS Web Service Discovery
draft-hallambaker-web-service-discovery-03

Document Type Active Internet-Draft (individual)
Last updated 2019-10-23
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
Network Working Group                                    P. Hallam-Baker
Internet-Draft                                          October 23, 2019
Intended status: Informational
Expires: April 25, 2020

                       DNS Web Service Discovery
               draft-hallambaker-web-service-discovery-03

Abstract

   This document describes a standardized approach to discovering Web
   Service Endpoints from a DNS name.  Services are advertised using the
   DNS SRV and TXT records and the HTTP Well Known Service conventions.

   This document is also available online at
   http://mathmesh.com/Documents/draft-hallambaker-web-service-
   discovery.html [1] .

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 April 25, 2020.

Copyright Notice

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

Hallam-Baker             Expires April 25, 2020                 [Page 1]
Internet-Draft          DNS Web Service Discovery           October 2019

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     2.2.  Defined Terms . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Service Discovery . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Host Identification . . . . . . . . . . . . . . . . . . .   4
       3.1.1.  SRV Host discovery  . . . . . . . . . . . . . . . . .   4
     3.2.  Service Description . . . . . . . . . . . . . . . . . . .   4
       3.2.1.  TXT Service and Host Description  . . . . . . . . . .   5
     3.3.  Service Selection . . . . . . . . . . . . . . . . . . . .   5
     3.4.  Web Service Endpoint Determination  . . . . . . . . . . .   5
     3.5.  DNS Fallback  . . . . . . . . . . . . . . . . . . . . . .   6
     3.6.  Example . . . . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Further Work  . . . . . . . . . . . . . . . . . . . . . . . .   8
     4.1.  Additional Description Keys . . . . . . . . . . . . . . .   8
     4.2.  Service Scaling . . . . . . . . . . . . . . . . . . . . .   8
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
     6.1.  Well-Known URIs . . . . . . . . . . . . . . . . . . . . .   9
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   9
     7.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .  10
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   Web services are traditionally identified by means of a URI
   specifying a Web Service Endpoint (WSE).  This is approach is
   unsatisfactory in many situations:

   o  Specification of the Web Service requires the transport and
      presentation protocols to be fixed.

   o  The discovery mechanism does not provide support for load
      balancing or fault tolerance.

   o  The identifiers are unsuited for human interaction.

   The last consideration is a particular concern where an account
   identifier is exposed to the user.  Attempts to 'teach' users to use
   URIs as account identifiers have been predictably unsuccessful.

Hallam-Baker             Expires April 25, 2020                 [Page 2]
Internet-Draft          DNS Web Service Discovery           October 2019

   Users expect and require accounts to be of the form user@example.com
   and not http://service.example.com/service/user.

   The Web Service discovery process described in this specification
Show full document text