Hi Jim, apologies for the delayed response.
> On 20 Dec 2023, at 15:26, Gould, James
> wrote:
>
> Gavin,
>
> Thanks for making the updates in draft-ietf-regext-epp-ttl-04. I went ahead
> and implemented draft-ietf-regext-epp-ttl-04 in the Verisign EPP SDK that
> implements a client and a
Gavin,
Thanks for making the updates in draft-ietf-regext-epp-ttl-04. I went ahead
and implemented draft-ietf-regext-epp-ttl-04 in the Verisign EPP SDK that
implements a client and a server. I did find the following issue:
The “commandTTLType“ is missing the optional “custom” attribute
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
