draft-ietf-regext-org-09.txt   draft-ietf-regext-org-10.txt 
Internet Engineering Task Force L. Zhou Internet Engineering Task Force L. Zhou
Internet-Draft CNNIC Internet-Draft CNNIC
Intended status: Standards Track N. Kong Intended status: Standards Track N. Kong
Expires: February 21, 2019 Consultant Expires: February 25, 2019 Consultant
G. Zhou G. Zhou
J. Yao J. Yao
CNNIC CNNIC
J. Gould J. Gould
Verisign, Inc. Verisign, Inc.
August 20, 2018 August 24, 2018
Extensible Provisioning Protocol (EPP) Organization Mapping Extensible Provisioning Protocol (EPP) Organization Mapping
draft-ietf-regext-org-09 draft-ietf-regext-org-10
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 objects mapping for provisioning and management of organization objects
stored in a shared central repository. Specified in Extensible stored in a shared central repository. Specified in Extensible
Markup 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
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 February 21, 2019. This Internet-Draft will expire on February 25, 2019.
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 8, line 28 skipping to change at page 8, line 28
o One or more <org:id> elements that contain the server-unique o One or more <org:id> elements that contain the server-unique
identifier of the organization objects to be queried. identifier of the organization objects to be queried.
Example <check> command: Example <check> command:
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: <check> C: <check>
C: <org:check C: <org:check
C: xmlns:org="urn:ietf:params:xml:ns:org-1.0"> C: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
C: <org:id>res1523</org:id> C: <org:id>res1523</org:id>
C: <org:id>re1523</org:id> C: <org:id>re1523</org:id>
C: <org:id>1523res</org:id> C: <org:id>1523res</org:id>
C: </org:check> C: </org:check>
C: </check> C: </check>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
When a <check> command has been processed successfully, the EPP When a <check> command has been processed successfully, the EPP
skipping to change at page 9, line 24 skipping to change at page 9, line 24
Example <check> response: Example <check> response:
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 lang="en">Command completed successfully</msg> S: <msg lang="en">Command completed successfully</msg>
S: </result> S: </result>
S: <resData> S: <resData>
S: <org:chkData S: <org:chkData
S: xmlns:org="urn:ietf:params:xml:ns:org-1.0"> S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
S: <org:cd> S: <org:cd>
S: <org:id avail="1">res1523</org:id> S: <org:id avail="1">res1523</org:id>
S: </org:cd> S: </org:cd>
S: <org:cd> S: <org:cd>
S: <org:id avail="0">re1523</org:id> S: <org:id avail="0">re1523</org:id>
S: <org:reason lang="en">In use</org:reason> S: <org:reason lang="en">In use</org:reason>
S: </org:cd> S: </org:cd>
S: <org:cd> S: <org:cd>
S: <org:id avail="1">1523res</org:id> S: <org:id avail="1">1523res</org:id>
S: </org:cd> S: </org:cd>
skipping to change at page 10, line 19 skipping to change at page 10, line 19
o An <org:id> element that contains the server-unique identifier of o An <org:id> element that contains the server-unique identifier of
the organization object to be queried. the organization object to be queried.
Example <info> command: Example <info> command:
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: <info> C: <info>
C: <org:info C: <org:info
C: xmlns:org="urn:ietf:params:xml:ns:org-1.0"> C: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
C: <org:id>res1523</org:id> C: <org:id>res1523</org:id>
C: </org:info> C: </org:info>
C: </info> C: </info>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
When an <info> command has been processed successfully, the EPP When an <info> command has been processed successfully, the EPP
<resData> element MUST contain a child <org:infData> element. This <resData> element MUST contain a child <org:infData> element. This
element or its ancestor element MUST identify the organization element or its ancestor element MUST identify the organization
skipping to change at page 12, line 49 skipping to change at page 12, line 49
organization object with identifier "registrar1362": organization object with identifier "registrar1362":
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 lang="en">Command completed successfully</msg> S: <msg lang="en">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:epp:org-1.0">
S: <org:id>registrar1362</org:id> S: <org:id>registrar1362</org:id>
S: <org:roid>registrar1362-REP</org:roid> S: <org:roid>registrar1362-REP</org:roid>
S: <org:role> S: <org:role>
S: <org:type>registrar</org:type> S: <org:type>registrar</org:type>
S: <org:status>ok</org:status> S: <org:status>ok</org:status>
S: <org:status>linked</org:status> S: <org:status>linked</org:status>
S: <org:roleID>1362</org:roleID> S: <org:roleID>1362</org:roleID>
S: </org:role> S: </org:role>
S: <org:status>ok</org:status> S: <org:status>ok</org:status>
S: <org:postalInfo type="int"> S: <org:postalInfo type="int">
skipping to change at page 14, line 13 skipping to change at page 14, line 13
object of reseller type managed by identifier "registrar1362": object of reseller type managed by identifier "registrar1362":
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 lang="en">Command completed successfully</msg> S: <msg lang="en">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:epp:org-1.0">
S: <org:id>reseller1523</org:id> S: <org:id>reseller1523</org:id>
S: <org:roid>reseller1523-REP</org:roid> S: <org:roid>reseller1523-REP</org:roid>
S: <org:role> S: <org:role>
S: <org:type>reseller</org:type> S: <org:type>reseller</org:type>
S: <org:status>ok</org:status> S: <org:status>ok</org:status>
S: <org:status>linked</org:status> S: <org:status>linked</org:status>
S: </org:role> S: </org:role>
S: <org:status>ok</org:status> S: <org:status>ok</org:status>
S: <org:parentId>registrar1362</org:parentId> S: <org:parentId>registrar1362</org:parentId>
S: <org:postalInfo type="int"> S: <org:postalInfo type="int">
skipping to change at page 18, line 10 skipping to change at page 18, line 10
identifiers for the contact objects associated with the identifiers for the contact objects associated with the
organization object. organization object.
Example <create> command: Example <create> command:
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: <create> C: <create>
C: <org:create C: <org:create
C: xmlns:org="urn:ietf:params:xml:ns:org-1.0"> C: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
C: <org:id>res1523</org:id> C: <org:id>res1523</org:id>
C: <org:role> C: <org:role>
C: <org:type>reseller</org:type> C: <org:type>reseller</org:type>
C: </org:role> C: </org:role>
C: <org:parentId>1523res</org:parentId> C: <org:parentId>1523res</org:parentId>
C: <org:postalInfo type="int"> C: <org:postalInfo type="int">
C: <org:name>Example Organization Inc.</org:name> C: <org:name>Example Organization Inc.</org:name>
C: <org:addr> C: <org:addr>
C: <org:street>123 Example Dr.</org:street> C: <org:street>123 Example Dr.</org:street>
C: <org:street>Suite 100</org:street> C: <org:street>Suite 100</org:street>
skipping to change at page 19, line 13 skipping to change at page 19, line 13
Example <create> response: Example <create> response:
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 lang="en">Command completed successfully</msg> S: <msg lang="en">Command completed successfully</msg>
S: </result> S: </result>
S: <resData> S: <resData>
S: <org:creData S: <org:creData
S: xmlns:org="urn:ietf:params:xml:ns:org-1.0"> S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
S: <org:id>res1523</org:id> S: <org:id>res1523</org:id>
S: <org:crDate>1999-04-03T22:00:00.0Z</org:crDate> S: <org:crDate>1999-04-03T22:00:00.0Z</org:crDate>
S: </org:creData> S: </org:creData>
S: </resData> S: </resData>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
skipping to change at page 20, line 10 skipping to change at page 20, line 10
a 2305 error response code when a <delete> command is attempted and a 2305 error response code when a <delete> command is attempted and
fails due to existing object relationships. fails due to existing object relationships.
Example <delete> command: Example <delete> command:
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: <delete> C: <delete>
C: <org:delete C: <org:delete
C: xmlns:org="urn:ietf:params:xml:ns:org-1.0"> C: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
C: <org:id>res1523</org:id> C: <org:id>res1523</org:id>
C: </org:delete> C: </org:delete>
C: </delete> C: </delete>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
When a <delete> command has been processed successfully, a server When a <delete> command has been processed successfully, a server
MUST respond with an EPP response with no <resData> element. MUST respond with an EPP response with no <resData> element.
skipping to change at page 24, line 10 skipping to change at page 24, line 10
o An OPTIONAL <org:url> element that contains the URL to the website o An OPTIONAL <org:url> element that contains the URL to the website
of the organization. of the organization.
Example <update> command: Example <update> command:
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>
C: <org:update C: <org:update
C: xmlns:org="urn:ietf:params:xml:ns:org-1.0"> C: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
C: <org:id>res1523</org:id> C: <org:id>res1523</org:id>
C: <org:add> C: <org:add>
C: <org:contact type="tech">sh8013</org:contact> C: <org:contact type="tech">sh8013</org:contact>
C: <org:role> C: <org:role>
C: <org:type>privacyproxy</org:type> C: <org:type>privacyproxy</org:type>
C: <org:status>clientLinkProhibited</org:status> C: <org:status>clientLinkProhibited</org:status>
C: </org:role> C: </org:role>
C: <org:status>clientLinkProhibited</org:status> C: <org:status>clientLinkProhibited</org:status>
C: </org:add> C: </org:add>
C: <org:rem> C: <org:rem>
skipping to change at page 26, line 13 skipping to change at page 26, line 13
response to the <create> command. response to the <create> command.
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="1001"> S: <result code="1001">
S: <msg lang="en">Command completed successfully; action pending</msg> S: <msg lang="en">Command completed successfully; action pending</msg>
S: </result> S: </result>
S: <resData> S: <resData>
S: <org:creData S: <org:creData
S: xmlns:org="urn:ietf:params:xml:ns:org-1.0"> S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
S: <org:id>res1523</org:id> S: <org:id>res1523</org:id>
S: <org:crDate>1999-04-03T22:00:00.0Z</org:crDate> S: <org:crDate>1999-04-03T22:00:00.0Z</org:crDate>
S: </org:creData> S: </org:creData>
S: </resData> S: </resData>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
skipping to change at page 27, line 22 skipping to change at page 27, line 22
S: <response> S: <response>
S: <result code="1301"> S: <result code="1301">
S: <msg lang="en">Command completed successfully; ack to dequeue</msg> S: <msg lang="en">Command completed successfully; ack to dequeue</msg>
S: </result> S: </result>
S: <msgQ count="5" id="12345"> S: <msgQ count="5" id="12345">
S: <qDate>1999-04-04T22:01:00.0Z</qDate> S: <qDate>1999-04-04T22:01:00.0Z</qDate>
S: <msg>Pending action completed successfully.</msg> S: <msg>Pending action completed successfully.</msg>
S: </msgQ> S: </msgQ>
S: <resData> S: <resData>
S: <org:panData S: <org:panData
S: xmlns:org="urn:ietf:params:xml:ns:org-1.0"> S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
S: <org:id paResult="1">res1523</org:id> S: <org:id paResult="1">res1523</org:id>
S: <org:paTRID> S: <org:paTRID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </org:paTRID> S: </org:paTRID>
S: <org:paDate>1999-04-04T22:00:00.0Z</org:paDate> S: <org:paDate>1999-04-04T22:00:00.0Z</org:paDate>
S: </org:panData> S: </org:panData>
S: </resData> S: </resData>
S: <trID> S: <trID>
S: <clTRID>BCD-23456</clTRID> S: <clTRID>BCD-23456</clTRID>
skipping to change at page 28, line 4 skipping to change at page 28, line 4
An EPP object mapping is specified in XML Schema notation. The An EPP object mapping is specified in XML Schema notation. The
formal syntax presented here is a complete schema representation of formal syntax presented here is a complete schema representation of
the object mapping suitable for automated validation of EPP XML the object mapping suitable for automated validation of EPP XML
instances. The BEGIN and END tags are not part of the schema; they instances. The BEGIN and END tags are not part of the schema; they
are used to note the beginning and ending of the schema for URI are used to note the beginning and ending of the schema for URI
registration purposes. registration purposes.
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:org-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:epp:org-1.0"
xmlns:org="urn:ietf:params:xml:ns:org-1.0" xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0"
xmlns:epp="urn:ietf:params:xml:ns:epp-1.0" xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- <!--
Import common element types. Import common element types.
--> -->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
<import namespace="urn:ietf:params:xml:ns:epp-1.0"/> <import namespace="urn:ietf:params:xml:ns:epp-1.0"/>
skipping to change at page 34, line 39 skipping to change at page 34, line 39
<sequence> <sequence>
<element name="cd" type="org:checkType" <element name="cd" type="org:checkType"
maxOccurs="unbounded" /> maxOccurs="unbounded" />
</sequence> </sequence>
</complexType> </complexType>
<complexType name="checkType"> <complexType name="checkType">
<sequence> <sequence>
<element name="id" type="org:checkIDType" /> <element name="id" type="org:checkIDType" />
<element name="reason" type="eppcom:reasonType" <element name="reason" type="eppcom:reasonType"
minOccurs="0" maxOccurs="5" /> minOccurs="0" />
</sequence> </sequence>
</complexType> </complexType>
<complexType name="checkIDType"> <complexType name="checkIDType">
<simpleContent> <simpleContent>
<extension base="eppcom:clIDType"> <extension base="eppcom:clIDType">
<attribute name="avail" type="boolean" <attribute name="avail" type="boolean"
use="required" /> use="required" />
</extension> </extension>
</simpleContent> </simpleContent>
skipping to change at page 44, line 33 skipping to change at page 44, line 33
* Updated XML schema for the maxOccurs value of "reason" element. * Updated XML schema for the maxOccurs value of "reason" element.
* Updated section 7.3. * Updated section 7.3.
* Replaced "http" with "https" in the examples. * Replaced "http" with "https" in the examples.
* Updated writing typos. * Updated writing typos.
* Modified XML namespace and schema. * Modified XML namespace and schema.
Organization WG document-10:
* Modified XML namespace and schema.
* Removed the maxOccurs value of "reason" element.
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
Email: zhoulinlin@cnnic.cn Email: zhoulinlin@cnnic.cn
Ning Kong Ning Kong
Consultant Consultant
Email: ietfing@gmail.com Email: ietfing@gmail.com
Guiqing Zhou Guiqing 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
Email: zhouguiqing@cnnic.cn Email: zhouguiqing@cnnic.cn
Jiankang Yao Jiankang Yao
CNNIC CNNIC
 End of changes. 20 change blocks. 
19 lines changed or deleted 25 lines changed or added

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