Use of Internationalized Email Addresses in EPP protocol
draft-belyavskiy-epp-eai-02

Document Type Active Internet-Draft (individual)
Authors Dmitry Belyavsky  , James Gould 
Last updated 2020-11-19
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized (tools) 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                                      D. Belyavskiy
Internet-Draft                                                          
Intended status: Standards Track                                J. Gould
Expires: 22 May 2021                                      VeriSign, Inc.
                                                        18 November 2020

        Use of Internationalized Email Addresses in EPP protocol
                      draft-belyavskiy-epp-eai-02

Abstract

   This document permits usage of Internationalized Email Addresses in
   the EPP protocol.  The Extensible Provisioning Protocol (EPP), being
   developed before appearing the standards for Internationalized Email
   Addresses (EAI), does not support such email addressed.  This
   document describes an EPP extension that allows EAI addresses to be
   used with an EPP object mapping like the EPP contact mapping.

   TO BE REMOVED on turning to RFC: The document is edited in the
   dedicated github repo (https://github.com/beldmit/eppeai).  Please
   send your submissions via GitHub.

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 22 May 2021.

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.

Belyavskiy & Gould         Expires 22 May 2021                  [Page 1]
Internet-Draft              Use of EAI in EPP              November 2020

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Conventions Used in This Document . . . . . . . . . . . .   3
   2.  Migrating to Newer Versions of This Extension . . . . . . . .   3
   3.  Object Attributes . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  <eai:eai> Extension Element . . . . . . . . . . . . . . .   4
     3.2.  [EAI-ADDRESS] Email Value . . . . . . . . . . . . . . . .   4
   4.  Email Address Specification . . . . . . . . . . . . . . . . .   4
   5.  EPP commands mapping  . . . . . . . . . . . . . . . . . . . .   4
     5.1.  EPP Query Commands  . . . . . . . . . . . . . . . . . . .   5
       5.1.1.  EPP <check> Command . . . . . . . . . . . . . . . . .   5
       5.1.2.  EPP <info> command  . . . . . . . . . . . . . . . . .   5
       5.1.3.  EPP <transfer> Command  . . . . . . . . . . . . . . .   6
     5.2.  EPP Transform Commands  . . . . . . . . . . . . . . . . .   7
       5.2.1.  EPP <create> command  . . . . . . . . . . . . . . . .   7
       5.2.2.  EPP <delete> Command  . . . . . . . . . . . . . . . .   8
       5.2.3.  EPP <renew> Command . . . . . . . . . . . . . . . . .   9
       5.2.4.  EPP <transfer> Command  . . . . . . . . . . . . . . .   9
       5.2.5.  EPP <update> command  . . . . . . . . . . . . . . . .   9
   6.  Formal syntax . . . . . . . . . . . . . . . . . . . . . . . .  10
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
     8.1.  XML Namespace . . . . . . . . . . . . . . . . . . . . . .  11
     8.2.  EPP Extension Registry  . . . . . . . . . . . . . . . . .  12
   9.  Implementation Considerations . . . . . . . . . . . . . . . .  12
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  12
     10.2.  Informative References . . . . . . . . . . . . . . . . .  13
   Appendix A.  Change History . . . . . . . . . . . . . . . . . . .  13
     A.1.  Change from 00 to 01  . . . . . . . . . . . . . . . . . .  13
     A.2.  Change from 01 to 02  . . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   RFC 6530 [RFC6530] introduced the framework for Internationalized
Show full document text