draft-ietf-regext-org-ext-04.txt   draft-ietf-regext-org-ext-05.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 5, 2018 X. Lee Expires: November 8, 2018 X. Lee
CNNIC CNNIC
J. Gould J. Gould
Verisign, Inc. Verisign, Inc.
May 4, 2018 May 7, 2018
Organization Extension for the Extensible Provisioning Protocol (EPP) Organization Extension for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-org-ext-04 draft-ietf-regext-org-ext-05
Abstract Abstract
This mapping, an extension to EPP object mappings like the EPP domain This mapping, an extension to EPP object mappings like the EPP domain
name mapping [RFC5731], to support assigning an organization to any name mapping [RFC5731], to support assigning an organization to any
existing object (domain, host, contact) as well as any future existing object (domain, host, contact) as well as any future
objects. objects.
Status of This Memo Status of This Memo
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 5, 2018. This Internet-Draft will expire on November 8, 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 45 skipping to change at page 2, line 45
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
7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 18 7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 18
8. Implementation Status . . . . . . . . . . . . . . . . . . . . 18 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 18
8.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 19 8.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 19
8.2. CNNIC Implementation . . . . . . . . . . . . . . . . . . 19 8.2. CNNIC Implementation . . . . . . . . . . . . . . . . . . 19
8.3. Reseller Extension . . . . . . . . . . . . . . . . . . . 20 9. Security Considerations . . . . . . . . . . . . . . . . . . . 19
9. Security Considerations . . . . . . . . . . . . . . . . . . . 20
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 . . . . . . . . . . . . . . . . . . . . . 22 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
have some other roles of entities involved in the domain registration have some other roles of entities involved in the domain registration
process which are not formally defined, such as resellers, DNS process which are not formally defined, such as resellers, DNS
service operators, privacy proxy, etc. service operators, privacy proxy, etc.
skipping to change at page 11, line 43 skipping to change at page 11, line 43
o An OPTIONAL <orgext:rem> element that contains attribute values to o An OPTIONAL <orgext:rem> element that contains attribute values to
be removed from the object. be removed from the object.
o An OPTIONAL <orgext:chg> element that contains attribute values to o An OPTIONAL <orgext:chg> element that contains attribute values to
be changed. be changed.
At least one and only one <orgext:add>, <orgext:rem> or <orgext:chg> At least one and only one <orgext:add>, <orgext:rem> or <orgext:chg>
element MUST be provided. The <orgext:add>, <orgext:rem> and element MUST be provided. The <orgext:add>, <orgext:rem> and
<orgext:chg> elements contain the following child element: <orgext:chg> elements contain the following child element:
o One or more <orgext:id> element that contains the identifier of o One or more <orgext:id> elements that contains the identifier of
the organization. The "role" attribute is used to represent the the organization. The "role" attribute is used to represent the
relationship that the organization has to the object. See relationship that the organization has to the object. See
Section 7.3 in [ID.draft-ietf-regext-org] for a list of values. Section 7.3 in [ID.draft-ietf-regext-org] for a list of values.
Example <update> command, adding a reseller: Example <update> command, adding a reseller:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command> C: <command>
C: <update> C: <update>
skipping to change at page 16, line 44 skipping to change at page 16, line 44
<element <element
name="chg" name="chg"
type="orgext:addRemChgType" type="orgext:addRemChgType"
minOccurs="0" minOccurs="0"
/> />
</sequence> </sequence>
</complexType> </complexType>
<complexType name="addRemChgType"> <complexType name="addRemChgType">
<sequence> <sequence>
<!-- agent identifier the organization, <!-- agent identifier of the organization,
e.g. registrar, reseller, privacy proxy, etc. --> e.g. registrar, reseller, privacy proxy, etc. -->
<element <element
name="id" name="id"
type="orgext:orgIdType" type="orgext:orgIdType"
minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
<!-- Child response element --> <!-- Child response element -->
<element <element
name="infData" name="infData"
type="orgext:infDataType"/> type="orgext:infDataType"/>
<!-- <orgext:infData> response elements --> <!-- <orgext:infData> response elements -->
<complexType name="infDataType"> <complexType name="infDataType">
<sequence> <sequence>
<!-- agent identifier the organization, <!-- agent identifier the organization,
e.g. registrar, reseller, privacy proxy, etc. --> e.g. registrar, reseller, privacy proxy, etc. -->
skipping to change at page 19, line 5 skipping to change at page 19, line 4
endorsement by the IETF. Furthermore, no effort has been spent to endorsement by the IETF. Furthermore, no effort has been spent to
verify the information presented here that was supplied by IETF verify the information presented here that was supplied by IETF
contributors. This is not intended as, and must not be construed to contributors. This is not intended as, and must not be construed to
be, a catalog of available implementations or their features. be, a catalog of available implementations or their features.
Readers are advised to note that other implementations may exist. Readers are advised to note that other implementations may exist.
According to [RFC7942], "this will allow reviewers and working groups According to [RFC7942], "this will allow reviewers and working groups
to assign due consideration to documents that have the benefit of to assign due consideration to documents that have the benefit of
running code, which may serve as evidence of valuable experimentation running code, which may serve as evidence of valuable experimentation
and feedback that have made the implemented protocols more mature. and feedback that have made the implemented protocols more mature.
It is up to the individual working groups to use this information as It is up to the individual working groups to use this information as
they see fit". they see fit".
Verisign has already implemented this extension. CNNIC and Net::DRI
(Patrick Mevzek) are in the process of development research to update
organization extension from reseller extension. Dns Belgium is
planning to implement it after the publication of this document.
8.1. Verisign EPP SDK 8.1. Verisign EPP SDK
Organization: Verisign Inc. Organization: Verisign Inc.
Name: Verisign EPP SDK Name: Verisign EPP SDK
Description: The Verisign EPP SDK includes both a full client Description: The Verisign EPP SDK includes both a full client
implementation and a full server stub implementation of draft-ietf- implementation and a full server stub implementation of draft-ietf-
regext-org-ext. regext-org-ext.
skipping to change at page 20, line 5 skipping to change at page 19, line 44
Description: CNNIC is trying to update organization extension from Description: CNNIC is trying to update organization extension from
previous reseller extension according to this document. previous reseller extension according to this document.
Level of maturity: Development Level of maturity: Development
Coverage: Organization extension for EPP Coverage: Organization extension for EPP
Contact: zhouguiqing@cnnic.cn Contact: zhouguiqing@cnnic.cn
8.3. Reseller Extension
This document was updated from [ID.draft-ietf-regext-reseller-ext].
CNNIC, Verisign and Net::DRI (Patrick Mevzek) have already
implemented this extension.
9. Security Considerations 9. Security Considerations
The object mapping extension described in this document does not The object mapping extension described in this document does not
provide any other security services or introduce any additional provide any other security services or introduce any additional
considerations beyond those described by [RFC5730], [RFC5731], considerations beyond those described by [RFC5730], [RFC5731],
[RFC5732] and [RFC5733] or those caused by the protocol layers used [RFC5732] and [RFC5733] or those caused by the protocol layers used
by EPP. by EPP.
10. Acknowledgment 10. Acknowledgment
skipping to change at page 21, line 42 skipping to change at page 21, line 26
<http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>. <http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>.
11.2. Informative References 11.2. Informative References
[ID.draft-ietf-regext-org] [ID.draft-ietf-regext-org]
Zhou, L., Kong, N., Zhou, G., Lee, X., and J. Gould, Zhou, L., Kong, N., Zhou, G., Lee, X., and J. Gould,
"Extensible Provisioning Protocol (EPP) Reseller Mapping", "Extensible Provisioning Protocol (EPP) Reseller Mapping",
Apr 2018, Apr 2018,
<http://tools.ietf.org/html/draft-ietf-regext-org>. <http://tools.ietf.org/html/draft-ietf-regext-org>.
[ID.draft-ietf-regext-reseller-ext]
Zhou, L., Kong, N., Wei, J., Lee, X., and J. Gould,
"Extensible Provisioning Protocol (EPP) Reseller Mapping",
Dec 2016, <http://tools.ietf.org/html/
draft-ietf-regext-reseller-ext>.
[RFC7451] Hollenbeck, S., "Extension Registry for the Extensible [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible
Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451,
February 2015, <https://www.rfc-editor.org/info/rfc7451>. February 2015, <https://www.rfc-editor.org/info/rfc7451>.
Appendix A. Change Log Appendix A. Change Log
Initial -00: Individual document submitted. Initial -00: Individual document submitted.
-01: -01:
skipping to change at page 23, line 34 skipping to change at page 23, line 9
* Updated typos. * Updated typos.
* Removed the example of <update> command, domain with no * Removed the example of <update> command, domain with no
organization. organization.
* Updated references. * Updated references.
* Updated section 8 of implementation status. * Updated section 8 of implementation status.
Organization WG document-05:
* Removed the minOccurs="0" from the addRemChgType type of the
XML schema
* Removed the third paragraph of "Implementation Status".
* Remove the Informative Reference to draft-ietf-regext-reseller-
ext from the draft.
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
 End of changes. 16 change blocks. 
29 lines changed or deleted 19 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/