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

Document Type Active Internet-Draft (individual)
Author Dmitry Belyavsky 
Last updated 2020-10-11
Stream (None)
Intended RFC status (None)
Formats plain text 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                                          October 11, 2020
Intended status: Standards Track
Expires: April 14, 2021

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

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 in contact mapping in the EPP protocol.

   TO BE REMOVED on turning to RFC: The document is edited in the
   dedicated github repo [1].  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 April 14, 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.  Please review these documents
   carefully, as they describe your rights and restrictions with respect

Belyavskiy               Expires April 14, 2021                 [Page 1]
Internet-Draft              Use of EAI in EPP               October 2020

   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 . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  EAI email address . . . . . . . . . . . . . . . . . . . .   3
     3.2.  [EAI-DUMMY] email value . . . . . . . . . . . . . . . . .   4
   4.  Email Address specification . . . . . . . . . . . . . . . . .   4
   5.  EPP commands mapping  . . . . . . . . . . . . . . . . . . . .   4
     5.1.  EPP <create> command  . . . . . . . . . . . . . . . . . .   4
     5.2.  EPP <update> command  . . . . . . . . . . . . . . . . . .   5
     5.3.  EPP <info> command  . . . . . . . . . . . . . . . . . . .   6
   6.  Formal syntax . . . . . . . . . . . . . . . . . . . . . . . .   8
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
     8.1.  XML Namespace . . . . . . . . . . . . . . . . . . . . . .  10
     8.2.  EPP Extension Registry  . . . . . . . . . . . . . . . . .  10
   9.  Implementation Considerations . . . . . . . . . . . . . . . .  10
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     10.2.  Informative References . . . . . . . . . . . . . . . . .  11
     10.3.  URIs . . . . . . . . . . . . . . . . . . . . . . . . . .  12
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   RFC 6530 [RFC6530] introduced the framework for Internationalized
   Email Addresses.  To make such addresses more widely accepted, the
   changes to various protocols need to be introduced.

   This document describes an Extensible Provisioning Protocol (EPP)
   extension for using the Email Addresses Internationalized (EAI) in
   contact object mapping descibed in RFC 5733 [RFC5733].

   The Extensible Provisioning Protocol (EPP) specified in RFC 5730
   [RFC5730] is a base document for object management operations and an
   extensible framework that maps protocol operations to objects.  The
   specifics of various objects managed via EPP is described in separate
   documents, RFC 5731 [RFC5731], RFC 5732 [RFC5732], RFC 5733
   [RFC5733], and RFC 5734 [RFC5734].

Belyavskiy               Expires April 14, 2021                 [Page 2]
Internet-Draft              Use of EAI in EPP               October 2020
Show full document text