Internet-Draft Tomek Zygmuntowicz
Expires: November 2003 Patrycja Wegrzynowicz
Kuba Laszkiewicz
Juliusz Brzostek
Witold Zarowski
NASK
May 2003
EPP parameters for .pl ccTLD
draft-zygmuntowicz-epp-pltld-00.txt
Status of this Memo
This document is an Internet-Draft and is in full conformance
with all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as
"work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Abstract
This document is a proposed description of the cooperation protocol
between NASK and its Partners. The proposal can be replaced with the
new document or can be invalidated.
The content of this proposal relates to the documents:
<draft-ietf-provreg-epp-08.txt>, <draft-ietf-provreg-epp-host-
06.txt>, <draft-ietf-provreg-epp-domain-06.txt>, <draft-ietf-
provreg-epp-contact-06.txt>, RFC 3375 published by Internet
Engineering Task Force.
NASK [Page 1]
Internet-Draft EPP parameters for .pl ccTLD May 2003
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 1
2. EPP modifications . . . . . . . . . . . . . . . . . . . . . . 1
3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Formal syntax . . . . . . . . . . . . . . . . . . . . . . . . 14
5. Security considerations . . . . . . . . . . . . . . . . . . . 16
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
7. Authors' addresses . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction
The Extensible Provisioning Protocol (EPP, [2]) describes an
application layer client-server protocol for the provisioning and
management of objects stored in a shared central repository.
Specified in XML, EPP defines generic object management operations
and an extensible framework that maps protocol operations to
objects.
The intent of this document is to specify the protocol elements in
EPP extensions in order to accomodate additional information
required for a registrar to interconnect with the .pl ccTLD registry
via an EPP-compatible interface.
2. EPP modifications
2.1. The individual element
The individual element has been added to commands:
<contact:create>, <contact:update> and <contact:info>. It
specifies whether the contact represents a private person.
2.2. The consentForPublishing element
The consentForPublishing element has been added to commands:
<contact:create>, <contact:update> and <contact:info>. It
specifies for a contact representing a private person whether
this person has given its assent for publishing personal details
in WHOIS database. The consentForPublishing element has no
meaning for a contact which does not represent a private person.
2.3. The reason element
The reason element has been added to <domain:create> command. It
includes a justification of registrant's rights to a domain.
NASK [Page 2]
Internet-Draft EPP parameters for .pl ccTLD May 2003
2.4. The book element
The book element has been added to the <domain:create> command.
Successfully processed <domain:create> command with provided
book element causes a reservation of a domain in the system.
Successfully processed <domain:create> command with not provided
book element causes a registration of a domain in the system.
The only operation which can be performed on the reserved domain
is registration by the client which had reserved the domain. If
the client which reserved a domain does not register the domain
before expiration of reservation period (the reservation period
is determined by parameters of the system) then a possibility
of a reservation and a registration of the domain is blocked for
a random period (this period is determined by parameters of the
system). The domain will be available for a reservation and a
registration after expiration of blockade period. Note that a
reservation of a domain prior to a reservation of this domain is
not obligatory.
The following rules of providing domain's data for
<domain:create> command are an necessary condition of a
successful domain registration:
- registrant's ID contained in <domain:registrant> element and
the domain name rights justification contained in
<domain:reason> element must be provided only once: either
during a domain reservation or registration.
- a domain validity period contained in <domain:period> element
must be provided only once: either during a domain
reservation or registration. When the domain validity period
is not provided, the system sets a default value which is
determined by system's parameters.
- domain authorization data contained in <domain:authInfo>
element must be provided during a domain reservation and
registration. Both values must be identical.
- name servers contained in <domain:ns> elements can be provided
only once, with the first <domain:create> command. The number
of provided name servers must meet the rules specified by
parameters of the system.
- identifiers of contacts associated with a domain contained in
<domain:contact> elements can be given only once: either
during a domain reservation or registration. Given list of
contacts must meet the rules specified by parameters of the
system. Providing no <domain:contact> elements neither during
a registration nor reservation is possible only when the
parameters of the system allow for the zero number of
contacts to be associated with a domain.
NASK [Page 3]
Internet-Draft EPP parameters for .pl ccTLD May 2003
2.5. A transfer of a domain or a contact does not require a
confirmation of sponsoring client of that object. A result of a
transfer command is returned directly in response to
<domain:transfer> or <contact:transfer> command with option
op=request (status serverApproved is set in case of successful
processing of transfer command). Options of the <domain:transfer>
and <contact:transfer> commands other than request are not
supported.
2.6. It is possible to delete a host using the <host:delete>
command, even if there are domains delegated to that host, on the
condition that the host is not configured for any domain which is
delegated to this host. A side effect of a removal of a host is
removal of all delegations to that host.
2.7. Using the <host:create> command it is possible to create a host
which belongs to a zone maintained by Registry (NASK) and for
which no superordinate domain exists. Such created host has the
pendingCreate status. It will be removed from the system if the
superordinate domain is not reserved or registered before
expiration of a period determined by the system parameters.
2.8. A change of a host's name is forbidden. A providing of the
<host:chg> element in the <host:update> element causes failure of
the <host:update> command.
2.9. The <host:info> command returns full set of information only
for sponsoring client, for other clients operation fails.
2.10. The <domain:info> command returns full set of information only
for sponsoring client of a domain and client which provided a
correct authorization information in the <domain:authInfo>
element. In other cases command fails.
2.11. The <contact:info> command returns full set of information
only to sponsoring client of a domain and to client who provided
a correct authorization information of domain in the
<contact:authInfo> element. Furthermore, if contact represents a
private person (individual=1) who consents to publish his/her
personal details (consentForPublishing=1) then information is
returned to the others clients. In other cases command fails.
NASK [Page 4]
Internet-Draft EPP parameters for .pl ccTLD May 2003
3. Examples
Example 1: Processing of the <domain:create> command with provided book
element
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
epp-1.0.xsd">
<command>
<create>
<domain:create
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
domain-1.0.xsd">
<domain:name>przyklad44.pl</domain:name>
<domain:ns>ns.przyklad2.pl</domain:ns>
<domain:ns>ns5.przyklad.pl</domain:ns>
<domain:authInfo>
<domain:pw>authinfo_of_d97</domain:pw>
</domain:authInfo>
</domain:create>
</create>
<extension>
<extdom:create xmlns:extdom="urn:nask:params:xml:ns:extdom-1.0"
xsi:schemaLocation="urn:nask:params:xml:ns:extdom-1.0
extdom-1.0.xsd">
<extdom:reason>nice name</extdom:reason>
<extdom:book/>
</extdom:create>
</extension>
<clTRID>ABC-12345</clTRID>
</command>
</epp>
Example 2: System answer to the <domain:create> command with provided
book element
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
epp-1.0.xsd">
<response>
<result code="1000">
<msg>Command completed successfully</msg>
</result>
NASK [Page 5]
Internet-Draft EPP parameters for .pl ccTLD May 2003
<resData>
<domain:creData
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
domain-1.0.xsd">
<domain:name>przyklad44.pl</domain:name>
<domain:crDate>1999-04-03T22:00:00.0Z</domain:crDate>
<domain:exDate>1999-18-03T22:00:00.0Z</domain:exDate>
</domain:creData>
</resData>
<trID>
<clTRID>ABC-12345</clTRID>
<svTRID>54321-XYZ</svTRID>
</trID>
</response>
</epp>
Example 3: Processing of the <host:create> command
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
epp-1.0.xsd">
<command>
<create>
<host:create
xmlns:host="urn:ietf:params:xml:ns:host-1.0"
xsi:schemaLocation="urn:ietf:params:xml:ns:host-1.0
host-1.0.xsd">
<host:name>ns1.example.tld</host:name>
<host:addr ip="v4">192.1.2.3</host:addr>
<host:addr ip="v4">198.1.2.3</host:addr>
<host:addr ip="v6">1080:0:0:0:8:800:200417A</host:addr>
</host:create>
</create>
<clTRID>ABC-12345</clTRID>
</command>
</epp>
Example 4: System answer to the <host:create> command
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
epp-1.0.xsd">
<response>
NASK [Page 6]
Internet-Draft EPP parameters for .pl ccTLD May 2003
<result code="1000">
<msg>Command completed successfully</msg>
</result>
<resData>
<host:creData
xmlns:host="urn:ietf:params:xml:ns:host-1.0"
xsi:schemaLocation="urn:ietf:params:xml:ns:host-1.0
host-1.0.xsd">
<host:name>ns1.example.tld</host:name>
<host:crDate>1999-04-03T22:00:00.0Z</host:crDate>
</host:creData>
</resData>
<trID>
<clTRID>ABC-12345</clTRID>
<svTRID>54322-XYZ</svTRID>
</trID> </response>
</epp>
Example 5: Processing of the <host:info> command
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
epp-1.0.xsd">
<command>
<info>
<host:info
xmlns:host="urn:ietf:params:xml:ns:host-1.0"
xsi:schemaLocation="urn:ietf:params:xml:ns:host-1.0
host-1.0.xsd">
<host:name>ns1.example.tld</host:name>
</host:info>
</info>
<clTRID>ABC-12345</clTRID>
</command>
</epp>
Example 6: System answer to the <host:info> command
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
epp-1.0.xsd">
<response>
<result code="1000">
<msg>Command completed successfully</msg>
NASK [Page 7]
Internet-Draft EPP parameters for .pl ccTLD May 2003
</result>
<resData>
<host:infData
xmlns:host="urn:ietf:params:xml:ns:host-1.0"
xsi:schemaLocation="urn:ietf:params:xml:ns:host-1.0
host-1.0.xsd">
<host:name>ns1.example.tld</host:name>
<host:roid>NS1_EXAMPLE1-REP</host:roid>
<host:status s="linked"/>
<host:status s="clientUpdateProhibited"/>
<host:addr ip="v4">192.1.2.3</host:addr>
<host:addr ip="v4">198.1.2.3</host:addr>
<host:addr ip="v6">1080:0:0:0:8:800:200417A</host:addr>
<host:clID>ClientY</host:clID>
<host:crID>ClientX</host:crID>
<host:crDate>1999-04-03T22:00:00.0Z</host:crDate>
<host:upID>ClientX</host:upID>
<host:upDate>1999-12-03T09:00:00.0Z</host:upDate>
<host:trDate>2000-04-08T09:00:00.0Z</host:trDate>
</host:infData>
</resData>
<trID>
<clTRID>ABC-12345</clTRID>
<svTRID>54322-XYZ</svTRID>
</trID>
</response>
</epp>
Example 7: Processing of the <host:update> command
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
epp-1.0.xsd">
<command>
<update>
<host:update
xmlns:host="urn:ietf:params:xml:ns:host-1.0"
xsi:schemaLocation="urn:ietf:params:xml:ns:host-1.0
host-1.0.xsd">
<host:name>ns1.example.tld</host:name>
<host:add>
<host:addr ip="v4">192.3.2.1</host:addr>
<host:status s="clientUpdateProhibited"/>
</host:add>
<host:rem>
<host:addr ip="v6">1080:0:0:0:8:800:200417A</host:addr>
NASK [Page 8]
Internet-Draft EPP parameters for .pl ccTLD May 2003
</host:rem>
<host:chg>
<host:name>ns2.example.tld</host:name>
</host:chg>
</host:update>
</update>
<clTRID>ABC-12345</clTRID>
</command>
</epp>
Example 8: System answer to the <host:update> command
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
epp-1.0.xsd">
<response>
<result code="1000">
<msg>Command completed successfully</msg>
</result>
<trID>
<clTRID>ABC-12345</clTRID>
<svTRID>54321-XYZ</svTRID>
</trID>
</response>
</epp>
Example 9: Processing of the <contact:create> command
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
epp-1.0.xsd">
<command>
<create>
<contact:create
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xsi:schemaLocation="urn:ietf:params:xml:ns:contact-1.0
contact-1.0.xsd">
<contact:id>sh8013</contact:id>
<contact:postalInfo type="int">
<contact:name>11John Doe</contact:name>
<contact:org>Example Inc.</contact:org>
<contact:addr>
<contact:street>123 Example Dr.</contact:street>
<contact:street>Suite 100</contact:street>
<contact:city>Dulles</contact:city>
NASK [Page 9]
Internet-Draft EPP parameters for .pl ccTLD May 2003
<contact:sp>VA</contact:sp>
<contact:pc>20166-6503</contact:pc>
<contact:cc>US</contact:cc>
</contact:addr>
</contact:postalInfo>
<contact:voice x="1234">+1.7035555555</contact:voice>
<contact:fax>+1.7035555556</contact:fax>
<contact:email>jdoe@example.tld</contact:email>
<contact:authInfo>
<contact:pw>2fooBAR</contact:pw>
</contact:authInfo>
</contact:create>
</create>
<extension>
<extcon:create xmlns:extcon="urn:nask:params:xml:ns:extcon-1.0"
xsi:schemaLocation="urn:nask:params:xml:ns:extcon-1.0
extcon-1.0.xsd">
<extcon:individual>1</extcon:individual>
<extcon:consentForPublishing>1</extcon:consentForPublishing>
</extcon:create>
</extension>
<clTRID>ABC-12345</clTRID>
</command>
</epp>
Example 10: System answer to the <contact:create> command
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
epp-1.0.xsd">
<response>
<result code="1000">
<msg>Command completed successfully</msg>
</result>
<resData>
<contact:creData
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xsi:schemaLocation="urn:ietf:params:xml:ns:contact-1.0
contact-1.0.xsd">
<contact:id>sh8013</contact:id>
<contact:crDate>1999-04-03T22:00:00.0Z</contact:crDate>
</contact:creData>
</resData>
<trID>
<clTRID>ABC-12345</clTRID>
NASK [Page 10]
Internet-Draft EPP parameters for .pl ccTLD May 2003
<svTRID>54321-XYZ</svTRID>
</trID>
</response>
</epp>
Example 11: Processing of the <contact:info> command
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
epp-1.0.xsd">
<command>
<info>
<contact:info
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xsi:schemaLocation="urn:ietf:params:xml:ns:contact-1.0
contact-1.0.xsd">
<contact:id>666666</contact:id>
</contact:info>
</info>
<extension>
<extcon:info
xmlns:extcon="urn:nask:params:xml:ns:extcon-1.0"
xsi:schemaLocation="urn:nask:params:xml:ns:extcon-1.0
extcon-1.0.xsd">
<extcon:authInfo>
<extcon:pw>2fooBAR</extcon:pw>
</extcon:authInfo>
</extcon:info>
</extension>
<clTRID>ABC-12345</clTRID>
</command>
</epp>
Example 12: System answer to the <contact:info> command
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
epp-1.0.xsd">
<response>
<result code="1000">
<msg>Command completed successfully</msg>
</result>
<resData>
NASK [Page 11]
Internet-Draft EPP parameters for .pl ccTLD May 2003
<contact:infData
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xsi:schemaLocation="urn:ietf:params:xml:ns:contact-1.0
contact-1.0.xsd">
<contact:id>sh8013</contact:id>
<contact:roid>SH8013-REP</contact:roid>
<contact:status s="linked"/>
<contact:status s="clientDeleteProhibited"/>
<contact:postalInfo type="int">
<contact:name>John Doe</contact:name>
<contact:org>Example Inc.</contact:org>
<contact:addr>
<contact:street>123 Example Dr.</contact:street>
<contact:street>Suite 100</contact:street>
<contact:city>Dulles</contact:city>
<contact:sp>VA</contact:sp>
<contact:pc>20166-6503</contact:pc>
<contact:cc>US</contact:cc>
</contact:addr>
</contact:postalInfo>
<contact:voice x="1234">+1.7035555555</contact:voice>
<contact:fax>+1.7035555556</contact:fax>
<contact:email>jdoe@example.tld</contact:email>
<contact:clID>ClientY</contact:clID>
<contact:crID>ClientX</contact:crID>
<contact:crDate>1999-04-03T22:00:00.0Z</contact:crDate>
<contact:upID>ClientX</contact:upID>
<contact:upDate>1999-12-03T09:00:00.0Z</contact:upDate>
<contact:trDate>2000-04-08T09:00:00.0Z</contact:trDate>
<contact:authInfo>
<contact:pw>2fooBAR</contact:pw>
</contact:authInfo>
</contact:infData>
</resData>
<trID>
<clTRID>ABC-12345</clTRID>
<svTRID>54322-XYZ</svTRID>
</trID>
</response></epp>
Example 13: Processing of the <contact:update> command
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
epp-1.0.xsd">
<command>
NASK [Page 12]
Internet-Draft EPP parameters for .pl ccTLD May 2003
<update>
<contact:update
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xsi:schemaLocation="urn:ietf:params:xml:ns:contact-1.0
contact-1.0.xsd">
<contact:id>sh8013</contact:id>
<contact:add>
<contact:status s="clientDeleteProhibited"/>
</contact:add>
<contact:chg>
<contact:postalInfo type="int">
<contact:org/>
<contact:addr>
<contact:street>124 Example Dr.</contact:street>
<contact:street>Suite 200</contact:street>
<contact:city>Dulles</contact:city>
<contact:sp>VA</contact:sp>
<contact:pc>20166-6503</contact:pc>
<contact:cc>US</contact:cc>
</contact:addr>
</contact:postalInfo>
<contact:voice>+1.7034444444</contact:voice>
<contact:fax/>
</contact:chg>
</contact:update>
</update>
<extension>
<extcon:update xmlns:extcon="urn:nask:params:xml:ns:extcon-1.0"
xsi:schemaLocation="urn:nask:params:xml:ns:extcon-1.0
extcon-1.0.xsd">
<extcon:consentForPublishing>1</extcon:consentForPublishing>
</extcon:update>
</extension>
<clTRID>ABC-12345</clTRID>
</command>
</epp>
Example 14: System answer to the <contact:update> command
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
epp-1.0.xsd">
<response>
<result code="1000">
<msg>Command completed successfully</msg>
</result>
NASK [Page 13]
Internet-Draft EPP parameters for .pl ccTLD May 2003
<trID>
<clTRID>ABC-12345</clTRID>
<svTRID>54321-XYZ</svTRID>
</trID>
</response>
</epp>
4. Formal syntax
Extdom-1.0.xsd:
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="http://www.dns.pl/NASK-EPP/extdom-1.0"
xmlns:extdom="http://www.dns.pl/NASK-EPP/extdom-1.0"
xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<!--
Import common element types.
-->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"
schemaLocation="eppcom-1.0.xsd"/>
<import namespace="urn:ietf:params:xml:ns:epp-1.0"
schemaLocation="epp-1.0.xsd"/>
<annotation>
<documentation>
NASK Extensible Provisioning Protocol v1.0
domain extension.
</documentation>
</annotation>
<element name="create" type="extdom:createType"/>
<element name="dlgData" type="extdom:dlgDataType"/>
<complexType name="createType">
<sequence>
<element name="reason" type="string" minOccurs="0"/>
<element name="book" minOccurs="0"/>
</sequence>
</complexType>
<complexType name="dlgDataType">
<sequence>
NASK [Page 14]
Internet-Draft EPP parameters for .pl ccTLD May 2003
<element name="name" type="eppcom:labelType"
maxOccurs="unbounded"/>
<element name="ns" type="eppcom:labelType"/>
</sequence>
</complexType>
<!--
End of schema.
-->
</schema>
Extcon-1.0.xsd:
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="http://www.dns.pl/NASK-EPP/extcon-1.0"
xmlns:extcon="http://www.dns.pl/NASK-EPP/extcon-1.0"
xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<!--
Import common element types.
-->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"
schemaLocation="eppcom-1.0.xsd"/>
<import namespace="urn:ietf:params:xml:ns:epp-1.0"
schemaLocation="epp-1.0.xsd"/>
<annotation> <documentation>
NASK Extensible Provisioning Protocol v1.0
contact extension.
</documentation>
</annotation>
<element name="create" type="extcon:allType"/>
<element name="update" type="extcon:updateType"/>
<element name="infData" type="extcon:allType"/>
<element name="info" type="extcon:infoType"/>
<complexType name="allType">
<sequence>
<element name="individual" type="boolean" minOccurs="0"/>
<element name="consentForPublishing" type="boolean"
minOccurs="0"/>
</sequence>
</complexType>
NASK [Page 15]
Internet-Draft EPP parameters for .pl ccTLD May 2003
<complexType name="updateType">
<sequence>
<element name="consentForPublishing" type="boolean"
minOccurs="0"/>
</sequence>
</complexType>
<complexType name="infoType">
<sequence>
<element name="authInfo" type="extcon:authInfoType"/>
</sequence>
</complexType>
<complexType name="authInfoType">
<choice>
<element name="pw" type="eppcom:pwAuthInfoType"/>
<element name="ext" type="eppcom:extAuthInfoType"/>
</choice>
</complexType>
<!--
End of schema.
-->
</schema>
5. Security Considerations
This document does not require any special security considerations
except those mentioned in documents [1], [2], [3], [4], [5], [6],
[7].
6. References
[1] S. Hollenbeck Generic Registry-Registrar Protocol Requirements,
September 2002, RFC 3375.
[2] S. Hollenbeck Extensible Provisioning Protocol, August 2002,
Internet-Draft.
[3] S. Hollenbeck Extensible Provisioning Protocol Contact Mapping,
August 2002, Internet-Draft.
[4] S. Hollenbeck Extensible Provisioning Protocol Domain Name
Mapping, August 2002, Internet-Draft.
[5] S. Hollenbeck Extensible Provisioning Protocol Host Mapping,
August 2002, Internet-Draft.
[6] S. Hollenbeck Extensible Provisioning Protocol Transport Over TCP,
August 2002, Internet-Draft.
[7] S. Hollenbeck Guidelines for Extending the Extensible Provisioning
Protocol, October 2002, Internet-Draft.
NASK [Page 16]
Internet-Draft EPP parameters for .pl ccTLD May 2003
10. Authors' Addresses
Patrycja Wegrzynowicz
NASK
ul. Wawozowa 18
02-796 Warszawa
Poland
Email: patrycjaw@nask.pl
Kuba Laszkiewicz
NASK
ul. Wawozowa 18
02-796 Warszawa
Poland
Email: jakubl@nask.pl
Juliusz Brzostek
NASK
ul. Wawozowa 18
02-796 Warszawa
Poland
Email: juliuszb@nask.pl
Tomek Zygmuntowicz
NASK
ul. Wawozowa 18
02-796 Warszawa
Poland
Email: tomekz@nask.pl
Witold Zarowski
NASK
ul. Wawozowa 18
02-796 Warszawa
Poland
Email: witzar@nask.pl