draft-ietf-regext-epp-eai-06.txt   draft-ietf-regext-epp-eai-07.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: 26 June 2022 VeriSign, Inc. Expires: 25 July 2022 VeriSign, Inc.
23 December 2021 21 January 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-06 draft-ietf-regext-epp-eai-07
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 26 June 2022. This Internet-Draft will expire on 25 July 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 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
and restrictions with respect to this document. Code Components and restrictions with respect to this document. Code Components
extracted from this document must include Revised BSD License text as extracted from this document must include Revised BSD License text 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 Revised BSD License. provided without warranty as described in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
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 . . . . . . . . . . . . . . . . . 4
4. Functional Extension . . . . . . . . . . . . . . . . . . . . 4 4. Functional Extension . . . . . . . . . . . . . . . . . . . . 4
5. Internationalized Email Addresses (EAI) Functional 5. Internationalized Email Addresses (EAI) Functional
Extension . . . . . . . . . . . . . . . . . . . . . . . . 4 Extension . . . . . . . . . . . . . . . . . . . . . . . . 5
5.1. Scope of Functional Extension . . . . . . . . . . . . . . 4 5.1. Scope of Functional Extension . . . . . . . . . . . . . . 5
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 . . . . . . . . . . . . . . . . . 8
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
8.1. Normative References . . . . . . . . . . . . . . . . . . 8 8.1. Normative References . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . 9 8.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 A.9. Change from the regext 04 to regext 05 version . . . . . 10
A.10. Change from the regext 05 to regext 06 version . . . . . 10 A.10. Change from the regext 05 to regext 06 version . . . . . 11
A.11. Change from the regext 06 to regext 07 version . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 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
skipping to change at page 5, line 13 skipping to change at page 5, line 25
the EPP session apply. There is no concept of a per-client, per- the EPP session apply. There is no concept of a per-client, per-
zone, per-extension, or per-field setting that is used to indicate zone, per-extension, or per-field setting that is used to indicate
support for EAI, but instead it's a global setting that applies to support for EAI, but instead it's a global setting that applies to
the EPP session. the EPP session.
5.2. Signaling Client and Server Support 5.2. Signaling Client and Server Support
The client and the server can signal support for the functional The client and the server can signal support for the functional
extension using a namespace URI in the login and greeting extension extension using a namespace URI in the login and greeting extension
services respectively. The namespace URI services respectively. The namespace URI
"urn:ietf:params:xml:ns:epp:eai-0.3" is used to signal support for "urn:ietf:params:xml:ns:epp:eai-1.0" is used to signal support for
the functional extension. The client includes the namespace URI in the functional extension. The client includes the namespace URI in
an <svcExtension> <extURI> element of the [RFC5730] <login> Command. an <svcExtension> <extURI> element of the [RFC5730] <login> Command.
The server includes the namespace URI in an <svcExtension> <extURI> The server includes the namespace URI in an <svcExtension> <extURI>
element of the [RFC5730] Greeting. element of the [RFC5730] Greeting.
5.3. Functional Extension Behavior 5.3. Functional Extension Behavior
5.3.1. EAI Functional Extension Negotiated 5.3.1. EAI Functional Extension Negotiated
If both client and server have indicated the support of the EAI If both client and server have indicated the support of the EAI
skipping to change at page 7, line 36 skipping to change at page 7, line 44
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:
URI: urn:ietf:params:xml:ns:epp:eai-0.3 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.
Registration request for the eai XML Schema: Registration request for the eai XML Schema:
URI: urn:ietf:params:xml:schema:epp:eai-0.3 URI: urn:ietf:params:xml:schema:epp:eai-1.0
Registrant Contact: IESG Registrant Contact: IESG
XML: See the "Formal Syntax" section of this document. XML: See the "Formal Syntax" section of this document.
7.2. EPP Extension Registry 7.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
IANA in the "Extensions for the Extensible Provisioning Protocol IANA in the "Extensions for the Extensible Provisioning Protocol
(EPP)" registry described in RFC 7451 [RFC7451]. The details of the (EPP)" registry described in RFC 7451 [RFC7451]. The details of the
registration are as follows: registration are as follows:
skipping to change at page 10, line 44 skipping to change at page 11, line 4
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 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 A.10. Change from the regext 05 to regext 06 version
1. Some nitpicking 1. Some nitpicking
A.11. Change from the regext 06 to regext 07 version
1. Namespace version set to 1.0
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. 14 change blocks. 
15 lines changed or deleted 19 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/