Version 7 by Thomas Gelf
on Jul 05, 2010 06:56.

compared with
Version 8 by Thomas Gelf
on Jul 05, 2010 07:01.

This line was removed.
This word was removed. This word was added.
This line was added.

Changes (23)

View Page History

{info:title=Origin, sponsorship}
Research and development for this component is being sponsored by my current employer, [Raiffeisen OnLine|]. Being a well-known ISP in South Tyrol (Northern Italy), we believe in the power of Open Source Software. We are intensively using the Zend Framework in various project and therefore thought that this library could be a nice addition to this powerful community project. The EPP project has been started as part of our internal PHP library and is right now being rearchitectured to fit ZF requirements.

* This library *will* try to strictly implement most (all?) of the following standards:
** [RFC 5730|] (4930, 3730): Extensible Provisioning Protocol (EPP)
** [RFC 5731|] (4931, 3731): EPP Domain Name Mapping
** [RFC 5732|] (4932, 3732): EPP Host Mapping
** [RFC 5733|] (4933, 3733): EPP Contact Mapping
** RFC 3915: [RFC 3915|]: Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)
** RFC 3735: [RFC 3735|]: Guidelines for Extending the Extensible Provisioning Protocol (EPP)
* This library *will* also support registry-specific extensions:
** Some registries have proprietary EPP extensions
** Once the base library is complete it should be attractive enough to get contributions for most/all known extensions please see [report-rfc4930-4934|] for an older overview)
* To make sure that extensibility as of RFC 3735 is given, a few extensions *will* be implemented together with the first version of Zend_Epp:
** is extending contact and domain objects
** EURid did a lot of tricky extensions and also added new commands (sunrise period) - an attempt to implement them would make sure that the library is really as extensible as required by RFC 3735
* DNSSEC as of [RFC 5910|] (4310) *would* also be an interesting extension
* If there is any interest in ENUM-related extensions: I'd love to get some input, especially from people having test accounts (e.g.
** RFC 4414: [RFC 4414|]: E.164 Number Mapping for the Extensible Provisioning Protocol (EPP)
** [RFC 5076|] (3761): ENUM Validation Information Mapping for the Extensible Provisioning Protocol
* This library will be able to support different transports and provide the most used ones (TCP, HTTP) with it's first version
** [RFC 5734|] (4934, 3734): Extensible Provisioning Protocol (EPP) Transport over TCP
* The first version *will* allow to run an EPP client (registrar)
* A following version *will* also allow to run an EPP server (registry)
* Therefore class structure will already
* Therefore class structure *will* already be done in a way to allow this library to be used in a server implementation
* This library *will not* provide any backend functions for persistent data storage
* It *will not* automagically handle all EPP-related jobs as it is nothing but a plain stupid EPP library
* This library *will* however provide some "shortcuts" for routine jobs such as message queue handling
* This library *will* take care of completely transparent EPP session handling