EPP protocol

EPP syntax

Technical documentation can be read here. Documentation related to registrar interface will be added later.

Resources of technical interest:

• Schema: eppcom-1.0 (RFC 3730)
• Schema: epp-1.0 (RFC 3730)
• Schema: domain-1.0 (RFC 3731)
• Schema: contact-1.0 (RFC 3733)
• Schema: host-1.0 (RFC 3732)
• Schema: dnssec-1.1 (RFC 5910)
• Schema: dnslu-1.0 (DNS-LU EPP extension)
• EPP over TCP: (RFC 3732)

Transport protocols

The EPP Server supports two transport protocols.

• `DNS-LU EPP over TCP` documented below.
• `RFC3734 EPP over TCP` below, is standard-compliant implementation of RFC3734 with 4-byte header preceding each EPP message. There is no specific encoding restriction, the header is part of the message size.
  Note: There was a compatibility bug in this implementation where the header size was NOT included in the size information.

DNS-LU transport protocol

The `DNS-LU EPP over TCP` is raw EPP over TCP where the TCP stream carries UTF-8 encoded EPP XML messages, without any header. The trailing </epp> is seen as end of EPP message.

Whitespace is allowed before/after an EPP message and may be used as keep-alive for the session.