draft-ietf-regext-epp-eai-04.txt   draft-ietf-regext-epp-eai-05.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: 3 March 2022 VeriSign, Inc. Expires: 14 June 2022 VeriSign, Inc.
30 August 2021 11 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-04 draft-ietf-regext-epp-eai-05
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 3 March 2022. This Internet-Draft will expire on 14 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
and restrictions with respect to this document. Code Components and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text extracted from this document must include Revised BSD License text as
as described in Section 4.e of the Trust Legal Provisions and are described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License. provided without warranty as described in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Conventions Used in This Document . . . . . . . . . . . . 3 1.1. Conventions Used in This Document . . . . . . . . . . . . 3
2. Migrating to Newer Versions of This Extension . . . . . . . . 3 2. Migrating to Newer Versions of This Extension . . . . . . . . 3
3. Email Address Specification . . . . . . . . . . . . . . . . . 3 3. Email Address Specification . . . . . . . . . . . . . . . . . 3
4. Functional Extension . . . . . . . . . . . . . . . . . . . . 4 4. Functional Extension . . . . . . . . . . . . . . . . . . . . 4
5. Internationalized Email Addresses (EAI) Functional 5. Internationalized Email Addresses (EAI) Functional
Extension . . . . . . . . . . . . . . . . . . . . . . . . 4 Extension . . . . . . . . . . . . . . . . . . . . . . . . 4
5.1. Scope of Functional Extension . . . . . . . . . . . . . . 4 5.1. Scope of Functional Extension . . . . . . . . . . . . . . 4
5.2. Signaling Client and Server Support . . . . . . . . . . . 5 5.2. Signaling Client and Server Support . . . . . . . . . . . 5
5.3. Functional Extension Behavior . . . . . . . . . . . . . . 5 5.3. Functional Extension Behavior . . . . . . . . . . . . . . 5
5.3.1. EAI Functional Extension Negotiated . . . . . . . . . 5 5.3.1. EAI Functional Extension Negotiated . . . . . . . . . 5
5.3.2. EAI Functional Extension Not Negotiated . . . . . . . 6 5.3.2. EAI Functional Extension Not Negotiated . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 7 6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 7 7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 7
7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 7 7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 7
8. Implementation Considerations . . . . . . . . . . . . . . . . 8 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 8.1. Normative References . . . . . . . . . . . . . . . . . . 8
9.1. Normative References . . . . . . . . . . . . . . . . . . 8 8.2. Informative References . . . . . . . . . . . . . . . . . 9
9.2. Informative References . . . . . . . . . . . . . . . . . 9
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
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
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
skipping to change at page 7, line 21 skipping to change at page 7, line 21
* When the email property is optional in the EPP command and the * When the email property is optional in the EPP command and the
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 in the provided email Registries SHOULD validate the domain names syntax in the provided
addresses. This can be done by validating all code points according email addresses. It is RECOMMENDED to validate all code points in
to IDNA2008 [RFC5892]. 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 8, line 15 skipping to change at page 8, line 15
Name of Extension: Use of Internationalized Email Addresses Name of Extension: Use of Internationalized Email Addresses
in EPP protocol in EPP protocol
Document status: Standards Track Document status: Standards Track
Reference: TBA Reference: TBA
Registrant Name and Email Address: IESG, <iesg@ietf.org> Registrant Name and Email Address: IESG, <iesg@ietf.org>
Top-Level Domains(TLDs): Any Top-Level Domains(TLDs): Any
IPR Disclosure: None IPR Disclosure: None
Status: Active Status: Active
Notes: None Notes: None
8. Implementation Considerations 8. References
Registries MAY apply extra limitation to the email address syntax
(e.g. the addresses can be limited to Left-to-Right scripts). These
limitations are out of scope of this document.
9. References
9.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.27487/RFC2119, March 1997, DOI 10.27487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.27487/RFC3688, January 2004, DOI 10.27487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
skipping to change at page 9, line 30 skipping to change at page 9, line 21
2012, <https://www.rfc-editor.org/info/rfc6532>. 2012, <https://www.rfc-editor.org/info/rfc6532>.
[RFC7451] Hollenbeck, S., "Extension Registry for the Extensible [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible
Provisioning Protocol", RFC 7451, DOI 10.27487/RFC7451, Provisioning Protocol", RFC 7451, DOI 10.27487/RFC7451,
February 2015, <https://www.rfc-editor.org/info/rfc7451>. February 2015, <https://www.rfc-editor.org/info/rfc7451>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.27487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.27487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
9.2. Informative References 8.2. Informative References
[RFC5892] Faltstrom, P., Ed., "The Unicode Code Points and [RFC5892] Faltstrom, P., Ed., "The Unicode Code Points and
Internationalized Domain Names for Applications (IDNA)", Internationalized Domain Names for Applications (IDNA)",
RFC 5892, DOI 10.27487/RFC5892, August 2010, RFC 5892, DOI 10.27487/RFC5892, August 2010,
<https://www.rfc-editor.org/info/rfc5892>. <https://www.rfc-editor.org/info/rfc5892>.
[RFC8543] Zhou, L., Kong, N., Yao, J., Gould, J., and G. Zhou, [RFC8543] Zhou, L., Kong, N., Yao, J., Gould, J., and G. Zhou,
"Extensible Provisioning Protocol (EPP) Organization "Extensible Provisioning Protocol (EPP) Organization
Mapping", RFC 8543, DOI 10.27487/RFC8543, March 2019, Mapping", RFC 8543, DOI 10.27487/RFC8543, March 2019,
<https://www.rfc-editor.org/info/rfc8543>. <https://www.rfc-editor.org/info/rfc8543>.
skipping to change at page 10, line 51 skipping to change at page 10, line 43
1. Changed to use a pointed XML namespace with "0.3" instead of 1. Changed to use a pointed XML namespace with "0.3" instead of
"0.2". "0.2".
2. Some wording improvements 2. Some wording improvements
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
1. Some nitpicking
2. The "Implementation considerations" section is removed
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
 End of changes. 11 change blocks. 
23 lines changed or deleted 23 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/