draft-ietf-regext-epp-eai-13.txt   draft-ietf-regext-epp-eai-14.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: 17 December 2022 VeriSign, Inc. Expires: 29 December 2022 VeriSign, Inc.
15 June 2022 27 June 2022
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-13 draft-ietf-regext-epp-eai-14
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 the Extensible Provisioning Protocol (EPP), being developed before the
standards for Internationalized Email Addresses (EAI), does not standards for Internationalized Email Addresses (EAI), does not
support such email addresses. 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 17 December 2022. This Internet-Draft will expire on 29 December 2022.
Copyright Notice Copyright Notice
Copyright (c) 2022 IETF Trust and the persons identified as the Copyright (c) 2022 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 3, line 7 skipping to change at page 3, line 7
A.8. Change from the regext 03 to regext 04 version . . . . . 12 A.8. Change from the regext 03 to regext 04 version . . . . . 12
A.9. Change from the regext 04 to regext 05 version . . . . . 12 A.9. Change from the regext 04 to regext 05 version . . . . . 12
A.10. Change from the regext 05 to regext 06 version . . . . . 12 A.10. Change from the regext 05 to regext 06 version . . . . . 12
A.11. Change from the regext 06 to regext 07 version . . . . . 12 A.11. Change from the regext 06 to regext 07 version . . . . . 12
A.12. Change from the regext 07 to regext 08 version . . . . . 12 A.12. Change from the regext 07 to regext 08 version . . . . . 12
A.13. Change from the regext 08 to regext 09 version . . . . . 13 A.13. Change from the regext 08 to regext 09 version . . . . . 13
A.14. Change from the regext 09 to regext 10 version . . . . . 13 A.14. Change from the regext 09 to regext 10 version . . . . . 13
A.15. Change from the regext 10 to regext 11 version . . . . . 13 A.15. Change from the regext 10 to regext 11 version . . . . . 13
A.16. Change from the regext 11 to regext 12 version . . . . . 13 A.16. Change from the regext 11 to regext 12 version . . . . . 13
A.17. Change from the regext 12 to regext 13 version . . . . . 13 A.17. Change from the regext 12 to regext 13 version . . . . . 13
A.18. Change from the regext 13 to regext 14 version . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
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 3, line 48 skipping to change at page 3, line 49
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
2. Migrating to Newer Versions of This Extension 2. Migrating to Newer Versions of This Extension
Servers that implement this extension SHOULD provide a way for Servers that implement this extension SHOULD provide a way for
clients to progressively update their implementations when a new clients to progressively update their implementations when a new
version of the extension is deployed. A newer version of the version of the extension is deployed. A newer version of the
extension is expected to use an XML namespace with a higher version extension is expected to use an XML namespace URI with a higher
number than the prior versions. version number than the prior versions.
3. Email Address Specification 3. Email Address Specification
Support of non-ASCII email address syntax is defined in RFC 6530 Support of non-ASCII email address syntax is defined in RFC 6530
[RFC6530]. This mapping does not prescribe minimum or maximum [RFC6530]. This mapping does not prescribe minimum or maximum
lengths for character strings used to represent email addresses. The lengths for character strings used to represent email addresses. The
exact syntax of such addresses is described in Section 3.3 of exact syntax of such addresses is described in Section 3.3 of
[RFC6531]. The validation rules introduced in RFC 6531 MUST be [RFC6531]. The validation rules introduced in RFC 6531 MUST be
followed when processing this extension. followed when processing this extension.
skipping to change at page 7, line 31 skipping to change at page 7, line 31
address providing a way to contact the registrant, the client MUST address providing a way to contact the registrant, the client MUST
omit the email property. If the email property is provided, the omit the email property. If the email property is provided, the
client MUST provide an ASCII email address. The provided address client MUST provide an ASCII email address. The provided address
can be an extra ASCII email address collected by registrar or can be an extra ASCII email address collected by registrar or
registrar-provided proxy email address. registrar-provided proxy email address.
6. IANA Considerations 6. IANA Considerations
6.1. XML Namespace 6.1. XML Namespace
This document uses URNs to describe XML namespaces and XML schemas This document uses URNs to describe XML namespaces conforming to a
conforming to a registry mechanism described in RFC 3688 [RFC3688]. registry mechanism described in RFC 3688 [RFC3688]. The following
The following URI assignment should be made by IANA: URI assignment should be made by IANA:
Registration request for the eai namespace: Registration request for the eai namespace:
URI: urn:ietf:params:xml:ns:epp:eai-1.0 URI: urn:ietf:params:xml:ns:epp:eai-1.0
Registrant Contact: IESG Registrant Contact: IESG
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
6.2. EPP Extension Registry 6.2. EPP Extension Registry
The EPP extension described in this document should be registered by The EPP extension described in this document should be registered by
skipping to change at page 13, line 25 skipping to change at page 13, line 25
1. Nitpicking according mostly GenArt review. 1. Nitpicking according mostly GenArt review.
A.16. Change from the regext 11 to regext 12 version A.16. Change from the regext 11 to regext 12 version
1. XML schema registration request removed. 1. XML schema registration request removed.
A.17. Change from the regext 12 to regext 13 version A.17. Change from the regext 12 to regext 13 version
1. Document updated according to SecDir and ART-ART review. 1. Document updated according to SecDir and ART-ART review.
A.18. Change from the regext 13 to regext 14 version
1. Document updated according the IANA review #1231866.
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. 7 change blocks. 
9 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/