Login Security Extension for the Extensible Provisioning Protocol (EPP)
RFC 8807

Document Type RFC - Proposed Standard (August 2020; No errata)
Authors James Gould  , Matthew Pozun 
Last updated 2020-08-07
Replaces draft-gould-regext-login-security
Stream Internet Engineering Task Force (IETF)
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Joseph Yee
Shepherd write-up Show (last changed 2020-01-31)
IESG IESG state RFC 8807 (Proposed Standard)
Action Holders
Consensus Boilerplate Yes
Telechat date
Responsible AD Barry Leiba
Send notices to Joseph Yee <jyee@afilias.info>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
IANA expert review state Expert Reviews OK

Internet Engineering Task Force (IETF)                          J. Gould
Request for Comments: 8807                                      M. Pozun
Category: Standards Track                                 VeriSign, Inc.
ISSN: 2070-1721                                              August 2020

Login Security Extension for the Extensible Provisioning Protocol (EPP)


   The Extensible Provisioning Protocol (EPP) includes a client
   authentication scheme that is based on a user identifier and
   password.  The structure of the password field is defined by an XML
   Schema data type that specifies minimum and maximum password length
   values, but there are no other provisions for password management
   other than changing the password.  This document describes an EPP
   extension that allows longer passwords to be created and adds
   additional security features to the EPP login command and response.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at

Copyright Notice

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

Table of Contents

   1.  Introduction
     1.1.  Conventions Used in This Document
   2.  Migrating to Newer Versions of This Extension
   3.  Object Attributes
     3.1.  Event
     3.2.  "[LOGIN-SECURITY]" Password
     3.3.  Dates and Times
   4.  EPP Command Mapping
     4.1.  EPP <login> Command
   5.  Formal Syntax
     5.1.  Login Security Extension Schema
   6.  IANA Considerations
     6.1.  XML Namespace
     6.2.  EPP Extension Registry
   7.  Security Considerations
   8.  References
     8.1.  Normative References
     8.2.  Informative References
   Authors' Addresses

1.  Introduction

   This document describes an Extensible Provisioning Protocol (EPP)
   extension for enhancing the security of the EPP login command in EPP
   [RFC5730].  EPP [RFC5730] includes a maximum password length of 16
   characters, which inhibits implementing stronger password security
   policies with higher entropy.  The enhancements include supporting
   longer passwords (or passphrases) than the 16-character maximum and
   providing a list of security events in the login response.  The
   password (current and new) in EPP [RFC5730] can be overridden by the
   password included in the extension to extend past the 16-character
   maximum.  The security events supported include password expiry,
   client certificate expiry, insecure cipher, insecure TLS protocol,
   new password complexity, login security statistical warning, and a
   custom event.  The attributes supported by the security events
   include an identified event type or a subtype, an indicated security
   level of warning or error, a future or past-due expiration date, the
   value that resulted in the event, the duration of the statistical
   event, and a free-form description with an optional language.

1.1.  Conventions Used in This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "OPTIONAL" in this document are to be interpreted as described in
   BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

   XML is case sensitive.  Unless stated otherwise, XML specifications
   and examples provided in this document MUST be interpreted in the
   character case presented in order to develop a conforming

   In examples, "C:" represents lines sent by a protocol client and "S:"
   represents lines returned by a protocol server.  In examples,
   indentation and whitespace are provided only to illustrate element
   relationships and are not a required feature of this protocol.

   "loginSec-1.0" is used as an abbreviation for
   "urn:ietf:params:xml:ns:epp:loginSec-1.0".  The XML namespace prefix
   "loginSec" is used, but implementations MUST NOT depend on it.
Show full document text