Hello Marc,
we're working on an implementation for our gTLD registries, but there's no
"running service" available yet. We might have something available in 2-3
months time, at which point I'm happy to come back to you again to run your
clients against our "test" implementation.
Best,
Alex
Dear Gavin.
Thanks for including the clarifications for the host-as-attributes
model!
I reviewed the document and found two problems:
- in 1.2 second point, and in 1.2.2 second paragraph, the reference
to "Section 1.3 of [RFC6895]" for the record type format is wrong.
There's no 1.3 section.
Greetings all,
I have just uploaded draft-ietf-regext-epp-ttl-04.
Notable changes in this version:
* The "for" attribute is now an enumeration, and can take the following values:
NS, DS, DNAME, A, , custom.
* If the "for" attribute is "custom", then the "custom" attribute can be used
to
Internet-Draft draft-ietf-regext-epp-ttl-04.txt is now available. It is a work
item of the Registration Protocols Extensions (REGEXT) WG of the IETF.
Title: Extensible Provisioning Protocol (EPP) mapping for DNS Time-To-Live
(TTL) values
Author: Gavin Brown
Name:
Hello,
As I’m currently working on a new version of RDAP Browser (a mobile RDAP
client on iOS and Android), I would like to know if some registries (either
domain or RIR) have or are about to implement draft-ietf-regext-redacted as it
is on its way to RFC. I would like to test my client on
