draft-ietf-regext-org-ext-07.txt   draft-ietf-regext-org-ext-08.txt 
Internet Engineering Task Force L. Zhou Internet Engineering Task Force L. Zhou
Internet-Draft N. Kong Internet-Draft CNNIC
Intended status: Standards Track J. Wei Intended status: Standards Track N. Kong
Expires: December 17, 2018 X. Lee Expires: February 21, 2019 Consultant
J. Wei
J. Yao
CNNIC CNNIC
J. Gould J. Gould
Verisign, Inc. Verisign, Inc.
June 15, 2018 August 20, 2018
Organization Extension for the Extensible Provisioning Protocol (EPP) Organization Extension for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-org-ext-07 draft-ietf-regext-org-ext-08
Abstract Abstract
This document describes an extension to EPP object mappings, which is This document describes an extension to EPP object mappings, which is
designed to support assigning an organization to any existing object designed to support assigning an organization to any existing object
(domain, host, contact) as well as any future objects. (domain, host, contact) as well as any future 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
skipping to change at page 1, line 36 skipping to change at page 1, line 38
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 December 17, 2018. This Internet-Draft will expire on February 21, 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
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
described in the Simplified BSD License. described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
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> Query 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 . . . . . . . . . . . . . . . . . . . . . 18
7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 17 7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 18
7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 18 7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 18
8. Implementation Status . . . . . . . . . . . . . . . . . . . . 18 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 19
8.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 19 8.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 19
8.2. CNNIC Implementation . . . . . . . . . . . . . . . . . . 19 8.2. CNNIC Implementation . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . 21 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24
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 be of entities: a registrant, a registrar and a registry. There may be
other roles of entities involved in the domain registration process other roles of entities involved in the domain registration process
which are not formally defined, such as resellers, DNS service which are not formally defined, such as resellers, DNS service
operators, privacy proxy, etc. operators, privacy proxies, 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 an 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 record for the delegation. A privacy proxy is nor the registrar of record for the delegation. A privacy proxy is
an entity used for domain registrations to protect the private an entity used for domain registrations to protect the private
information of the individuals and organizations. These kind of information of the individuals and organizations. These kind of
entities are defined as "organizations" with different role types in entities are defined as "organizations" with different role types 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
skipping to change at page 3, line 42 skipping to change at page 3, line 31
this document MUST reference the existing organization identifier. this document MUST reference the existing organization identifier.
This document is specified using the XML 1.0 as described in This document 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
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in BCP 14
[RFC2119][RFC8174] when, and only when, they appear in all capitals,
as shown here.
In examples, "C:" represents lines sent by a protocol client and "S:" In examples, "C:" represents lines sent by a protocol client and "S:"
represents lines returned by a protocol server. Indentation and represents lines returned by a protocol server. Indentation and
white space in examples are provided only to illustrate element white space in examples are provided only to illustrate element
relationships and are not a REQUIRED feature of this specification. relationships and are not a required feature of this specification.
XML is case sensitive. Unless stated otherwise, XML specifications XML is case sensitive. Unless stated otherwise, XML specifications
and examples provided in this document MUST be interpreted in the and examples provided in this document MUST be interpreted in the
character case presented to develop a conforming implementation. character case presented to develop a conforming implementation.
orgext-1.0 in this document is used as an abbreviation for The XML namespace prefix "orgext" is used, but implementations MUST
urn:ietf:params:xml:ns:orgext-1.0. The XML namespace prefix "orgext" NOT depend on it and instead employ a proper namespace-aware XML
is used, but implementations MUST NOT depend on it and instead employ parser and serializer to interpret and output the XML documents.
a proper namespace-aware XML parser and serializer to interpret and
output the XML documents.
3. Object Attributes 3. Object Attributes
This extension adds additional elements to EPP object mappings like This extension adds additional elements to EPP object mappings like
the EPP domain name mapping [RFC5731]. Only the new elements are the EPP domain name mapping [RFC5731]. Only the new elements are
described here. described here.
3.1. Organization Identifier 3.1. Organization Identifier
Organization identifier provides the ID of an organization. Its Organization identifier provides the ID of an organization. Its
skipping to change at page 4, line 46 skipping to change at page 4, line 40
an object, and <transfer> to retrieve object transfer status an object, and <transfer> to retrieve object transfer status
information. information.
4.1.1. EPP <check> Command 4.1.1. EPP <check> Command
This extension does not add any elements to the EPP <check> command This extension does not add any elements to the EPP <check> command
or <check> response described in the EPP object mapping. or <check> response described in the EPP object mapping.
4.1.2. EPP <info> Command 4.1.2. EPP <info> Command
This extension does not add any element to the EPP <info> command This extension does not add any elements to the EPP <info> command
described in the EPP object mapping. However, additional elements described in the EPP object mapping. However, additional elements
are defined for the <info> response in the EPP object mapping. are defined for the <info> response in the EPP object mapping.
When an <info> command has been processed successfully, the EPP When an <info> command has been processed successfully, the EPP
<resData> element MUST contain child elements as described in the EPP <resData> element MUST contain child elements as described in the EPP
object extensions. In addition, the EPP <extension> element SHOULD object extensions. In addition, the EPP <extension> element SHOULD
contain a child <orgext:infData> element that identifies the contain a child <orgext:infData> element. This element or its
extension namespace if the object has data associated with this ancestor element MUST identify the extension namespace if the object
extension and based on server policy. The <orgext:infData> element has data associated with this extension and based on server policy.
contains the following child elements: The <orgext:infData> element contains the following child elements:
o Zero or more <orgext:id> elements are allowed that contains the o Zero or more <orgext:id> elements are allowed that contain the
identifier of the organization. The "role" attribute is used to identifier of the organization. The "role" attribute is used to
represent the relationship that the organization has to the represent the relationship that the organization has to the
object. See Section 7.3 in [ID.draft-ietf-regext-org] for a list object. See Section 7.3 in [ID.draft-ietf-regext-org] for a list
of values. of values.
Example <info> response for an authorized client with multiple Example <info> response for an authorized client with multiple
organizations: organizations:
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">
skipping to change at page 8, line 23 skipping to change at page 8, line 23
4.2.1. EPP <create> Command 4.2.1. EPP <create> Command
This extension defines additional elements for the EPP <create> This extension defines additional elements for the EPP <create>
command described in the EPP object extensions. No additional command described in the EPP object extensions. No additional
elements are defined for the EPP <create> response. elements are defined for the EPP <create> response.
The EPP <create> command provides a transform operation that allows a The EPP <create> command provides a transform operation that allows a
client to create an object. In addition to the EPP command elements client to create an object. In addition to the EPP command elements
described in the EPP object extensions, the command MUST contain an described in the EPP object extensions, the command MUST contain an
<extension> element, and the <extension> element MUST contain a child <extension> element, and the <extension> element MUST contain a child
<orgext:create> element that identifies the extension namespace if <orgext:create> element. This element or its ancestor element MUST
the client wants to associate data defined in this extension to the identify the extension namespace if the client wants to associate
object. The <orgext:create> element contains the following child data defined in this extension to the object. The <orgext:create>
elements: element contains the following child elements:
o One or more <orgext:id> elements that contains the identifier of o One or more <orgext:id> elements that contain 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 <create> Command with only one organization: Example <create> Command with only one organization:
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>
skipping to change at page 11, line 24 skipping to change at page 11, line 24
This extension defines additional elements for the EPP <update> This extension defines additional elements for the EPP <update>
command described in the EPP domain mapping [RFC5731], host mapping command described in the EPP domain mapping [RFC5731], host mapping
[RFC5732] and contact mapping [RFC5733]. No additional elements are [RFC5732] and contact mapping [RFC5733]. No additional elements are
defined for the EPP <update> response. defined for the EPP <update> response.
The EPP <update> command provides a transform operation that allows a The EPP <update> command provides a transform operation that allows a
client to modify the attributes of an object. In addition to the EPP client to modify the attributes of an object. In addition to the EPP
<update> command elements, the command MUST contain an <extension> <update> command elements, the command MUST contain an <extension>
element, and the <extension> element MUST contain a child element, and the <extension> element MUST contain a child
<orgext:update> element that identifies the extension namespace if <orgext:update> element. This element or its ancestor element MUST
the client wants to update the object with data defined in this identify the extension namespace if the client wants to update the
extension. The <orgext:update> element contains the following child object with data defined in this extension. The <orgext:update>
elements: element contains the following child elements:
o An OPTIONAL <orgext:add> element that contains attribute values to o An OPTIONAL <orgext:add> element that contains attribute values to
be added to the object. be added to the object.
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> Exactly one <orgext:add>, <orgext:rem> or <orgext:chg> element MUST
element MUST be provided. The <orgext:add>, <orgext:rem> and be provided. The <orgext:add>, <orgext:rem> and <orgext:chg>
<orgext:chg> elements contain the following child element: elements contain the following child element:
o One or more <orgext:id> elements that contains the identifier of o One or more <orgext:id> elements that contain 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 15, line 5 skipping to change at page 15, line 5
C: </orgext:chg> C: </orgext:chg>
C: </orgext:update> C: </orgext:update>
C: </extension> C: </extension>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
When an extended <update> command has been processed successfully, When an extended <update> command has been processed successfully,
the EPP response is as described in the EPP object extension. the EPP response is as described in the EPP object extension.
An EPP error response MUST be returned if an <update> command cannot
be processed for any reason. An attempt to add one organization ID
or multiple organization IDs with a particular role value when at
least one of them already exists does not change the object at all.
A server SHOULD notify clients that object relationships exist by
sending a 2305 error response code. An attempt to remove an
organization ID or multiple organization IDs with a particular role
value when at least one of them does not exist does not change the
object at all. A server SHOULD notify clients that object
relationships does not exist by sending a 2305 error response code.
An attempt to change an organization ID or multiple organization IDs
with a particular role value when at least one of them does not exist
does not change the object at all. A server SHOULD notify clients
that object relationships does not exist by sending a 2305 error
response code. Response format with error value elements is defined
in Section 2.6 of [RFC5730].
5. Formal Syntax 5. Formal Syntax
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
skipping to change at page 17, line 49 skipping to change at page 18, line 21
includes this extension. includes this extension.
7. IANA Considerations 7. IANA Considerations
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 extension namespace:
URI: urn:ietf:params:xml:ns:epp:orgext-1.0
Registrant Contact: IESG
XML: None. Namespace URIs do not represent an XML specification.
Registration request for the organization XML schema:
URI: urn:ietf:params:xml:schema:epp:orgext-1.0
URI: urn:ietf:params:xml:ns:orgext-1.0
Registrant Contact: IESG Registrant Contact: IESG
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:
skipping to change at page 20, line 46 skipping to change at page 21, line 23
[RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733,
August 2009, <https://www.rfc-editor.org/info/rfc5733>. August 2009, <https://www.rfc-editor.org/info/rfc5733>.
[RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
Code: The Implementation Status Section", BCP 205, Code: The Implementation Status Section", BCP 205,
RFC 7942, DOI 10.17487/RFC7942, July 2016, RFC 7942, DOI 10.17487/RFC7942, July 2016,
<https://www.rfc-editor.org/info/rfc7942>. <https://www.rfc-editor.org/info/rfc7942>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[W3C.REC-xml-20040204] [W3C.REC-xml-20040204]
Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and
F. Yergeau, ""Extensible Markup Language (XML) 1.0 (Third F. Yergeau, ""Extensible Markup Language (XML) 1.0 (Third
Edition)", World Wide Web Consortium FirstEdition REC-xml- Edition)", World Wide Web Consortium FirstEdition REC-xml-
20040204", February 2004, 20040204", February 2004,
<http://www.w3.org/TR/2004/REC-xml-20040204>. <http://www.w3.org/TR/2004/REC-xml-20040204>.
[W3C.REC-xmlschema-1-20041028] [W3C.REC-xmlschema-1-20041028]
Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn,
""XML Schema Part 1: Structures Second Edition", World ""XML Schema Part 1: Structures Second Edition", World
skipping to change at page 23, line 33 skipping to change at page 24, line 19
* Added "Query" for "<Transfer> Query Command". * Added "Query" for "<Transfer> Query Command".
* Change "Registrant Contact" to IESG in section 7.1. * Change "Registrant Contact" to IESG in section 7.1.
* Modified section 7.2. * Modified section 7.2.
Organization WG document-07: Organization WG document-07:
* Updated "Abstraction". * Updated "Abstraction".
Organization WG document-08:
* Updated error codes of <update> response.
* Modified XML namespace and schema.
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
Email: zhoulinlin@cnnic.cn Email: zhoulinlin@cnnic.cn
Ning Kong Ning Kong
CNNIC Consultant
4 South 4th Street, Zhongguancun, Haidian District
Beijing, Beijing 100190 Email: ietfing@gmail.com
China
Phone: +86 10 5881 3147
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
Email: weijunkai@cnnic.cn Email: weijunkai@cnnic.cn
Jiankang Yao
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
Email: xl@cnnic.cn Email: yaojk@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. 35 change blocks. 
68 lines changed or deleted 88 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/