draft-ietf-regext-org-01.txt   draft-ietf-regext-org-02.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 G. Zhou Intended status: Standards Track G. Zhou
Expires: June 8, 2018 X. Lee Expires: September 1, 2018 X. Lee
CNNIC CNNIC
J. Gould J. Gould
VeriSign, Inc. VeriSign, Inc.
December 5, 2017 February 28, 2018
Extensible Provisioning Protocol (EPP) Organization Mapping Extensible Provisioning Protocol (EPP) Organization Mapping
draft-ietf-regext-org-01 draft-ietf-regext-org-02
Abstract Abstract
This document describes an Extensible Provisioning Protocol (EPP) This document describes an Extensible Provisioning Protocol (EPP)
mapping for provisioning and management of organization object stored mapping for provisioning and management of organization objects
in a shared central repository. Specified in Extensible Markup stored in a shared central repository. Specified in Extensible
Language (XML), this extended mapping is applied to provide Markup Language (XML), this extended mapping is applied to provide
additional features required for the provisioning of organizations. additional features required for the provisioning of organizations.
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 June 8, 2018. This Internet-Draft will expire on September 1, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 30 skipping to change at page 2, line 30
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
3.2. Organization Roles . . . . . . . . . . . . . . . . . . . 4 3.2. Organization Roles . . . . . . . . . . . . . . . . . . . 4
3.2.1. Role Type . . . . . . . . . . . . . . . . . . . . . . 4 3.2.1. Role Type . . . . . . . . . . . . . . . . . . . . . . 4
3.2.2. Role Identifier . . . . . . . . . . . . . . . . . . . 4 3.2.2. Role Identifier . . . . . . . . . . . . . . . . . . . 4
3.3. Contact and Client Identifiers . . . . . . . . . . . . . 4 3.2.3. Example of Organization Roles . . . . . . . . . . . . 4
3.4. Organization Status Values . . . . . . . . . . . . . . . 4 3.3. Contact and Client Identifiers . . . . . . . . . . . . . 5
3.4. Organization Status Values . . . . . . . . . . . . . . . 5
3.5. Role Status Values . . . . . . . . . . . . . . . . . . . 6 3.5. Role Status Values . . . . . . . . . . . . . . . . . . . 6
3.6. Parent Identifier . . . . . . . . . . . . . . . . . . . . 6 3.6. Parent Identifier . . . . . . . . . . . . . . . . . . . . 6
3.7. URL . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.7. URL . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 6 3.8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 7
4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 7 4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 7
4.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 7 4.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 7
4.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 9 4.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 9
4.1.3. EPP <transfer> Command . . . . . . . . . . . . . . . 14 4.1.3. EPP <transfer> Command . . . . . . . . . . . . . . . 15
4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 14 4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 15
4.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 14 4.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 15
4.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 18 4.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 19
4.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 19 4.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 20
4.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 19 4.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 20
4.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 20 4.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 21
5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 23 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 24
6. Internationalization Considerations . . . . . . . . . . . . . 29 6. Internationalization Considerations . . . . . . . . . . . . . 30
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 29 7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 30
7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 30 7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 31
7.3. Role Values Registry . . . . . . . . . . . . . . . . . . 30 7.3. Role Values Registry . . . . . . . . . . . . . . . . . . 31
8. Implementation Status . . . . . . . . . . . . . . . . . . . . 32
8. Implementation Status . . . . . . . . . . . . . . . . . . . . 31 8.1. CNNIC Implementation . . . . . . . . . . . . . . . . . . 32
8.1. CNNIC Impelementation . . . . . . . . . . . . . . . . . . 31 8.2. Reseller Extension . . . . . . . . . . . . . . . . . . . 33
8.2. Reseller Extension . . . . . . . . . . . . . . . . . . . 32 9. Security Considerations . . . . . . . . . . . . . . . . . . . 33
9. Security Considerations . . . . . . . . . . . . . . . . . . . 32 10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 33
10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 32 11. Normative References . . . . . . . . . . . . . . . . . . . . 33
11. Normative References . . . . . . . . . . . . . . . . . . . . 32 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 34
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 33 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 34
1. Introduction 1. Introduction
There are many domain entities, such as registrar, reseller, DNS There are many entities, such as registrars, resellers, DNS service
service operator, or privacy proxy involved in the domain operators, or privacy proxies involved in the domain registration
registration business. These kind of entities have not been formally business. These kind of entities have not been formally defined as
defined in EPP which will be specified as "organization" in this an object in EPP which will be specified as "organization" in this
document. document.
This document describes an organization object mapping for version This document describes an organization object mapping for version
1.0 of the Extensible Provisioning Protocol (EPP) [RFC5730]. This 1.0 of the Extensible Provisioning Protocol (EPP) [RFC5730]. This
mapping is specified using the XML 1.0 as described in mapping is specified using the XML 1.0 as described in
[W3C.REC-xml-20040204] and XML Schema notation as described in [W3C.REC-xml-20040204] and XML Schema notation as described in
[W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028]. [W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028].
2. Conventions Used in This Document 2. Conventions Used in This Document
skipping to change at page 4, line 30 skipping to change at page 4, line 30
described in [RFC5730]. Its corresponding element is <org:id>. described in [RFC5730]. Its corresponding element is <org:id>.
3.2. Organization Roles 3.2. Organization Roles
The organization roles are used to represent the relationship an The organization roles are used to represent the relationship an
organization would have. Its corresponding element is <org:role>. organization would have. Its corresponding element is <org:role>.
3.2.1. Role Type 3.2.1. Role Type
An organization would support a list of roles. See Section 7.3 for a An organization would support a list of roles. See Section 7.3 for a
list of values. Its corresponding element is <org:type> with an list of values. Its corresponding element is <org:type> with a
"roleStatus" attribute. The values of role statuses are defined in "roleStatus" attribute. The values of role statuses are defined in
Section 3.5. Section 3.5.
3.2.2. Role Identifier 3.2.2. Role Identifier
A role MAY have a third party assigned identifier such as the IANA ID A role MAY have a third party assigned identifier such as the IANA ID
for registrars. Its corresponding element is <org:roleid>. for registrars. Its corresponding element is <org:roleid>.
3.2.3. Example of Organization Roles
Example of "Organization Roles"
S: <org:role>
S: <org:type roleStatus="ok">registrar</org:type>
S: <org:roleid>1362</org:roleid>
S: </org:role>
3.3. Contact and Client Identifiers 3.3. Contact and Client Identifiers
All EPP contacts are identified by a server-unique identifier. All EPP contacts are identified by a server-unique identifier.
Contact identifiers are character strings with a specific minimum Contact identifiers are character strings with a specific minimum
length, a specified maximum length, and a specified format. Contact length, a specified maximum length, and a specified format. Contact
identifiers use the "clIDType" client identifier syntax described in identifiers use the "clIDType" client identifier syntax described in
[RFC5730]. [RFC5730].
3.4. Organization Status Values 3.4. Organization Status Values
skipping to change at page 5, line 12 skipping to change at page 5, line 27
Status Value Descriptions: Status Value Descriptions:
o ok: This is the normal status value for an object that has no o ok: This is the normal status value for an object that has no
pending operations or prohibitions. This value is set and removed pending operations or prohibitions. This value is set and removed
by the server as other status values are added or removed. by the server as other status values are added or removed.
o hold: Organization transform commands and new links MUST be o hold: Organization transform commands and new links MUST be
rejected. rejected.
o terminated: The organization has been terminated MUST NOT be o terminated: The organization which has been terminated MUST NOT be
linked. Organization transform commands and new links MUST be linked. Organization transform commands and new links MUST be
rejected. rejected.
o linked: The organization object has at least one active o linked: The organization object has at least one active
association with another object. The "linked" status is not association with another object. The "linked" status is not
explicitly set by the client. Servers SHOULD provide services to explicitly set by the client. Servers SHOULD provide services to
determine existing object associations. determine existing object associations.
o clientLinkProhibited, serverLinkProhibited: Requests to add new o clientLinkProhibited, serverLinkProhibited: Requests to add new
links to the organization MUST be rejected. links to the organization MUST be rejected.
skipping to change at page 6, line 47 skipping to change at page 7, line 10
Loops SHOULD be prohibited. If organization A has B as parent Loops SHOULD be prohibited. If organization A has B as parent
identifier, organization B must not have organization A as parent identifier, organization B must not have organization A as parent
identifier. identifier.
3.7. URL 3.7. URL
The URL represents the organization web home page, as defined with The URL represents the organization web home page, as defined with
the <org:url> element. the <org:url> element.
3.8.
Date and time attribute values MUST be represented in Universal
Coordinated Time (UTC) using the Gregorian calendar. The extended
date-time form using upper case "T" and "Z" characters defined in
[W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time
values, as XML Schema does not support truncated date-time forms or
lower case "T" and "Z" characters.
4. EPP Command Mapping 4. EPP Command Mapping
A detailed description of the EPP syntax and semantics can be found A detailed description of the EPP syntax and semantics can be found
in the EPP core protocol specification [RFC5730]. The command in the EPP core protocol specification [RFC5730]. The command
mappings described here are specifically for use in provisioning and mappings described here are specifically for use in provisioning and
managing organization information via EPP. managing organization information via EPP.
4.1. EPP Query Commands 4.1. EPP Query Commands
EPP provides two commands to retrieve domain information: <check> to EPP provides two commands to retrieve domain information: <check> to
determine if an organization object can be provisioned within a determine if an organization object can be provisioned within a
repository, and <info> to retrieve detailed information associated repository, and <info> to retrieve detailed information associated
with an organization object. This document does not define a mapping with an organization object. This document does not define a mapping
for the EPP <transfer> command. for the EPP <transfer> command to retrieve domain-object transfer
status information..
4.1.1. EPP <check> Command 4.1.1. EPP <check> Command
The EPP <check> command is used to determine if an object can be The EPP <check> command is used to determine if an object can be
provisioned within a repository. It provides a hint that allows a provisioned within a repository. It provides a hint that allows a
client to anticipate the success or failure of provisioning an object client to anticipate the success or failure of provisioning an object
using the <create> command, as object-provisioning requirements are using the <create> command, as object-provisioning requirements are
ultimately a matter of server policy. ultimately a matter of server policy.
In addition to the standard EPP command elements, the <check> command In addition to the standard EPP command elements, the <check> command
skipping to change at page 10, line 9 skipping to change at page 10, line 41
optional role id of the organization. optional role id of the organization.
* A <org:type> element that contains the type of the * A <org:type> element that contains the type of the
organization, as defined in Section 3.2. A "roleStatus" organization, as defined in Section 3.2. A "roleStatus"
attribute is used to describe the status value of a role type. attribute is used to describe the status value of a role type.
* An OPTIONAL <org:roleid> element that contains a third party * An OPTIONAL <org:roleid> element that contains a third party
assigned identifier, such as IANA ID for registrars, as defined assigned identifier, such as IANA ID for registrars, as defined
in Section 3.2.2. in Section 3.2.2.
o A <org:status> element that contains the operational status of the o One or more <org:status> elements that contains the operational
organization, as defined in Section 3.4. status of the organization, as defined in Section 3.4.
o An OPTIONAL <org:parentId> element that contains the identifier of o An OPTIONAL <org:parentId> element that contains the identifier of
the parent object, as defined in Section 3.6. the parent object, as defined in Section 3.6.
o One or two <org:postalInfo> elements that contain postal-address o One or two <org:postalInfo> elements that contain postal-address
information. Two elements are provided so that address information. Two elements are provided so that address
information can be provided in both internationalized and information can be provided in both internationalized and
localized forms; a "type" attribute is used to identify the two localized forms; a "type" attribute is used to identify the two
forms. If an internationalized form (type="int") is provided, forms. If an internationalized form (type="int") is provided,
element content MUST be represented in a subset of UTF-8 that can element content MUST be represented in a subset of UTF-8 that can
skipping to change at page 11, line 38 skipping to change at page 12, line 23
organization object creation. organization object creation.
o A <org:upID> element that contains the identifier of the client o A <org:upID> element that contains the identifier of the client
that last updated the organization object. This element MUST NOT that last updated the organization object. This element MUST NOT
be present if the organization has never been modified. be present if the organization has never been modified.
o A <org:upDate> element that contains the date and time of the most o A <org:upDate> element that contains the date and time of the most
recent organization object modification. This element MUST NOT be recent organization object modification. This element MUST NOT be
present if the organization object has never been modified. present if the organization object has never been modified.
Example <info> response for "Example Registrar Inc." registrar object Example <info> response for "Example Registrar Inc." organization
with registrar identifier "1362": object with registrar identifier "1362":
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <resData> S: <resData>
S: <org:infData S: <org:infData
S: xmlns:org="urn:ietf:params:xml:ns:org-1.0"> S: xmlns:org="urn:ietf:params:xml:ns:org-1.0">
skipping to change at page 13, line 4 skipping to change at page 14, line 4
S: <org:upID>ClientX</org:upID> S: <org:upID>ClientX</org:upID>
S: <org:upDate>1999-12-03T09:00:00.0Z</org:upDate> S: <org:upDate>1999-12-03T09:00:00.0Z</org:upDate>
S: </org:infData> S: </org:infData>
S: </resData> S: </resData>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID> S: <svTRID>54322-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
Example <info> response for "Example Reseller Inc." reseller object Example <info> response for "Example Reseller Inc." organization
managed by registrar identifier "1362": object of reseller type managed by registrar identifier "1362":
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <resData> S: <resData>
S: <org:infData S: <org:infData
S: xmlns:org="urn:ietf:params:xml:ns:org-1.0"> S: xmlns:org="urn:ietf:params:xml:ns:org-1.0">
skipping to change at page 14, line 14 skipping to change at page 15, line 14
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> Command
The transfer semantics does not apply to organization object. No EPP The transfer semantics does not apply to organization object. No EPP
<transfer> command is defined in this document. <transfer> command is defined in this document.
4.2. EPP Transform Commands 4.2. EPP Transform Commands
EPP provides four commands to transform organization-object EPP provides four commands to transform organization object
information: <create> to create an instance of an organization information: <create> to create an instance of an organization
object, <delete> to delete an instance of an organization object, object, <delete> to delete an instance of an organization object,
<transfer> to manage organization-object sponsorship changes, and <transfer> to manage organization-object sponsorship changes, and
<update> to change information associated with an organization <update> to change information associated with an organization
object. This document does not define a mapping for the EPP object. This document does not define a mapping for the EPP
<transfer> and <renew> command. <transfer> and <renew> command.
Transform commands are typically processed and completed in real Transform commands are typically processed and completed in real
time. Server operators MAY receive and process transform commands time. Server operators MAY receive and process transform commands
but defer completing the requested action if human or third-party but defer completing the requested action if human or third-party
skipping to change at page 21, line 23 skipping to change at page 22, line 23
element content MUST be represented in a subset of UTF-8 that can element content MUST be represented in a subset of UTF-8 that can
be represented in the 7-bit US-ASCII character set. If a be represented in the 7-bit US-ASCII character set. If a
localized form (type="loc") is provided, element content MAY be localized form (type="loc") is provided, element content MAY be
represented in unrestricted UTF-8. The change of the postal info represented in unrestricted UTF-8. The change of the postal info
is defined as a replacement of that postal info element with the is defined as a replacement of that postal info element with the
contents of the sub-elements included in the update command. An contents of the sub-elements included in the update command. An
empty <org:postalInfo> element is supported to allow a type of empty <org:postalInfo> element is supported to allow a type of
postal info to be removed. The <org:postalInfo> element contains postal info to be removed. The <org:postalInfo> element contains
the following child elements: the following child elements:
o
* A <org:name> element that contains the name of the * A <org:name> element that contains the name of the
organization. organization.
* A <org:addr> element that contains address information * A <org:addr> element that contains address information
associated with the organization. A <org:addr> element associated with the organization. A <org:addr> element
contains the following child elements: contains the following child elements:
+ One, two, or three OPTIONAL <org:street> elements that + One, two, or three OPTIONAL <org:street> elements that
contain the organization's street address. contain the organization's street address.
skipping to change at page 26, line 31 skipping to change at page 27, line 31
<!-- <!--
Child elements of the <create> command. Child elements of the <create> command.
--> -->
<complexType name="createType"> <complexType name="createType">
<sequence> <sequence>
<element name="id" <element name="id"
type="eppcom:clIDType"/> type="eppcom:clIDType"/>
<element name="role" <element name="role"
type="org:roleType"/> type="org:roleType"/>
<element name="status" <element name="status"
type="org:statusType" default="ok"/> type="org:statusType" default="ok" maxOccurs="9"/>
<element name="parentId" <element name="parentId"
type="eppcom:clIDType" minOccurs="0"/> type="eppcom:clIDType" minOccurs="0"/>
<element name="postalInfo" <element name="postalInfo"
type="org:postalInfoType" maxOccurs="2"/> type="org:postalInfoType" maxOccurs="2"/>
<element name="voice" <element name="voice"
type="contact:e164Type" minOccurs="0"/> type="contact:e164Type" minOccurs="0"/>
<element name="fax" <element name="fax"
type="contact:e164Type" minOccurs="0"/> type="contact:e164Type" minOccurs="0"/>
<element name="email" <element name="email"
type="eppcom:minTokenType"/> type="eppcom:minTokenType"/>
skipping to change at page 31, line 11 skipping to change at page 32, line 11
registry or registrar). registry or registrar).
Registrant Name: IESG Registrant Name: IESG
Registrant Contact Information: iesg@ietf.org Registrant Contact Information: iesg@ietf.org
Value: privacyproxy Value: privacyproxy
Type: role Type: role
Description: The entity object instance represents a third-party who Description: The entity object instance represents a third-party who
could help to register a domain without exposing their private could help to register a domain without exposing the registrants'
information. private information..
Registrant Name: IESG Registrant Name: IESG
Registrant Contact Information: iesg@ietf.org Registrant Contact Information: iesg@ietf.org
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
[RFC6982] before publication. This section records the status of [RFC6982] 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
skipping to change at page 31, line 45 skipping to change at page 32, line 45
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".
CNNIC is in the process of development research to update EPP CNNIC is in the process of development research to update EPP
organization mapping from reseller mapping. Verisign is also organization mapping from reseller mapping. Verisign is also
planning to implement this document. planning to implement this document.
8.1. CNNIC Impelementation 8.1. CNNIC Implementation
Organization: CNNIC Organization: CNNIC
Name: EPP Organization Mapping Name: EPP Organization Mapping
Description: CNNIC is trying to update EPP organizaiton mapping from Description: CNNIC is trying to update EPP organization mapping from
previous reseller mapping according to this document. previous reseller mapping according to this document.
Level of maturity: Research. Level of maturity: Research.
Coverage: EPP organization mapping. Coverage: EPP organization mapping.
Contact: zhouguiqing@cnnic.cn Contact: zhouguiqing@cnnic.cn
8.2. Reseller Extension 8.2. Reseller Extension
This document was updated from draft-ietf-regext-reseller. CNNIC, This document was updated from draft-ietf-regext-reseller. CNNIC,
Verisign and Patrick Mevzek have already implemented the reseller Verisign and Net::DRI (Patrick Mevzek) have already implemented the
mapping. reseller mapping.
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] or those caused by considerations beyond those described by [RFC5730] or those caused by
the protocol layers used by EPP. The security considerations the protocol layers used by EPP. The security considerations
described in these other specifications apply to this specification described in these other specifications apply to this specification
as well. as well.
10. Acknowledgement 10. Acknowledgment
The authors would like to thank Rik Ribbers, Marc Groeneweg, Patrick The authors would like to thank Rik Ribbers, Marc Groeneweg, Patrick
Mevzek, Antoin Verschuren and Scott Hollenbeck for their careful Mevzek, Antoin Verschuren and Scott Hollenbeck for their careful
review and valuable comments. review and valuable comments.
11. Normative References 11. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
skipping to change at page 34, line 27 skipping to change at page 35, line 27
* Updated url definition. * Updated url definition.
* Updated XML schema. * Updated XML schema.
-03: -03:
* Changed author information. * Changed author information.
* Updated section 3.1. * Updated section 3.1.
* Refactored the XSD file. Added <chgPostalInfoType> element. * Refactoried the XSD file. Added <chgPostalInfoType> element.
* Added acknowledgement. * Added acknowledgment.
WG document-00: WG document submitted WG document-00: WG document submitted
WG document-01: Keep document alive for further discussion. WG document-01: Keep document alive for further discussion.
Reseller object or entity object with multiple roles? Reseller object or entity object with multiple roles?
Organization WG document-00: Change to a generic organization object Organization WG document-00: Change to a generic organization object
mapping. mapping.
Organization WG document-01: Added "Imeplementation Status" section. Organization WG document-01: Added "Implementation Status" section.
Authors' Addresses Organization WG document-02: Accepted some of the feedbacks on the
mailing list.
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
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
Guiqing Zhou Guiqing Zhou
 End of changes. 32 change blocks. 
62 lines changed or deleted 83 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/