draft-ietf-regext-org-ext-05.txt   draft-ietf-regext-org-ext-06.txt 
Internet Engineering Task Force L. Zhou Internet Engineering Task Force L. Zhou
Internet-Draft N. Kong Internet-Draft N. Kong
Intended status: Standards Track J. Wei Intended status: Standards Track J. Wei
Expires: November 8, 2018 X. Lee Expires: November 10, 2018 X. Lee
CNNIC CNNIC
J. Gould J. Gould
Verisign, Inc. Verisign, Inc.
May 7, 2018 May 9, 2018
Organization Extension for the Extensible Provisioning Protocol (EPP) Organization Extension for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-org-ext-05 draft-ietf-regext-org-ext-06
Abstract Abstract
This mapping, an extension to EPP object mappings like the EPP domain This mapping which is an extension to EPP object mappings, is
name mapping [RFC5731], to support assigning an organization to any designed to support assigning an organization to any existing object
existing object (domain, host, contact) as well as any future (domain, host, contact) as well as any future objects.
objects.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 November 8, 2018. This Internet-Draft will expire on November 10, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 30 skipping to change at page 2, line 29
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions Used in This Document . . . . . . . . . . . . . . 3 2. Conventions Used in This Document . . . . . . . . . . . . . . 3
3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Organization Identifier . . . . . . . . . . . . . . . . . 4 3.1. Organization Identifier . . . . . . . . . . . . . . . . . 4
4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 4 4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 4
4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 4 4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 4
4.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 4 4.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 4
4.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 4 4.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 4
4.1.3. EPP <transfer> Command . . . . . . . . . . . . . . . 7 4.1.3. EPP <transfer> Query Command . . . . . . . . . . . . 7
4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 8 4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 8
4.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 8 4.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 8
4.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 10 4.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 10
4.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 10 4.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 10
4.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 11 4.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 11
4.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 11 4.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 11
5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 15 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 15
6. Internationalization Considerations . . . . . . . . . . . . . 17 6. Internationalization Considerations . . . . . . . . . . . . . 17
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 17 7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 17
skipping to change at page 3, line 8 skipping to change at page 3, line 8
10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 20 10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 20
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
11.1. Normative References . . . . . . . . . . . . . . . . . . 20 11.1. Normative References . . . . . . . . . . . . . . . . . . 20
11.2. Informative References . . . . . . . . . . . . . . . . . 21 11.2. Informative References . . . . . . . . . . . . . . . . . 21
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 21 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23
1. Introduction 1. Introduction
In the business model of domain registration, we usually have 3 roles In the business model of domain registration, we usually have 3 roles
of entities, a registrant, a registrar and a registry. There may of entities, a registrant, a registrar and a registry. There may be
have some other roles of entities involved in the domain registration other roles of entities involved in the domain registration process
process which are not formally defined, such as resellers, DNS which are not formally defined, such as resellers, DNS service
service operators, privacy proxy, etc. operators, privacy proxy, etc.
A domain reseller is an individual or a company that acts as a agent A domain reseller is an individual or a company that acts as a agent
for accredited registrars. A third-party DNS service operator is for accredited registrars. A third-party DNS service operator is
responsible for a zone where the operator is neither the registrant responsible for a zone where the operator is neither the registrant
nor the registrar of records for the delegation. And a privacy proxy nor the registrar of record for the delegation. A privacy proxy is
is an entity that provides with individuals or organizations domain an entity used for domain registrations to protect the private
registration without exposing their private information. These kind information of the individuals and organizations. These kind of
of entities are defined as "organizations" with different role types entities are defined as "organizations" with different role types in
in this document. this document.
In order to facilitate provisioning and management of organization In order to facilitate provisioning and management of organization
information in a shared central repository, this document proposes an information in a shared central repository, this document proposes an
organization extension mapping for any EPP object like domain names organization extension mapping for any EPP object like domain names
in [RFC5731], hosts in [RFC5732] and contacts in [RFC5733]. The in [RFC5731], hosts in [RFC5732] and contacts in [RFC5733]. The
examples provided in this document are used for the domain object for examples provided in this document are used for the domain object for
illustration purpose. The host and contact object could be extended illustration purpose. The host and contact object could be extended
in the same way with the domain object. in the same way with the domain object.
An organization mapping object defined in [ID.draft-ietf-regext-org] An organization mapping object defined in [ID.draft-ietf-regext-org]
skipping to change at page 7, line 47 skipping to change at page 7, line 47
S: <trID> S: <trID>
S: <clTRID>ngcl-IvJjzMZc</clTRID> S: <clTRID>ngcl-IvJjzMZc</clTRID>
S: <svTRID>test142AWQONJZ</svTRID> S: <svTRID>test142AWQONJZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
An EPP error response MUST be returned if an <info> command cannot be An EPP error response MUST be returned if an <info> command cannot be
processed for any reason. processed for any reason.
4.1.3. EPP <transfer> Command 4.1.3. EPP <transfer> Query Command
This extension does not add any elements to the EPP <transfer> This extension does not add any elements to the EPP <transfer> query
command or <transfer> response described in the EPP domain name command or <transfer> query response described in the EPP domain name
mapping [RFC5731], host mapping [RFC5732] and contact mapping mapping [RFC5731], host mapping [RFC5732] and contact mapping
[RFC5733]. [RFC5733].
4.2. EPP Transform Commands 4.2. EPP Transform Commands
EPP provides five commands to transform domain objects: <create> to EPP provides five commands to transform domain objects: <create> to
create an instance of a domain object, <delete> to delete an instance create an instance of a domain object, <delete> to delete an instance
of a domain object, <renew> to extend the validity period of a domain of a domain object, <renew> to extend the validity period of a domain
object, <transfer> to manage domain object sponsorship changes, and object, <transfer> to manage domain object sponsorship changes, and
<update> to change information associated with a domain object. <update> to change information associated with a domain object.
skipping to change at page 18, line 4 skipping to change at page 18, line 4
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 [RFC3688]. IANA is conforming to a registry mechanism described in [RFC3688]. IANA is
requested to assignment the following URI. requested to assignment the following URI.
Registration request for the organization namespace: Registration request for the organization namespace:
URI: urn:ietf:params:xml:ns:orgext-1.0 URI: urn:ietf:params:xml:ns:orgext-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IESG
document.
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
the IANA in the EPP Extension Registry described in [RFC7451]. The the IANA in the EPP Extension Registry described in [RFC7451]. The
details of the registration are as follows: details of the registration are as follows:
Name of Extension: Organization Extension Name of Extension: Organization Extension for the Extensible
Provisioning Protocol (EPP)
Document status: Standards Track
Reference: (insert reference to RFC version of this document)
Registrant Name and Email Address: IESG Registrant Name and Email Address: IESG, iesg@ietf.org
TLDs: any TLDs: Any
IPR Disclosure: none IPR Disclosure: None
Status: active Status: Active
Notes: none Notes: None
8. Implementation Status 8. Implementation Status
Note to RFC Editor: Please remove this section and the reference to Note to RFC Editor: Please remove this section and the reference to
[RFC7942] before publication. This section records the status of [RFC7942] before publication. This section records the status of
known implementations of the protocol defined by this specification known implementations of the protocol defined by this specification
at the time of posting of this Internet-Draft, and is based on a at the time of posting of this Internet-Draft, and is based on a
proposal described in [RFC7942]. The description of implementations proposal described in [RFC7942]. The description of implementations
in this section is intended to assist the IETF in its decision in this section is intended to assist the IETF in its decision
processes in progressing drafts to RFCs. Please note that the processes in progressing drafts to RFCs. Please note that the
skipping to change at page 23, line 19 skipping to change at page 23, line 19
Organization WG document-05: Organization WG document-05:
* Removed the minOccurs="0" from the addRemChgType type of the * Removed the minOccurs="0" from the addRemChgType type of the
XML schema XML schema
* Removed the third paragraph of "Implementation Status". * Removed the third paragraph of "Implementation Status".
* Remove the Informative Reference to draft-ietf-regext-reseller- * Remove the Informative Reference to draft-ietf-regext-reseller-
ext from the draft. ext from the draft.
Organization WG document-06:
* Updated "Abstraction".
* Added "Query" for "<Transfer> Query Command".
* Change "Registrant Contact" to IESG in section 7.1.
* Modified section 7.2.
Authors' Addresses Authors' Addresses
Linlin Zhou Linlin Zhou
CNNIC CNNIC
4 South 4th Street, Zhongguancun, Haidian District 4 South 4th Street, Zhongguancun, Haidian District
Beijing, Beijing 100190 Beijing, Beijing 100190
China China
Phone: +86 10 5881 2677 Phone: +86 10 5881 2677
Email: zhoulinlin@cnnic.cn Email: zhoulinlin@cnnic.cn
skipping to change at page 23, line 38 skipping to change at page 24, line 4
Email: zhoulinlin@cnnic.cn Email: zhoulinlin@cnnic.cn
Ning Kong Ning Kong
CNNIC CNNIC
4 South 4th Street, Zhongguancun, Haidian District 4 South 4th Street, Zhongguancun, Haidian District
Beijing, Beijing 100190 Beijing, Beijing 100190
China China
Phone: +86 10 5881 3147 Phone: +86 10 5881 3147
Email: nkong@cnnic.cn Email: nkong@cnnic.cn
Junkai Wei Junkai Wei
CNNIC CNNIC
4 South 4th Street, Zhongguancun, Haidian District 4 South 4th Street, Zhongguancun, Haidian District
Beijing, Beijing 100190 Beijing, Beijing 100190
China China
Phone: +86 10 5881 3494 Phone: +86 10 5881 3494
Email: weijunkai@cnnic.cn Email: weijunkai@cnnic.cn
Xiaodong Lee Xiaodong Lee
CNNIC CNNIC
4 South 4th Street, Zhongguancun, Haidian District 4 South 4th Street, Zhongguancun, Haidian District
Beijing, Beijing 100190 Beijing, Beijing 100190
China China
Phone: +86 10 5881 3020
Email: xl@cnnic.cn Email: xl@cnnic.cn
James Gould James Gould
Verisign, Inc. Verisign, Inc.
12061 Bluemont Way 12061 Bluemont Way
Reston, VA 20190 Reston, VA 20190
US US
Email: jgould@verisign.com Email: jgould@verisign.com
 End of changes. 21 change blocks. 
35 lines changed or deleted 39 lines changed or added

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