Extensible Provisioning Protocol (EPP) Organization Mapping
draft-ietf-regext-org-04
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 8543.
|
|
|---|---|---|---|
| Authors | Linlin Zhou , Ning Kong , Guiqing Zhou , XiaoDong Lee , James Gould | ||
| Last updated | 2018-05-03 | ||
| Replaces | draft-ietf-regext-reseller | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews |
GENART Last Call review
(of
-10)
by Stewart Bryant
Ready w/issues
|
||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | In WG Last Call | |
| Document shepherd | (None) | ||
| IESG | IESG state | Became RFC 8543 (Proposed Standard) | |
| Consensus boilerplate | Yes | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-ietf-regext-org-04
<element name="chg"
type="org:chgType" minOccurs="0"/>
</sequence>
</complexType>
<!--
Data elements that can be added or removed.
-->
<complexType name="addRemType">
<sequence>
<element name="contact"
type="org:contactType" minOccurs="0" maxOccurs="unbounded"/>
<element name="role" type="org:roleType"
minOccurs="0" maxOccurs="unbounded"/>
<element name="status" type="org:statusType"
minOccurs="0" maxOccurs="9"/>
</sequence>
</complexType>
<!--
Data elements that can be changed.
-->
<complexType name="chgType">
<sequence>
<element name="parentId"
type="eppcom:clIDType" minOccurs="0"/>
<element name="postalInfo"
type="org:chgPostalInfoType"
minOccurs="0" maxOccurs="2"/>
<element name="voice"
type="org:e164Type" minOccurs="0"/>
Zhou, et al. Expires November 5, 2018 [Page 30]
Internet-Draft EPP Organization Mapping May 2018
<element name="fax"
type="org:e164Type" minOccurs="0"/>
<element name="email"
type="eppcom:minTokenType" minOccurs="0"/>
<element name="url"
type="anyURI" minOccurs="0"/>
</sequence>
</complexType>
<complexType name="chgPostalInfoType">
<sequence>
<element name="name"
type="org:postalLineType" minOccurs="0"/>
<element name="addr"
type="org:addrType" minOccurs="0"/>
</sequence>
<attribute name="type"
type="org:postalInfoEnumType" use="required"/>
</complexType>
<!--
Child response elements.
-->
<element name="chkData" type="org:chkDataType"/>
<element name="creData" type="org:creDataType"/>
<element name="infData" type="org:infDataType"/>
<!--
<check> response elements.
-->
<complexType name="chkDataType">
<sequence>
<element name="cd" type="org:checkType"
maxOccurs="unbounded" />
</sequence>
</complexType>
<complexType name="checkType">
<sequence>
<element name="id" type="org:checkIDType" />
<element name="reason" type="eppcom:reasonType"
minOccurs="0" />
</sequence>
</complexType>
<complexType name="checkIDType">
<simpleContent>
<extension base="eppcom:clIDType">
Zhou, et al. Expires November 5, 2018 [Page 31]
Internet-Draft EPP Organization Mapping May 2018
<attribute name="avail" type="boolean"
use="required" />
</extension>
</simpleContent>
</complexType>
<!--
<info> response elements.
-->
<complexType name="infDataType">
<sequence>
<element name="id"
type="eppcom:clIDType"/>
<element name="roid"
type="eppcom:roidType"/>
<element name="role"
type="org:roleType" maxOccurs="unbounded"/>
<element name="status"
type="org:statusType" maxOccurs="9"/>
<element name="parentId"
type="eppcom:clIDType" minOccurs="0"/>
<element name="postalInfo"
type="org:postalInfoType" minOccurs="0" maxOccurs="2"/>
<element name="voice"
type="org:e164Type" minOccurs="0"/>
<element name="fax"
type="org:e164Type" minOccurs="0"/>
<element name="email"
type="eppcom:minTokenType" minOccurs="0"/>
<element name="url"
type="anyURI" minOccurs="0"/>
<element name="contact"
type="org:contactType" minOccurs="0" maxOccurs="unbounded"/>
<element name="clID"
type="eppcom:clIDType" minOccurs="0"/>
<element name="crID"
type="eppcom:clIDType"/>
<element name="crDate"
type="dateTime"/>
<element name="upID"
type="eppcom:clIDType" minOccurs="0"/>
<element name="upDate"
type="dateTime" minOccurs="0"/>
</sequence>
</complexType>
<!--
<create> response elements.
-->
Zhou, et al. Expires November 5, 2018 [Page 32]
Internet-Draft EPP Organization Mapping May 2018
<complexType name="creDataType">
<sequence>
<element name="id" type="eppcom:clIDType" />
<element name="crDate" type="dateTime" />
</sequence>
</complexType>
<!--
End of schema.
-->
</schema>
END
6. Internationalization Considerations
EPP is represented in XML, which provides native support for encoding
information using the Unicode character set and its more compact
representations including UTF-8. Conformant XML processors recognize
both UTF-8 and UTF-16. Though XML includes provisions to identify
and use other character encodings through use of an "encoding"
attribute in an <?xml?> declaration, use of UTF-8 is RECOMMENDED.
As an extension of the EPP organization object mapping, the elements
and element content described in this document MUST inherit the
internationalization conventions used to represent higher-layer
domain and core protocol structures present in an XML instance that
includes this extension.
7. IANA Considerations
7.1. XML Namespace
This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism described in [RFC3688]. IANA is
requested to assignment the following URI.
Registration request for the organization namespace:
URI: urn:ietf:params:xml:ns:org-1.0
Registrant Contact: See the "Author's Address" section of this
document.
XML: None. Namespace URIs do not represent an XML specification.
Registration request for the organization XML schema:
URI: urn:ietf:params:xml:ns:org-1.0
Zhou, et al. Expires November 5, 2018 [Page 33]
Internet-Draft EPP Organization Mapping May 2018
Registrant Contact: See the "Author's Address" section of this
document.
XML: See the "Formal Syntax" section of this document.
7.2. EPP Extension Registry
The EPP extension described in this document should be registered by
the IANA in the EPP Extension Registry described in [RFC7451]. The
details of the registration are as follows:
Name of Extension: Organization Object Extension
Document status: Standards Track
Reference: (insert reference to RFC version of this document)
Registrant Name and Email Address: IESG
TLDs: any
IPR Disclosure: none
Status: active
Notes: none
7.3. Role Values Registry
The following values should be registered by the IANA in the "EPP
Organization Role Values" registry. The registration policy for this
registry is "Expert Review" [RFC8126].
7.3.1. Registration Template
Value: the string value being registered.
Description: Brief description of the organization role values.
Registrant Name: For Standards Track RFCs, state "IESG". For others,
give the name of the responsible party.
Registrant Contact Information: an email address, postal address, or
some other information to be used to contact the registrant.
Zhou, et al. Expires November 5, 2018 [Page 34]
Internet-Draft EPP Organization Mapping May 2018
7.3.2. Initial Registry Contents
Followings are the initial registry contents:
Value: registrar
Description: The entity object instance represents the authority
responsible for the registration in the registry.
Registrant Name: IESG
Registrant Contact Information: iesg@ietf.org
Value: reseller
Description: The entity object instance represents a third party
through which the registration was conducted (i.e., not the
registry or registrar).
Registrant Name: IESG
Registrant Contact Information: iesg@ietf.org
Value: privacyproxy
Description: The entity object instance represents a third-party
who could help to register a domain without exposing the
registrants' private information..
Registrant Name: IESG
Registrant Contact Information: iesg@ietf.org
8. Implementation Status
Note to RFC Editor: Please remove this section and the reference to
[RFC7942] before publication. This section records the status of
known implementations of the protocol defined by this specification
at the time of posting of this Internet-Draft, and is based on a
proposal described in [RFC7942]. The description of implementations
in this section is intended to assist the IETF in its decision
processes in progressing drafts to RFCs. Please note that the
listing of any individual implementation here does not imply
endorsement by the IETF. Furthermore, no effort has been spent to
verify the information presented here that was supplied by IETF
contributors. This is not intended as, and must not be construed to
be, a catalog of available implementations or their features.
Readers are advised to note that other implementations may exist.
Zhou, et al. Expires November 5, 2018 [Page 35]
Internet-Draft EPP Organization Mapping May 2018
According to [RFC7942], "this will allow reviewers and working groups
to assign due consideration to documents that have the benefit of
running code, which may serve as evidence of valuable experimentation
and feedback that have made the implemented protocols more mature.
It is up to the individual working groups to use this information as
they see fit".
Verisign has already implemented this object mapping. CNNIC and
Net::DRI (Patrick Mevzek) are in the process of development research
to update organization objecct from reseller object. Dns Belgium is
planning to implement it after the publication of this document.
8.1. Verisign EPP SDK
Organization: Verisign Inc.
Name: Verisign EPP SDK
Description: The Verisign EPP SDK includes both a full client
implementation and a full server stub implementation of draft-ietf-
regext-org.
Level of maturity: Development
Coverage: All aspects of the protocol are implemented.
Licensing: GNU Lesser General Public License
Contact: jgould@verisign.com
URL: https://www.verisign.com/en_US/channel-resources/domain-
registry-products/epp-sdks
8.2. CNNIC Implementation
Organization: CNNIC
Name: EPP Organization Mapping
Description: CNNIC is trying to update EPP organization mapping from
previous reseller mapping according to this document.
Level of maturity: Development
Coverage: EPP organization mapping
Contact: zhouguiqing@cnnic.cn
Zhou, et al. Expires November 5, 2018 [Page 36]
Internet-Draft EPP Organization Mapping May 2018
8.3. Reseller Extension
This document was updated from [ID.draft-ietf-regext-reseller].
CNNIC, Verisign and Net::DRI (Patrick Mevzek) have already
implemented the reseller mapping.
9. Security Considerations
The object mapping extension described in this document does not
provide any other security services or introduce any additional
considerations beyond those described by [RFC5730] or those caused by
the protocol layers used by EPP. The security considerations
described in these other specifications apply to this specification
as well.
10. Acknowledgment
The authors would like to thank Rik Ribbers, Marc Groeneweg, Patrick
Mevzek, Antoin Verschuren and Scott Hollenbeck for their careful
review and valuable comments.
11. References
11.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009,
<https://www.rfc-editor.org/info/rfc5730>.
[RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
Code: The Implementation Status Section", BCP 205,
RFC 7942, DOI 10.17487/RFC7942, July 2016,
<https://www.rfc-editor.org/info/rfc7942>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>.
Zhou, et al. Expires November 5, 2018 [Page 37]
Internet-Draft EPP Organization Mapping May 2018
[W3C.REC-xml-20040204]
Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and
F. Yergeau, ""Extensible Markup Language (XML) 1.0 (Third
Edition)", World Wide Web Consortium FirstEdition REC-xml-
20040204", February 2004,
<http://www.w3.org/TR/2004/REC-xml-20040204>.
[W3C.REC-xmlschema-1-20041028]
Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn,
""XML Schema Part 1: Structures Second Edition", World
Wide Web Consortium Recommendation REC-xmlschema-
1-20041028", October 2004,
<http://www.w3.org/TR/2004/REC-xmlschema-1-20041028>.
[W3C.REC-xmlschema-2-20041028]
Biron, P. and A. Malhotra, ""XML Schema Part 2: Datatypes
Second Edition", World Wide Web Consortium Recommendation
REC-xmlschema-2-20041028", October 2004,
<http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>.
11.2. Informative References
[ID.draft-ietf-regext-reseller]
Zhou, L., Kong, N., Guiqing, G., Lee, X., and J. Gould,
"Extensible Provisioning Protocol (EPP) Reseller Mapping",
Dec 2016,
<http://tools.ietf.org/html/draft-ietf-regext-reseller>.
[RFC7451] Hollenbeck, S., "Extension Registry for the Extensible
Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451,
February 2015, <https://www.rfc-editor.org/info/rfc7451>.
Appendix A. Change Log
Initial -00: Individual document submitted.
-01:
* Updated abstract text.
* Added sentences to avoid loop of parent identifiers in section
3.4.
* Revised typos in section 3.6.
* Added explanation of contact type attribute in section 4.1.2.
* Updated <info> responses.
Zhou, et al. Expires November 5, 2018 [Page 38]
Internet-Draft EPP Organization Mapping May 2018
* Deleted description of <transfer> command in section 4.1 and
4.2.
* Deleted whoisInfo disclose type in XML schema.
* Deleted maxOccurs of addRemType.
* Deleted extra "OPTIONAL" in section 4.2.5.
* Updated typos in <update> response.
-02:
* Changed author information.
* Updated url definition.
* Updated XML schema.
-03:
* Changed author information.
* Updated section 3.1.
* Refactoried the XSD file. Added <chgPostalInfoType> element.
* Added acknowledgment.
WG document-00: WG document submitted
WG document-01: Keep document alive for further discussion.
Reseller object or entity object with multiple roles?
Organization WG document-00: Change to a generic organization object
mapping.
Organization WG document-01: Added "Implementation Status" section.
Organization WG document-02: Accepted some of the feedbacks on the
mailing list.
Organization WG document-03:
* Updated section 3.2, changed the structure of organization
role.
* Updated section 4.2.5 for the "add", "rem" and "chg" example.
Zhou, et al. Expires November 5, 2018 [Page 39]
Internet-Draft EPP Organization Mapping May 2018
* Updated section 5 of formal syntax.
* Updated section 7.2 for the registration template and initial
values.
* Updated section 8 of implementation status.
Organization WG document-04:
* Updated section 3.2, changed the structure of organization
role.
* Updated references.
* Updated section 8 of implementation status.
Authors' Addresses
Linlin Zhou
CNNIC
4 South 4th Street, Zhongguancun, Haidian District
Beijing, Beijing 100190
China
Phone: +86 10 5881 2677
Email: zhoulinlin@cnnic.cn
Ning Kong
CNNIC
4 South 4th Street, Zhongguancun, Haidian District
Beijing, Beijing 100190
China
Phone: +86 10 5881 3147
Email: nkong@cnnic.cn
Guiqing Zhou
CNNIC
4 South 4th Street, Zhongguancun, Haidian District
Beijing, Beijing 100190
China
Phone: +86 10 5881 2692
Email: zhouguiqing@cnnic.cn
Zhou, et al. Expires November 5, 2018 [Page 40]
Internet-Draft EPP Organization Mapping May 2018
Xiaodong Lee
CNNIC
4 South 4th Street, Zhongguancun, Haidian District
Beijing, Beijing 100190
China
Phone: +86 10 5881 3020
Email: xl@cnnic.cn
James Gould
Verisign, Inc.
12061 Bluemont Way
Reston, VA 20190
US
Email: jgould@verisign.com
Zhou, et al. Expires November 5, 2018 [Page 41]