Jump to content

Extensible Provisioning Protocol: Difference between revisions

From ICANNWiki
← Older edit
VisualWikitext
Marie Cabural (talk | contribs)
9,082 edits
No edit summary
Christiane (talk | contribs)
Bureaucrats, steward, Administrators, translator
3,247 edits
m Christiane moved page EPP to Extensible Provisioning Protocol over redirect: Standardize
 
(15 intermediate revisions by 5 users not shown)
Line 1: Line 1:
[[Image:UnderConstruction.png]]
'''Extensible Provisioning Protocol (EPP)''' is an [[XML]] based protocol used by the Internet industry, particularly the [[registrar]]s and [[Registry|registries]] in managing domain names (register, renew, modify, delete, transfer) and other elements in a [[SRS|Shared Registry System]] environment. It is the standard protocol used by a majority of [[gTLD]]s and [[ccTLD]]s.<ref>[http://www.uknof.org.uk/uknof5/Brown-EPP/ What is EPP?]</ref> As described by [[RFC]] 3730, EPP can be used in a multiple layered protocol and operating environments with different transport and security requirements. MIME media type application/epp+xml identifies the content of EPP.<ref>[http://tools.ietf.org/html/rfc3730  Extensible Provisioning Protocol (EPP). The motivation for the creation of EPP was to create a robust and flexible protocol that could provide communication between domain name registries and domain name registrars]</ref> The motivation for the creation of EPP was to create a robust and flexible '''protocol''' that could provide communication between domain name registries and domain name registrars
 
 
 
'''Extensible Provisioning Protocol (EPP)''' is an XML based protocol used by the internet industry particularly the registrars and registries in managing domain names (register, renew, modify, delete, transfer) and other elements in a [[SRS|Shared Registry System]] environment. It is the standard protocol used by majority of [[gTLD]]s.<ref>[http://www.uknof.org.uk/uknof5/Brown-EPP/ What is EPP?]</ref> EPP can be used in a multiple layered protocol and operating environments with different transport and security requirements. MIME media type application/epp+xml identifies the content of EPP.<ref>[http://tools.ietf.org/html/rfc3730  Extensible Provisioning Protocol (EPP)]</ref>


==Service Elements Provided by EPP==
==Service Elements Provided by EPP==
Based on RFC 3730, EPP provides basic service elements which include:
EPP provides basic service elements, which include:
* service discovery
* Service discovery
* commands
* Commands
* responses
* Responses
* extension framework supporting the definition of managed objects and the relationship of protocol requests and responses to those objects
* Extension framework supporting the definition of managed objects and the relationship of protocol requests and responses to those objects


==EPP Command Categories==
==EPP Command Categories==
A command is initiated by clients. A certain command is processed by a server so that the client who initiated it will receive a response. The three types of EPP commands include:
A command is initiated by clients. A certain command is processed by a server so that the client who initiated it will receive a response. EPP commands include:
# session management commands- establish and end persistent sessions with an EPP server
# '''Session Management Commands'''- establish and end persistent sessions with an EPP server
# query commands-perform read-only object information retrieval operations
# '''Query Commands'''- perform read-only object information retrieval operations
# data transform commands-perform read-write object management operations
# '''Data Transform Commands'''- perform read-write object management operations


==EPP Implementation==
==EPP Implementation==
[[DotRegistrar]] and [[Key Systems]], [[Afilias]], [[NeuStar]], and [[VeriSign]] tested and implemented EPP on their servers. Other registries also adopted the protocol including:<ref>[http://www.ietf.org/iesg/implementation/report-rfc4930-4934.txt Implementation Report for RFCs 4930-4934]</ref>
[[DotRegistrar]] and [[Key-Systems]], [[Afilias]], [[NeuStar]], and [[VeriSign]] tested and implemented EPP on their servers. Other registries also adopted the protocol including:<ref>[http://www.ietf.org/iesg/implementation/report-rfc4930-4934.txt Implementation Report for RFCs 4930-4934]</ref>
[[.aero]], [[.fr]], [[.ag]], [[.si]], [[.asia]], [[.at]], [[.au]], [[.be]], [[.biz]], [[.br]], [[.bz]], [[.cat]], [[.la]], [[.cx]], [[.gs]], [[.tl]], [[.ki]], [[.ms]], [[.mu]], [[.nf]], [[.ht]], [[.na]], [[.coop]], [[.cz]], [[.eu]], [[.hn]], [[.co.cz]], [[.info]], [[.it]], [[.lc]], [[.lu]], [[.me]], [[.mn]], [[.mobi]], [[.name]], [[.uk]], [[.no]], [[.nl]], [[.nu]], [[.org]], [[.pl]] (over HTTPS), [[.pro]], [[.pt]], [[.sc]], [[.se]], [[.ch]], [[.li]], [[.travel]], [[.us]], [[.vc]], [[.com]], .[[net]], [[.cc]], [[.tv]], [[.jobs]], [[.es]] (over HTTPS), [[.cn]], [[.tw]], [[.im]], [[.cl]], [[.ac]], [[.sh]], [[.io]], [[.tm]], [[.in]], i.3.4.e164.arpa (infrastructure ENUM)
* [[.aero]], [[.asia]], [[.biz]], [[.cat]], [[.com]], [[.coop]], [[.info]], [[.jobs]], [[.mobi]], [[.name]], [[.net]], [[.org]], [[.pro]], [[.travel]]
in Austria)
 
* [[.au]], [[.eu]], [[.us]], [[.fr]], [[.ag]], [[.si]], [[.at]],   [[.be]], [[.br]],   [[.bz]],   [[.la]], [[.cx]], [[.gs]], [[.tl]], [[.ki]], [[.ms]], [[.mu]], [[.nf]], [[.ht]], [[.na]],   [[.cz]],   [[.hn]], [[.co.cz]], [[.it]], [[.lc]], [[.lu]], [[.me]], [[.mn]],   [[.uk]], [[.no]], [[.nl]], [[.nu]], [[.pt]], [[.sc]], [[.se]], [[.ch]], [[.li]], [[.vc]], [[.cc]], [[.tv]],   [[.cn]], [[.tw]], [[.im]], [[.cl]], [[.ac]], [[.sh]], [[.io]], [[.tm]], [[.in]], [[.es]] (over HTTPS), [[.pl]] (over HTTPS), [[.tc]], [[.gd]], [[.vg]]


==Related RFCs==
* i.3.4.e164.arpa (infrastructure [[ENUM]]) in Austria)
 
==Related [[RFC]]s==
* RFC 3375- Extensible Provisioning Protocol (EPP) meets and exceeds the requirements for a generic registry-registrar protocol
* RFC 3735- Guidelines for Extending the Extensible Provisioning Protocol  
* RFC 3735- Guidelines for Extending the Extensible Provisioning Protocol  
* RFC 3915- Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol  
* RFC 3915- Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol  
Line 33: Line 33:
* RFC 5733- Extensible Provisioning Protocol (EPP) Contact Mapping
* RFC 5733- Extensible Provisioning Protocol (EPP) Contact Mapping
* RFC 5734- Extensible Provisioning Protocol (EPP) Transport over TCP
* RFC 5734- Extensible Provisioning Protocol (EPP) Transport over TCP
 
==References==
==References==
{{reflist}}  
{{reflist}}  
Line 39: Line 39:
[[Category: Glossary]]
[[Category: Glossary]]


__NOTOC__
__FORCETOC__

Latest revision as of 22:01, 9 May 2024

Extensible Provisioning Protocol (EPP) is an XML based protocol used by the Internet industry, particularly the registrars and registries in managing domain names (register, renew, modify, delete, transfer) and other elements in a Shared Registry System environment. It is the standard protocol used by a majority of gTLDs and ccTLDs.[1] As described by RFC 3730, EPP can be used in a multiple layered protocol and operating environments with different transport and security requirements. MIME media type application/epp+xml identifies the content of EPP.[2] The motivation for the creation of EPP was to create a robust and flexible protocol that could provide communication between domain name registries and domain name registrars

Service Elements Provided by EPP[edit | edit source]

EPP provides basic service elements, which include:

  • Service discovery
  • Commands
  • Responses
  • Extension framework supporting the definition of managed objects and the relationship of protocol requests and responses to those objects

EPP Command Categories[edit | edit source]

A command is initiated by clients. A certain command is processed by a server so that the client who initiated it will receive a response. EPP commands include:

  1. Session Management Commands- establish and end persistent sessions with an EPP server
  2. Query Commands- perform read-only object information retrieval operations
  3. Data Transform Commands- perform read-write object management operations

EPP Implementation[edit | edit source]

DotRegistrar and Key-Systems, Afilias, NeuStar, and VeriSign tested and implemented EPP on their servers. Other registries also adopted the protocol including:[3]

  • i.3.4.e164.arpa (infrastructure ENUM) in Austria)

Related RFCs[edit | edit source]

  • RFC 3375- Extensible Provisioning Protocol (EPP) meets and exceeds the requirements for a generic registry-registrar protocol
  • RFC 3735- Guidelines for Extending the Extensible Provisioning Protocol
  • RFC 3915- Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol
  • RFC 4114- E.164 Number Mapping for the Extensible Provisioning Protocol
  • RFC 4310- Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol
  • RFC 5730- Extensible Provisioning Protocol
  • RFC 5731- Extensible Provisioning Protocol (EPP) Domain Name Mapping
  • RFC 5732- Extensible Provisioning Protocol (EPP) Host Mapping
  • RFC 5733- Extensible Provisioning Protocol (EPP) Contact Mapping
  • RFC 5734- Extensible Provisioning Protocol (EPP) Transport over TCP

References[edit | edit source]


Retrieved from "https://icannwiki.org/index.php?title=Extensible_Provisioning_Protocol&oldid=1350741"