Re: Lists and EPP

I agree the agile client approach is wise.

Meanwhile, the registrars that are downstream from registries have to
make a lot of changes to accommodate delta between implementation A
and implementation B of EPP / Business Logic, etc.  Many of the
changes present themselves once the developers are in the OT&E wading
pool and notice the differences between systems, which planning can't
necessarily overcome.

These 'opportunities' to address the differences simply present
themselves with the need to address them, not unlike a jury summons or
a flaming paper bag on the doorstep after a ring of the doorbell.

Jothan



2011/6/8 Patrik Fältström <[email protected]>:
> On 9 jun 2011, at 05.14, [email protected] wrote:
>
>> Registrars which implemented agile clients had foresight.
>
> It is not that simple...
>
> A registrar have one user interface, regardless of whether it is a web page or API. That exposes a certain business logic to the registrants.
>
> The registry then translates the business logic regarding registration, renewal, transfer etc into the specific logic that the registry in question require.
>
> This implies both changes in the business logic and epp requirements.
>
> And in many cases it does not matter how agile clients you have...because the way renewal works for example, and requirements from the registry that certain things must be exposed to the registrant and what not.
>
>   Patrik
>
>
_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg