Re: [provreg] New Version Notification for draft-brown-epp-fees-01.txt

I think this could be modeled by having extensible custom types on each "
*fee"* element, or maybe on each "*cd"* element. I would be hesitant to
embed too much application logic into the protocol, and instead just make
the schema flexible enough to model different scenarios.

On Thu, May 1, 2014 at 3:05 PM, Luis Muñoz <lem@isc.org> wrote:

>
> On May 1, 2014, at 11:52 AM, MICHAEL W YOUNG <michael@mwyoung.ca> wrote:
>
> > It would be interesting to query a given domain for an answer on which
> programs its applicable for.  Lets say I am a registrar that signed up for
> marketing programs (out of registry band) "A1" and program "B2" with the
> registry operator, instead of keeping track of that in my registrar
> systems, whenever I go to check pricing on a domain, I would also receive
> any current programs that are applicable to that domain along with the base
> pricing I originally queried.  I can then do subsequent lookups on the
> program pricing if I don't have the program pricing handy, or if the
> program pricing varies depending on the specific string.
>
> Why not return the pricing associated to each program in the same
> transaction? That would save on queries and I think it's a fair assumption
> that server-side looking up the list of programs will also provide the
> relevant pricing information with the same effort.
>
> Best regards
>
> -lem
>
> _______________________________________________
> provreg mailing list
> provreg@ietf.org
> https://www.ietf.org/mailman/listinfo/provreg
>