Thomas, > What I don't like is that the "avail" attribute has been moved to the framing > <fee:cd> element, while it's an attribute of <fee:command> in the current > fee-0.15 draft. The latter has the big advantage of the server being able to > report e.g. the availability of a fee (and the domain in general) for > different > launch phases.
i think you have mentioned an important argument *against* your own proposal. You write "availability of a fee (and the domain in general)", which means that your proposal tries to mix in two different semantics into the same element - which, in turn, seems ambigious and probably even dangerous. The "avail" attribute can *either* indicate whether fee information is available, *or* whether a certain commmand on a certain domain in a certain phase (at the current point in time?) is "available". I think it's easy to see that the second "type" of availability would entail all kinds of problems. Therefore i'd rather not go down that path. It would pack too much logic into the command (eg. "is a transfer on that domain available for that client during the given phase at the current time?" - i don't want to be in the position to decide about such cases..) James, what is your most recent proposal for the descriptive text of the "avail" attribute at the "fee:cd" level? best, Alex _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
