WebFinger Email Automatic Configuration
draft-jones-webfinger-email-autoconfig-00

Document Type Active Internet-Draft (individual)
Last updated 2019-07-08
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. Jones
Internet-Draft                                              G. Salgueiro
Intended status: Standards Track                                   Cisco
Expires: January 9, 2020                                    July 8, 2019

                WebFinger Email Automatic Configuration
               draft-jones-webfinger-email-autoconfig-00

Abstract

   This document describes procedures for automatically configuring an
   email client by using WebFinger to convey mail server configuration
   and security-related information.

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 January 9, 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Jones & Salgueiro        Expires January 9, 2020                [Page 1]
Internet-Draft     WebFinger Email Autoconfigiguration         July 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions Used in This Document . . . . . . . . . . . . . .   2
   3.  Example User Scenario . . . . . . . . . . . . . . . . . . . .   3
   4.  Email Auto-Configuration Procedures . . . . . . . . . . . . .   5
     4.1.  Initiating a WebFinger Query  . . . . . . . . . . . . . .   5
     4.2.  Processing the JSON Resource Descriptor . . . . . . . . .   5
     4.3.  Requesting the Email Configuration Document . . . . . . .   5
   5.  Email Configuration Document Syntax . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   6
     9.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Configuring email clients manually can be a time-consuming and
   mundane task that can actually be fairly arduous as the number of
   users or clients increases.  While people with technical
   understanding of the various protocols and settings employed can
   configure a single email client fairly easily, the task can prove
   challenging and frustrating for non-technical users.

   This document defines procedures utilizing WebFinger [RFC7033] that
   make it trivial for end-users to configure email clients with little
   or no assistance and with minimal technical skill.  All that is
   required for the user to do is enter his or her account identifier,
   select an email account, and provide credentials.

   Following these procedures, the complexity of configuring an email
   client is shifted away from the end-user and pushed onto the software
   tools that implement these procedures and the email administrators
   who would have to configure the settings for each user server-side
   and publish the required configuration data.  However, the
   configuration data can be generated with automated tools, meaning
   there would be minimal effort for the email administrators.

2.  Conventions Used in This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP

Jones & Salgueiro        Expires January 9, 2020                [Page 2]
Internet-Draft     WebFinger Email Autoconfigiguration         July 2019

   14 [RFC2119] [RFC8174] when, and only when, they appear in all
Show full document text