Klaus Malorny <Klaus.Malorny@knipp.de>, EPP Provreg <email@example.com>
James Gould <firstname.lastname@example.org>
Fri, 20 Nov 2009 13:00:17 -0500
[ietf-provreg] Anyone working on 4310-bis?
Re: [ietf-provreg] Anyone working on 4310-bis?
Title: Re: [ietf-provreg] Anyone working on 4310-bis?
Interesting idea, but I believe that the client implementing a preset timer is the simplest approach for both Registrar and Registry. The registry could publish the global TTL set or allow for the TTL to be set independently for each domain and publish the DNS latency SLA out-of-band. Setting the TTL for a domain would be a good idea for a different EPP extension. Creating a poll message for each update would be difficult for the client to match up, since the poll messages are usually consumed asynchronously using a single threaded session. Creating a poll message would also be a challenge for the Registry since metrics would have to be consolidated on a per domain basis across the DNS constellation. I would go with the KISS approach on this one by using a preset timer on the client side with reasonable and conservative estimates and optionally allow the client to explicitly set the TTL for a domain in a separate EPP extension.
James F. Gould
Principal Software Engineer
VeriSign Naming Services
21345 Ridgetop Circle
Dulles, VA 20166
Notice to Recipient: This e-mail contains confidential, proprietary and/or Registry Sensitive information intended solely for the recipient and, thus may not be retransmitted, reproduced or disclosed without the prior written consent of VeriSign Naming and Directory Services. If you have received this e-mail message in error, please notify the sender immediately by telephone or reply e-mail and destroy the original message without making a copy. Thank you.
From: Klaus Malorny <Klaus.Malorny@knipp.de>
Date: Thu, 19 Nov 2009 11:51:48 -0500
To: EPP Provreg <email@example.com>
Subject: Re: [ietf-provreg] Anyone working on 4310-bis?
I don't want to broaden the discussion even more, but I'd like to have your
comments on another question in the context of 4310-bis.
If a registrar issues a domain:update request which changes the DS data, then
this is usually a part of the KSK rollover process. The rollover process depends
on various timeouts, which rely on the TTLs of the DS records in the parent zone
and the time of update of the DS records.
Both values -- the TTL of the DS records and the update time of the name servers
-- are subject to the registry and are unavailable from the EPP point of view.
Of course, one can simply poll the name servers of the parent zones and check
whether the performed changes have become visible, or, even simpler, blindly
rely that it has happened after an ample amount of time.
On the other hand, if requested by the registrar, the EPP server *could* send a
notification via the poll mechanism to the registrar, that the name servers of
the registry now reflect the changes of a specific update that had been
processed successfully earlier. TTLs could be reported at the same time.
This could not only make sense in the context of DNSSEC, but also for name
server changes as well, and could also include create and delete requests, if
Now, would you consider such a feature as useful, as a complete nonsense, maybe
as something in-between? Would such a feature be worth the effort? If so, should
it be included in 4310-bis?
List run by majordomo software. For (Un-)subscription and similar details
send "help" to firstname.lastname@example.org
Date list |