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 from the
“commandTTLType”, so the “custom” rrec type cannot be specified in the create
and update commands.
I have the following recommendation:
I implemented from the full examples included in the draft, so my
recommendation is to include the use of the <ttl:ttl for=”custom”
custom=”DELEG”>3600</ttl:ttl> in the domain create and domain info response
examples to cover all
elements defined in the XML schema. Of course, there no method yet to define
the attributes for the DELEG resource record itself, but that’s not important
for this draft.
What’s not clear in the server, is the set of <ttl> elements to return in the
info response. Should the server return only the <ttl> elements that have been
explicitly set or should the server return the <ttl> elements for all support
resource record types? Inclusion of the TTL server policy attributes (“min”,
“max”, and “default”) would make the case to include all supported resource
record types, which seems overkill to include in all domain and host info
responses by default. I believe it’s best to extend the info command with an
<ttl:info> element that includes the option to include the policy attributes in
the info response, which would also include the full set of supported resource
record types with the server policy attributes. Such as the following domain
info command extensions:
Domain Info Command that only includes the set TTL records in the domain info
response:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
<command>
<info>
<domain:info
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
<domain:name>example.com</domain:name>
</domain:info>
</info>
<extension>
<ttl:info
xmlns:ttl="urn:ietf:params:xml:ns:epp:ttl-1.0"/>
</extension>
<clTRID>ABC-12345</clTRID>
</command>
</epp>
Domain Info Command that includes the supported TTL records with the server
policy attributes in the domain info response:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
<command>
<info>
<domain:info
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
<domain:name>example.com</domain:name>
</domain:info>
</info>
<extension>
<ttl:info
xmlns:ttl="urn:ietf:params:xml:ns:epp:ttl-1.0"
policy="true"/>
</extension>
<clTRID>ABC-12345</clTRID>
</command>
</epp>
This enables the client to choose what information they want included in the
info response and does not include the TTL extension with all support TTL
records by default in every domain and host response.
Thanks,
--
JG
James Gould
Fellow Engineer
jgo...@verisign.com
<applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgo...@verisign.com>
703-948-3271
12061 Bluemont Way
Reston, VA 20190
Verisign.com <http://verisigninc.com/>
On 12/14/23, 12:26 PM, "regext on behalf of Gavin Brown"
<regext-boun...@ietf.org <mailto:regext-boun...@ietf.org> on behalf of
gavin.br...@icann.org <mailto:gavin.br...@icann.org>> wrote:
Caution: This email originated from outside the organization. Do not click
links or open attachments unless you recognize the sender and know the content
is safe.
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, AAAA, custom.
* If the "for" attribute is "custom", then the "custom" attribute can be used
to specify a DNS record type other than those above. However, it still has to
match the regular expression from RFC 6895 and still has to be registered with
IANA.
* <ttl> elements - in responses only - must have the "min", "default" and "max"
attributes. I'm open to feedback about making them mandatory but I think they
are so useful to clients that there would have to be a pretty compelling reason
to remove the "required" XSD property.
This version also closes off the backlog of changes I had planned, so unless
the WG has more feedback, I think this draft is basically done from a
functional perspective I will however require to complete the Implementation
Status section to get to the RFC publication stage.
Thanks,
> On 14 Dec 2023, at 17:06, internet-dra...@ietf.org
> <mailto:internet-dra...@ietf.org> wrote:
>
> 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: draft-ietf-regext-epp-ttl-04.txt
> Pages: 21
> Dates: 2023-12-14
>
> Abstract:
>
> This document describes an extension to the Extensible Provisioning
> Protocol (EPP) that allows EPP clients to manage the Time-To-Live
> (TTL) value for domain name delegation records.
>
> About this draft
>
> This note is to be removed before publishing as an RFC.
>
> The source for this draft, and an issue tracker, may can be found at
> https://secure-web.cisco.com/14NtlJSWQw8Lv7hMPifpgnsilIvx-Elr2EEzMYhc1C7g8m4cFsEeaerglbRVbEFY7PSFQDL-fIj9qAfez6VVEXcwUixt7wnTbtRQnWCIGclGqjsMzjchaEuewSSbvVvO4R_WuiE3n6v31bWGXI1uQPI-_6BW9u4kSvrq8ZeFYLH5DDvuWkNYr94ZwNda1RVBzFpBu10LDA7rF0VpmoAdzqR3Y4lhDdTHB51ih0Sf0-ik81CVm1ipfsLKQFrm_1ykscu_swTgciGeJL8H6PFRTgXK-a20oCURz-2-USI1KsOg/https%3A%2F%2Fgithub.com%2Fgbxyz%2Fepp-ttl-extension
>
> <https://secure-web.cisco.com/14NtlJSWQw8Lv7hMPifpgnsilIvx-Elr2EEzMYhc1C7g8m4cFsEeaerglbRVbEFY7PSFQDL-fIj9qAfez6VVEXcwUixt7wnTbtRQnWCIGclGqjsMzjchaEuewSSbvVvO4R_WuiE3n6v31bWGXI1uQPI-_6BW9u4kSvrq8ZeFYLH5DDvuWkNYr94ZwNda1RVBzFpBu10LDA7rF0VpmoAdzqR3Y4lhDdTHB51ih0Sf0-ik81CVm1ipfsLKQFrm_1ykscu_swTgciGeJL8H6PFRTgXK-a20oCURz-2-USI1KsOg/https%3A%2F%2Fgithub.com%2Fgbxyz%2Fepp-ttl-extension>
>
> The IETF datatracker status page for this Internet-Draft is:
> https://secure-web.cisco.com/1_qNpvbtjZ4irDWmBaep562ShK8C2tW10UMh89FMXap3FnuyBJeCyaWWDsuM7DEpW3IC9ZLVkOyVzJsTPB4o2OdHXoS-zDAT3dtxSY5DR1vXPvd74wto3lyIw-z1INFj1mVnW4PmF2ZIXVRGJ1oIGmz1ZJf1_-fE0bsWXPMq9Vxm-VRmKYcHC2E0o8gbJpoFPBkhhOFXeIBpiH-SZ24X1COzRYc8ZGnRHssX1VIlDwh6nAw2lNNuXoxDqkGLsrCxvr2WMx0JXQw3yfYEU9PM8UoUI0un6lo3auJUe85xsYI0/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-regext-epp-ttl%2F
>
> <https://secure-web.cisco.com/1_qNpvbtjZ4irDWmBaep562ShK8C2tW10UMh89FMXap3FnuyBJeCyaWWDsuM7DEpW3IC9ZLVkOyVzJsTPB4o2OdHXoS-zDAT3dtxSY5DR1vXPvd74wto3lyIw-z1INFj1mVnW4PmF2ZIXVRGJ1oIGmz1ZJf1_-fE0bsWXPMq9Vxm-VRmKYcHC2E0o8gbJpoFPBkhhOFXeIBpiH-SZ24X1COzRYc8ZGnRHssX1VIlDwh6nAw2lNNuXoxDqkGLsrCxvr2WMx0JXQw3yfYEU9PM8UoUI0un6lo3auJUe85xsYI0/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-regext-epp-ttl%2F>
>
> There is also an HTMLized version available at:
> https://secure-web.cisco.com/19iv9_fsa1Cd3Zd5bp8RR1zkvz-rCLfVXftpZABB4V8CsGrAxFu0rTr4YhfimNpGhcXPPsC8z3ajXV3n1uMCl3QaqvLDS8H6JhO4SGYWenxggtXNoCaNRBFTJ7-aHO4vZor_xVEJXICs02O-vN2Tya4sRatb4gYLfEFOwYJ-Wr4tXW5mloCTHScuVqTNpwEzQm2Uinp9k6wEdOFKHujmqS7OC42WV1_lT_xW36m6Mnzhc3VLvaheTKGfmrxcXVxqMJWH7e-G_X_Um02XAuJwTNoAU6H-NcaetiiQY1Mka9ac/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-regext-epp-ttl-04
>
> <https://secure-web.cisco.com/19iv9_fsa1Cd3Zd5bp8RR1zkvz-rCLfVXftpZABB4V8CsGrAxFu0rTr4YhfimNpGhcXPPsC8z3ajXV3n1uMCl3QaqvLDS8H6JhO4SGYWenxggtXNoCaNRBFTJ7-aHO4vZor_xVEJXICs02O-vN2Tya4sRatb4gYLfEFOwYJ-Wr4tXW5mloCTHScuVqTNpwEzQm2Uinp9k6wEdOFKHujmqS7OC42WV1_lT_xW36m6Mnzhc3VLvaheTKGfmrxcXVxqMJWH7e-G_X_Um02XAuJwTNoAU6H-NcaetiiQY1Mka9ac/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-regext-epp-ttl-04>
>
> A diff from the previous version is available at:
> https://secure-web.cisco.com/1PEv7Vt6N2OJUlX8W9WpRebLI4461YwyLqMDwkgxozmY4OZRxOb_sO4z2HJ6D4AqqEthj7yTMhUikaL344Z8u9EE4FjsNeM1Kiis37TZ5omItimSqeqxCWL3czGr1dWFO8KTGYp5hf2Hb8bGyTTGGlRy68BUbeHcx0NFfjzfb_edA264pHuOSe3iWK1A40YP8WpQ0-Unlrgy8WerEC8LJposQbTLIiOXFtOqjRVypOpKWFKEzhFnmuaocczQPm9ChktZwlpOeA52BBRSAIYp-0DvrzBvVn0LezvZ31APpDsk/https%3A%2F%2Fauthor-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-ietf-regext-epp-ttl-04
>
> <https://secure-web.cisco.com/1PEv7Vt6N2OJUlX8W9WpRebLI4461YwyLqMDwkgxozmY4OZRxOb_sO4z2HJ6D4AqqEthj7yTMhUikaL344Z8u9EE4FjsNeM1Kiis37TZ5omItimSqeqxCWL3czGr1dWFO8KTGYp5hf2Hb8bGyTTGGlRy68BUbeHcx0NFfjzfb_edA264pHuOSe3iWK1A40YP8WpQ0-Unlrgy8WerEC8LJposQbTLIiOXFtOqjRVypOpKWFKEzhFnmuaocczQPm9ChktZwlpOeA52BBRSAIYp-0DvrzBvVn0LezvZ31APpDsk/https%3A%2F%2Fauthor-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-ietf-regext-epp-ttl-04>
>
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
>
>
> _______________________________________________
> regext mailing list
> regext@ietf.org <mailto:regext@ietf.org>
> https://secure-web.cisco.com/1NU0qtQxVL_EASJbq3mDdyifa71I2kkAugcu5z-jK-ZMhwphzQBlVHIZtcgOSv3Nn9tqh6JsbB07LLzpmMsWD75uHTQtC09DHWb7VhLseZa9iXwo271QL_ByGwYmOyKWymWiVGxDbSkLgg4n9GyFuv5Y4cHxATWF2bjJsc25aixerbxnxXVNADDVDCXo2H3aRe7jyR4DxlTruezMrd2Lpe6h5c5cAlxhSYrxAPnFm9K8VtqI9oZ9D4DnfZ8Hz9xMPz_Kis05teMQY9Rk1cUAPuzKPwJEpDyxiPnNEP7X8LI0/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext
>
> <https://secure-web.cisco.com/1NU0qtQxVL_EASJbq3mDdyifa71I2kkAugcu5z-jK-ZMhwphzQBlVHIZtcgOSv3Nn9tqh6JsbB07LLzpmMsWD75uHTQtC09DHWb7VhLseZa9iXwo271QL_ByGwYmOyKWymWiVGxDbSkLgg4n9GyFuv5Y4cHxATWF2bjJsc25aixerbxnxXVNADDVDCXo2H3aRe7jyR4DxlTruezMrd2Lpe6h5c5cAlxhSYrxAPnFm9K8VtqI9oZ9D4DnfZ8Hz9xMPz_Kis05teMQY9Rk1cUAPuzKPwJEpDyxiPnNEP7X8LI0/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext>
--
Gavin Brown
Principal Engineer, Global Domains & Strategy
Internet Corporation for Assigned Names and Numbers (ICANN)
https://secure-web.cisco.com/1vOnPoJ7i1eXTEl4laHUx9Fw2EJ1o77X3XtyouyEdyYkgxqpCxmJ73hSQ1M3z1xvxXsB_qFRmYo54AK2xlcmWWexy8mzRqSL1BCXuxhbV6CJzEElVVoGVDda89LQryoCo1FHyIyVBgYFAwiYBB9TRwtd_WnUBrNax0dErt5re9L_wOOqVuqaVG9D7bM9cC5wQ4G-XYo80q_4wVb4W0B1r7AF6PfeUGjGtvhj6LZiS3YzYgW8seCfcmSY_pN7zXoVKSfC9SEArix5xvVuUUdFvjgF17rN8ReY-6fceB4CYbKA/https%3A%2F%2Fwww.icann.org
<https://secure-web.cisco.com/1vOnPoJ7i1eXTEl4laHUx9Fw2EJ1o77X3XtyouyEdyYkgxqpCxmJ73hSQ1M3z1xvxXsB_qFRmYo54AK2xlcmWWexy8mzRqSL1BCXuxhbV6CJzEElVVoGVDda89LQryoCo1FHyIyVBgYFAwiYBB9TRwtd_WnUBrNax0dErt5re9L_wOOqVuqaVG9D7bM9cC5wQ4G-XYo80q_4wVb4W0B1r7AF6PfeUGjGtvhj6LZiS3YzYgW8seCfcmSY_pN7zXoVKSfC9SEArix5xvVuUUdFvjgF17rN8ReY-6fceB4CYbKA/https%3A%2F%2Fwww.icann.org>
_______________________________________________
regext mailing list
regext@ietf.org <mailto:regext@ietf.org>
https://secure-web.cisco.com/1NU0qtQxVL_EASJbq3mDdyifa71I2kkAugcu5z-jK-ZMhwphzQBlVHIZtcgOSv3Nn9tqh6JsbB07LLzpmMsWD75uHTQtC09DHWb7VhLseZa9iXwo271QL_ByGwYmOyKWymWiVGxDbSkLgg4n9GyFuv5Y4cHxATWF2bjJsc25aixerbxnxXVNADDVDCXo2H3aRe7jyR4DxlTruezMrd2Lpe6h5c5cAlxhSYrxAPnFm9K8VtqI9oZ9D4DnfZ8Hz9xMPz_Kis05teMQY9Rk1cUAPuzKPwJEpDyxiPnNEP7X8LI0/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext
<https://secure-web.cisco.com/1NU0qtQxVL_EASJbq3mDdyifa71I2kkAugcu5z-jK-ZMhwphzQBlVHIZtcgOSv3Nn9tqh6JsbB07LLzpmMsWD75uHTQtC09DHWb7VhLseZa9iXwo271QL_ByGwYmOyKWymWiVGxDbSkLgg4n9GyFuv5Y4cHxATWF2bjJsc25aixerbxnxXVNADDVDCXo2H3aRe7jyR4DxlTruezMrd2Lpe6h5c5cAlxhSYrxAPnFm9K8VtqI9oZ9D4DnfZ8Hz9xMPz_Kis05teMQY9Rk1cUAPuzKPwJEpDyxiPnNEP7X8LI0/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext>
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
