draft-ietf-regext-org-ext-03.txt   draft-ietf-regext-org-ext-04.txt 
Internet Engineering Task Force L. Zhou Internet Engineering Task Force L. Zhou
Internet-Draft N. Kong Internet-Draft N. Kong
Intended status: Standards Track J. Wei Intended status: Standards Track J. Wei
Expires: October 29, 2018 X. Lee Expires: November 5, 2018 X. Lee
CNNIC CNNIC
J. Gould J. Gould
VeriSign, Inc. Verisign, Inc.
April 27, 2018 May 4, 2018
Organization Extension for the Extensible Provisioning Protocol (EPP) Organization Extension for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-org-ext-03 draft-ietf-regext-org-ext-04
Abstract Abstract
This mapping, an extension to EPP object mappings like the EPP domain This mapping, an extension to EPP object mappings like the EPP domain
name mapping [RFC5731], to support assigning an organization to any name mapping [RFC5731], to support assigning an organization to any
existing object (domain, host, contact) as well as any future existing object (domain, host, contact) as well as any future
objects. objects.
Status of This Memo Status of This Memo
skipping to change at page 1, line 37 skipping to change at page 1, line 37
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 29, 2018. This Internet-Draft will expire on November 5, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 38 skipping to change at page 2, line 38
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> Command . . . . . . . . . . . . . . . 7 4.1.3. EPP <transfer> 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 . . . . . . . . . . . . . 18 6. Internationalization Considerations . . . . . . . . . . . . . 17
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 18 7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 17
7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 18 7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 18
8. Implementation Status . . . . . . . . . . . . . . . . . . . . 19 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 18
8.1. CNNIC Implementation . . . . . . . . . . . . . . . . . . 19 8.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 19
8.2. Reseller Extension . . . . . . . . . . . . . . . . . . . 20 8.2. CNNIC Implementation . . . . . . . . . . . . . . . . . . 19
8.3. Reseller Extension . . . . . . . . . . . . . . . . . . . 20
9. Security Considerations . . . . . . . . . . . . . . . . . . . 20 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 . . . . . . . . . . . . . . . . . . . . . . . 23
1. Introduction 1. Introduction
In the business model of domain registration, we usually have 3 roles In the business model of domain registration, we usually have 3 roles
of entities, a registrant, a registrar and a registry. There may of entities, a registrant, a registrar and a registry. There may
have some other roles of entities involved in the domain registration have some other roles of entities involved in the domain registration
process which are not formally defined, such as resellers, DNS process which are not formally defined, such as resellers, DNS
service operators, privacy proxy, etc. service operators, privacy proxy, etc.
skipping to change at page 4, line 10 skipping to change at page 4, line 14
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 orgext-1.0 in this document is used as an abbreviation for
urn:ietf:params:xml:ns:orgext-1.0. urn:ietf:params:xml:ns:orgext-1.0.
3. Object Attributes 3. Object Attributes
This extension adds additional elements to the EPP domain name This extension adds additional elements to EPP object mappings like
mapping [RFC5731]. Only the new elements are described here. the EPP domain name mapping [RFC5731]. Only the new elements are
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
corresponding element is <orgext:id> which refers to the corresponding element is <orgext:id> which refers to the
<organization:id> element defined in [ID.draft-ietf-regext-org]. All <organization:id> element defined in [ID.draft-ietf-regext-org]. All
organization objects are identified by a server-unique identifier. organization objects are identified by a server-unique identifier.
4. EPP Command Mapping 4. EPP Command Mapping
skipping to change at page 8, line 28 skipping to change at page 8, line 28
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 that identifies the extension namespace if
the client wants to associate data defined in this extension to the the client wants to associate data defined in this extension to the
object. The <orgext:create> element contains the following child object. The <orgext:create> element contains the following child
elements: elements:
o One or more <orgext:id> element that contains the identifier of o One or more <orgext:id> elements that contains the identifier of
the organization. The "role" attribute is used to represent the the organization. The "role" attribute is used to represent the
relationship that the organization has to the object. See relationship that the organization has to the object. See
Section 7.3 in [ID.draft-ietf-regext-org] for a list of values. Section 7.3 in [ID.draft-ietf-regext-org] for a list of values.
Example <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 12, line 50 skipping to change at page 12, line 50
C: <orgext:add> C: <orgext:add>
C: <orgext:id role="reseller">myreseller</orgext:id> C: <orgext:id role="reseller">myreseller</orgext:id>
C: <orgext:id role="privacyproxy">myproxy</orgext:id> C: <orgext:id role="privacyproxy">myproxy</orgext:id>
C: </orgext:add> C: </orgext:add>
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>
Example <update> command, domain with no organization:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
<command>
<update>
<domain:update
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
<domain:name>example.com</domain:name>
</domain:update>
</update>
<extension>
<orgext:update
xmlns:orgext="urn:ietf:params:xml:ns:orgext-1.0">
<orgext:add/>
</orgext:update>
</extension>
<clTRID>ABC-12345</clTRID>
</command>
</epp>
C:</epp>
Example <update> command, removing a reseller: Example <update> command, removing 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>
C: <domain:update C: <domain:update
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>example.com</domain:name> C: <domain:name>example.com</domain:name>
C: </domain:update> C: </domain:update>
skipping to change at page 17, line 5 skipping to change at page 16, line 27
</complexType> </complexType>
<!-- <!--
Child elements of <orgext:update> command Child elements of <orgext:update> command
--> -->
<complexType name="updateType"> <complexType name="updateType">
<sequence> <sequence>
<element <element
name="add" name="add"
type="orgext:addRemChgType" type="orgext:addRemChgType"
minOccurs="0"
/> />
<element <element
name="rem" name="rem"
type="orgext:addRemChgType" type="orgext:addRemChgType"
minOccurs="0"
/> />
<element <element
name="chg" name="chg"
type="orgext:addRemChgType" type="orgext:addRemChgType"
minOccurs="0"
/> />
</sequence> </sequence>
</complexType> </complexType>
<complexType name="addRemChgType"> <complexType name="addRemChgType">
<sequence> <sequence>
<!-- agent identifier the organization, <!-- agent identifier the organization,
e.g. registrar, reseller, privacy proxy, etc. --> e.g. registrar, reseller, privacy proxy, etc. -->
<element <element
name="id" name="id"
type="orgext:orgIdType" type="orgext:orgIdType"
minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
<!-- Child response element --> <!-- Child response element -->
<element <element
name="infData" name="infData"
type="orgext:infDataType"/> type="orgext:infDataType"/>
<!-- <orgext:infData> response elements --> <!-- <orgext:infData> response elements -->
<complexType name="infDataType"> <complexType name="infDataType">
<sequence> <sequence>
skipping to change at page 18, line 30 skipping to change at page 18, line 5
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 namespace:
o URI: urn:ietf:params:xml:ns:orgext-1.0 URI: urn:ietf:params:xml:ns:orgext-1.0
o Registrant Contact: See the "Author's Address" section of this Registrant Contact: See the "Author's Address" section of this
document. document.
o 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:
Name of Extension: Organization Extension Name of Extension: Organization Extension
Document status: Standards Track Document status: Standards Track
skipping to change at page 19, line 4 skipping to change at page 18, line 27
Name of Extension: Organization Extension Name of Extension: Organization Extension
Document status: Standards Track Document status: Standards Track
Reference: (insert reference to RFC version of this document) Reference: (insert reference to RFC version of this document)
Registrant Name and Email Address: IESG Registrant Name and Email Address: IESG
TLDs: any TLDs: any
IPR Disclosure: none IPR Disclosure: none
Status: active Status: active
Notes: none Notes: none
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 [RFC7942] 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
at the time of posting of this Internet-Draft, and is based on a at the time of posting of this Internet-Draft, and is based on a
proposal described in [RFC6982]. The description of implementations proposal described in [RFC7942]. The description of implementations
in this section is intended to assist the IETF in its decision in this section is intended to assist the IETF in its decision
processes in progressing drafts to RFCs. Please note that the processes in progressing drafts to RFCs. Please note that the
listing of any individual implementation here does not imply listing of any individual implementation here does not imply
endorsement by the IETF. Furthermore, no effort has been spent to endorsement by the IETF. Furthermore, no effort has been spent to
verify the information presented here that was supplied by IETF verify the information presented here that was supplied by IETF
contributors. This is not intended as, and must not be construed to contributors. This is not intended as, and must not be construed to
be, a catalog of available implementations or their features. be, a catalog of available implementations or their features.
Readers are advised to note that other implementations may exist. Readers are advised to note that other implementations may exist.
According to [RFC6982], "this will allow reviewers and working groups According to [RFC7942], "this will allow reviewers and working groups
to assign due consideration to documents that have the benefit of to assign due consideration to documents that have the benefit of
running code, which may serve as evidence of valuable experimentation running code, which may serve as evidence of valuable experimentation
and feedback that have made the implemented protocols more mature. and feedback that have made the implemented protocols more mature.
It is up to the individual working groups to use this information as It is up to the individual working groups to use this information as
they see fit". they see fit".
VeriSign has already implemented this extension. CNNIC and Net::DRI Verisign has already implemented this extension. CNNIC and Net::DRI
(Patrick Mevzek) are in the process of development research to update (Patrick Mevzek) are in the process of development research to update
organization extension from reseller extension. Dns Belgium is organization extension from reseller extension. Dns Belgium is
planning to implement it after the publication of this document. planning to implement it after the publication of this document.
8.1. CNNIC Implementation 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-ext.
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 Organization: CNNIC
Name: Organization Extension for EPP Name: Organization Extension for EPP
Description: CNNIC is trying to update organization extension from Description: CNNIC is trying to update organization extension from
previous reseller extension according to this document. previous reseller extension according to this document.
Level of maturity: Research. Level of maturity: Development
Coverage: Organization extension for EPP. Coverage: Organization extension for EPP
Contact: zhouguiqing@cnnic.cn Contact: zhouguiqing@cnnic.cn
8.2. Reseller Extension 8.3. Reseller Extension
This document was updated from draft-ietf-regext-reseller-ext. This document was updated from [ID.draft-ietf-regext-reseller-ext].
CNNIC, VeriSign and Net::DRI (Patrick Mevzek) have already CNNIC, Verisign and Net::DRI (Patrick Mevzek) have already
implemented this extension. implemented this extension.
9. Security Considerations 9. Security Considerations
The object mapping extension described in this document does not The object mapping extension described in this document does not
provide any other security services or introduce any additional provide any other security services or introduce any additional
considerations beyond those described by [RFC5730], [RFC5731], considerations beyond those described by [RFC5730], [RFC5731],
[RFC5732] and [RFC5733] or those caused by the protocol layers used [RFC5732] and [RFC5733] or those caused by the protocol layers used
by EPP. by EPP.
skipping to change at page 21, line 9 skipping to change at page 21, line 9
<https://www.rfc-editor.org/info/rfc5731>. <https://www.rfc-editor.org/info/rfc5731>.
[RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732,
August 2009, <https://www.rfc-editor.org/info/rfc5732>. August 2009, <https://www.rfc-editor.org/info/rfc5732>.
[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>.
[RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
Code: The Implementation Status Section", RFC 6982, Code: The Implementation Status Section", BCP 205,
DOI 10.17487/RFC6982, July 2013, RFC 7942, DOI 10.17487/RFC7942, July 2016,
<https://www.rfc-editor.org/info/rfc6982>. <https://www.rfc-editor.org/info/rfc7942>.
[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>.
[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,
skipping to change at page 21, line 43 skipping to change at page 21, line 39
Biron, P. and A. Malhotra, ""XML Schema Part 2: Datatypes Biron, P. and A. Malhotra, ""XML Schema Part 2: Datatypes
Second Edition", World Wide Web Consortium Recommendation Second Edition", World Wide Web Consortium Recommendation
REC-xmlschema-2-20041028", October 2004, REC-xmlschema-2-20041028", October 2004,
<http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>. <http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>.
11.2. Informative References 11.2. Informative References
[ID.draft-ietf-regext-org] [ID.draft-ietf-regext-org]
Zhou, L., Kong, N., Zhou, G., Lee, X., and J. Gould, Zhou, L., Kong, N., Zhou, G., Lee, X., and J. Gould,
"Extensible Provisioning Protocol (EPP) Reseller Mapping", "Extensible Provisioning Protocol (EPP) Reseller Mapping",
Feb 2018, Apr 2018,
<http://tools.ietf.org/html/draft-ietf-regext-org>. <http://tools.ietf.org/html/draft-ietf-regext-org>.
[ID.draft-ietf-regext-reseller-ext]
Zhou, L., Kong, N., Wei, J., Lee, X., and J. Gould,
"Extensible Provisioning Protocol (EPP) Reseller Mapping",
Dec 2016, <http://tools.ietf.org/html/
draft-ietf-regext-reseller-ext>.
[RFC7451] Hollenbeck, S., "Extension Registry for the Extensible
Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451,
February 2015, <https://www.rfc-editor.org/info/rfc7451>.
Appendix A. Change Log Appendix A. Change Log
Initial -00: Individual document submitted. Initial -00: Individual document submitted.
-01: -01:
* Updated abstract and introduction. * Updated abstract and introduction.
* Revised typos in info response. * Revised typos in info response.
skipping to change at page 23, line 13 skipping to change at page 23, line 21
mailing list. Modified the examples in the document. mailing list. Modified the examples in the document.
Organization WG document-03: Organization WG document-03:
* Updated typos. * Updated typos.
* Changed some descriptions about <orgext:id> and role attribute. * Changed some descriptions about <orgext:id> and role attribute.
* Modified the example of "domain with no organization". * Modified the example of "domain with no organization".
* Updated section 8, adding implementation status of VeriSign. * Updated section 8, adding implementation status of Verisign.
Organization WG document-04:
* Updated typos.
* Removed the example of <update> command, domain with no
organization.
* Updated references.
* Updated section 8 of implementation status.
Authors' Addresses Authors' Addresses
Linlin Zhou Linlin Zhou
CNNIC CNNIC
4 South 4th Street, Zhongguancun, Haidian District 4 South 4th Street, Zhongguancun, Haidian District
Beijing, Beijing 100190 Beijing, Beijing 100190
China China
Phone: +86 10 5881 2677 Phone: +86 10 5881 2677
skipping to change at page 24, line 14 skipping to change at page 24, line 32
Xiaodong Lee 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
Phone: +86 10 5881 3020 Phone: +86 10 5881 3020
Email: xl@cnnic.cn Email: xl@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. 33 change blocks. 
61 lines changed or deleted 85 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/