On 4 Mar 2005, at 13:07, Edward Lewis wrote:
Is there a registry willing to add to it's database a schema for "these are future edits to make to the registration?" Would the schema be capped at the expiration of the object? Would the schema's contents be altered automatically upon a renewal, an automatic renewal? How would a registrant (or registrar) get access to this future information? A special IRIS interface?
As I read this, it seems you think this is a big deal. I'm not sure that it is.
Why do you draw such a conclusion? It's just a list of questions pertaining to one aspect holding future keys.
Conceptually, this is akin to what my bank already lets me do with "Internet banking" by posting future transactions (for example, a fund transfer close to the due date, rather than immediately the statement arrives). They put the request in a queue, provide me with an interface to display (but not change) it, and take action when the due date arrives.
How they cope if I close my account, or merge it with another before the due date, I have no idea. 8-)
If the banks can do it, I sure a clueful registrar could manage ...
There is a large difference between a registry and a bank.
Some would argue that if a registry would try to perform services like this, it would be a manifestation of "feature creep" resulting in a cost borne by the customers of the registry and a possible albatross (an asset which comes back to haunt you later).
I'm not sure that, even awash in cash (resources) and looking to creep features, storing keys for future benefit would be a worthy feature to add. Do you want to build operational dependencies between the DNS operator and registry any finer than we have now? Than is *needed* for DNSSEC?
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis +1-571-434-5468
NeuStar
Achieving total enlightenment has taught me that ignorance is bliss. . dnsop resources:_____________________________________________________ web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
