draft-ietf-regext-epp-eai-05.txt   draft-ietf-regext-epp-eai-06.txt 
Network Working Group D. Belyavskiy Network Working Group D. Belyavskiy
Internet-Draft Internet-Draft
Intended status: Standards Track J. Gould Intended status: Standards Track J. Gould
Expires: 14 June 2022 VeriSign, Inc. Expires: 26 June 2022 VeriSign, Inc.
11 December 2021 23 December 2021
Use of Internationalized Email Addresses in the Extensible Provisioning Use of Internationalized Email Addresses in the Extensible Provisioning
Protocol (EPP) Protocol (EPP)
draft-ietf-regext-epp-eai-05 draft-ietf-regext-epp-eai-06
Abstract Abstract
This document describes an EPP extension that permits usage of This document describes an EPP extension that permits usage of
Internationalized Email Addresses in the EPP protocol and specifies Internationalized Email Addresses in the EPP protocol and specifies
the terms when it can be used by EPP clients and servers. The the terms when it can be used by EPP clients and servers. The
Extensible Provisioning Protocol (EPP), being developed before Extensible Provisioning Protocol (EPP), being developed before
appearing the standards for Internationalized Email Addresses (EAI), appearing the standards for Internationalized Email Addresses (EAI),
does not support such email addresses. does not support such email addresses.
skipping to change at page 1, line 41 skipping to change at page 1, line 41
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on 14 June 2022. This Internet-Draft will expire on 26 June 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 45 skipping to change at page 2, line 45
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 9 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 9
A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 9 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 9
A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 9 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 9
A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 10 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 10
A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 10 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 10
A.5. Change from 04 to the regext 01 version . . . . . . . . . 10 A.5. Change from 04 to the regext 01 version . . . . . . . . . 10
A.6. Change from the regext 01 to regext 02 version . . . . . 10 A.6. Change from the regext 01 to regext 02 version . . . . . 10
A.7. Change from the regext 02 to regext 03 version . . . . . 10 A.7. Change from the regext 02 to regext 03 version . . . . . 10
A.8. Change from the regext 03 to regext 04 version . . . . . 10 A.8. Change from the regext 03 to regext 04 version . . . . . 10
A.9. Change from the regext 04 to regext 05 version . . . . . 10 A.9. Change from the regext 04 to regext 05 version . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 A.10. Change from the regext 05 to regext 06 version . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
[RFC6530] introduced the framework for Internationalized Email [RFC6530] introduced the framework for Internationalized Email
Addresses. To make such addresses more widely accepted, the changes Addresses. To make such addresses more widely accepted, the changes
to various protocols need to be introduced. to various protocols need to be introduced.
This document describes an Extensible Provisioning Protocol (EPP) This document describes an Extensible Provisioning Protocol (EPP)
extension that permits usage of Internationalized Email Addresses in extension that permits usage of Internationalized Email Addresses in
the EPP protocol and specifies the terms when it can be used by EPP the EPP protocol and specifies the terms when it can be used by EPP
skipping to change at page 7, line 22 skipping to change at page 7, line 22
email property is an EAI address with no alternative ASCII email property is an EAI address with no alternative ASCII
address, the client SHOULD omit the email property. If the email address, the client SHOULD omit the email property. If the email
property is provided, the client MUST provide an ASCII email property is provided, the client MUST provide an ASCII email
address. The provided email address should provide a way to address. The provided email address should provide a way to
contact the registrant. It can be a secondary ASCII email address contact the registrant. It can be a secondary ASCII email address
or registrar-provided proxy email address. or registrar-provided proxy email address.
6. Security Considerations 6. Security Considerations
Registries SHOULD validate the domain names syntax in the provided Registries SHOULD validate the domain names syntax in the provided
email addresses. It is RECOMMENDED to validate all code points in email addresses to reduce the risk of future usability errors. It is
the domain names according to IDNA2008 [RFC5892]. RECOMMENDED to validate all code points in the domain names according
to IDNA2008 [RFC5892].
7. IANA Considerations 7. IANA Considerations
7.1. XML Namespace 7.1. XML Namespace
This document uses URNs to describe XML namespaces and XML schemas This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism described in RFC 3688 [RFC3688]. conforming to a registry mechanism described in RFC 3688 [RFC3688].
The following URI assignment should be made by IANA: The following URI assignment should be made by IANA:
Registration request for the eai namespace: Registration request for the eai namespace:
skipping to change at page 10, line 49 skipping to change at page 10, line 49
A.8. Change from the regext 03 to regext 04 version A.8. Change from the regext 03 to regext 04 version
1. Some nitpicking 1. Some nitpicking
A.9. Change from the regext 04 to regext 05 version A.9. Change from the regext 04 to regext 05 version
1. Some nitpicking 1. Some nitpicking
2. The "Implementation considerations" section is removed 2. The "Implementation considerations" section is removed
A.10. Change from the regext 05 to regext 06 version
1. Some nitpicking
Authors' Addresses Authors' Addresses
Dmitry Belyavskiy Dmitry Belyavskiy
8 marta st. 8 marta st.
Moscow Moscow
127083 127083
Russian Federation Russian Federation
Phone: +7 916 262 5593 Phone: +7 916 262 5593
Email: beldmit@gmail.com Email: beldmit@gmail.com
James Gould James Gould
 End of changes. 7 change blocks. 
7 lines changed or deleted 14 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/