Organization Extension for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-org-ext-08
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (regext WG)
|
|
Last updated |
|
2018-08-19
(latest revision 2018-06-14)
|
|
Replaces |
|
draft-ietf-regext-reseller-ext
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
pdf
html
bibtex
|
Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Pieter Vandepitte
|
|
Shepherd write-up |
|
Show
(last changed 2018-07-04)
|
IESG |
IESG state |
|
AD Evaluation::AD Followup
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Adam Roach
|
|
Send notices to |
|
Pieter Vandepitte <pieter.vandepitte@dnsbelgium.be>
|
Internet Engineering Task Force L. Zhou
Internet-Draft CNNIC
Intended status: Standards Track N. Kong
Expires: February 21, 2019 Consultant
J. Wei
J. Yao
CNNIC
J. Gould
Verisign, Inc.
August 20, 2018
Organization Extension for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-org-ext-08
Abstract
This document describes an extension to EPP object mappings, which is
designed to support assigning an organization to any existing object
(domain, host, contact) as well as any future objects.
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 February 21, 2019.
Copyright Notice
Copyright (c) 2018 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
Zhou, et al. Expires February 21, 2019 [Page 1]
Internet-Draft Organization Extension for the EPP August 2018
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
2. Conventions Used in This Document . . . . . . . . . . . . . . 3
3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Organization Identifier . . . . . . . . . . . . . . . . . 4
4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 4
4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 4
4.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 4
4.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 4
4.1.3. EPP <transfer> Query Command . . . . . . . . . . . . 7
4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 8
4.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 8
4.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 10
4.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 10
4.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 11
4.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 11
5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 15
6. Internationalization Considerations . . . . . . . . . . . . . 17
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 18
7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 18
8. Implementation Status . . . . . . . . . . . . . . . . . . . . 19
8.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 19
8.2. CNNIC Implementation . . . . . . . . . . . . . . . . . . 20
9. Security Considerations . . . . . . . . . . . . . . . . . . . 20
10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 20
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
11.1. Normative References . . . . . . . . . . . . . . . . . . 20
11.2. Informative References . . . . . . . . . . . . . . . . . 21
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24
1. Introduction
In the business model of domain registration, we usually have 3 roles
of entities: a registrant, a registrar and a registry. There may be
Show full document text