IMAP Service Extension for Client Identity
draft-yu-imap-client-id-00

Document Type Active Internet-Draft (individual)
Last updated 2018-05-24
Stream (None)
Intended RFC status (None)
Formats plain text 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)
INTERNET-DRAFT                                                  Y. Deion
<draft-yu-imap-client-id-00.txt>                              LinuxMagic
Intended Status: Standards Track
Expires November 24, 2018                                   May 24, 2018

               IMAP Service Extension for Client Identity
                    <draft-yu-imap-client-id-00.txt>    

Abstract

   This document defines an Internet Message Access Protocol (IMAP)
   service extension called "CID" which provides a method for clients to
   indicate an identity to the server.

   This identity is an additional token that may be used for security
   and/or informational purposes, and with it a server may optionally
   apply heuristics using this token.

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), its areas,
   and its working groups.  Note that other groups may also distribute
   working documents as Internet-Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

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
   (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.

Yu, Deion                Expires November 24, 2018              [Page 1]
INTERNET-DRAFT            IMAP Client Identity              May 24, 2018

Table of Contents

   1.  Introduction .................................................  2
   2.  Conventions Used in This Document ............................  3
   3.  CID ..........................................................  3
     3.1.  CID Command ..............................................  3
     3.2.  CID Arguments ............................................  3
     3.3. Advertising the CID capability ............................  4
     3.4. Restrictions on the CID command ...........................  4
   4.  Formal Syntax ................................................  4
   5.  Discussion ...................................................  5
     5.1.  Applying heuristics to CID ...............................  5
     5.2. Utility of CID ............................................  5
     5.3. Use Cases of CID ..........................................  6
     5.4. Other IMAP Client Identifiers .............................  6
     5.5. Future Considerations .....................................  7
   6.  Client Identity Types ........................................  7
   7.  Examples .....................................................  8
     7.1.  UUID as Client Identity ..................................  8
     7.2.  Malformed CID Command ....................................  8
     7.3.  Client Identity Without a TLS/SSL Session ................  9
     7.4.  Client Identity Leading to Rejection .....................  9
   8.  Security Considerations ......................................  9
   9.  IANA Considerations .......................................... 10
   10. References ................................................... 10
     10.1. Normative References ..................................... 10
   Contributors ..................................................... 10   
   Authors' Addresses ............................................... 10

1. Introduction

   The [IMAP] protocol and its extensions describe methods whereby an
   client may provide identity and/or authentication information to
   an IMAP server.  However, these existing methods are subject to
   limitations and none offer a way to identify the IMAP client with
   absolute confidence.  This document defines an IMAP service extension
   to provide an additional identity token which can represent the IMAP
   client with a higher degree of certainty when accessing the IMAP
   server.

   Typically IMAP clients enter the authenticated state by using either
   the AUTHENTICATE or LOGIN command.  IMAP servers are often subject to
   malicious clients attempting to use authorization credentials and/or
Show full document text