.NU Domain is among the first Country-Code Top-Level Domains (ccTLDs)
to offer its registrars the new standard Extensible Provisioning
Protocol (EPP). The implementation of this standard provides registrars
the ability to use a single interface for all TLD registries and
streamlines integration processes, thus reducing registrars’ costs. The
Internet organization ICANN, which oversees the Internet’s domain name
system, now requires all generic top domains, such as .com, .net, .org,
to adapt to EPP.
“EPP is a very important standard for the management of domain names as
it eliminates manual routines. We believe we can cut our costs for
domain names by 10 to 20 percent, which will also benefit .NU Domain
customers,” said Sam Nurmi, CEO of Sweden’s third largest web hotel,
Loopia, which has successfully tested .NU Domain’s new EPP interface.
“Once again .NU Domain is leading the way with a technical solution
that is years ahead of Nic-Se.”
Previously, there were no recognized standards for the systems that web
page resellers and registrars use for their interaction with top level
domain systems. The standards body, Internet Engineering Task Force
(IETF), finalized a new protocol, Extensible Provisioning Protocol
(EPP) for top domains in March 2004. ICANN now requires all generic
(non-geographic or country code) top level domains to adopt EPP.
Generic top level domains .org, .info and .biz already have the
protocol in use, while .com and .net have started to adapt.
“Although ICANN has not stipulated that the ccTLDS must adapt to EPP,
the expected financial savings will drive the registrar’s demand for
EPP adoption by all popular ccTLDs,” said, William, J. Semich,
president of .NU Domain. “The ccTLD registries of Poland .PL and the
Netherlands .NL are in the process of implementing EPP.”
EPP is defined on the IETF home page: www.ietf.org/rfc/rfc3731.txt?number=3731
ICANN’s requirements for generic top-domains can be found on: www.icann.org/registries/agreements.htm
For more information, please contact Support at email@example.com