[regext] Re: [Ext] Secdir last call review of draft-ietf-regext-epp-ttl-15

[Gavin Brown <[e-mail]>]

Hi all,

I've taken the liberty of uploading version -17 to add this section.

https://www.ietf.org/archive/id/draft-ietf-regext-epp-ttl-17.html#name-changes-to-server-policy

Diff to the previous version: https://author-tools.ietf.org/iddiff?url2=draft-ietf-regext-epp-ttl-17

G.

> On 11 Oct 2024, at 10:48, Gavin Brown <[e-mail]> wrote:
> 
> Hi Wes,
> 
>>> Policy changes will almost certainly only happen infrequently, and the
>>> omission was intentional on my point. Do you feel it warrants some
>>> discussion in the document?
>> 
>> I think inserting a warning note would be helpful to the reader.
>> Something along the lines of "Although a client is requesting a
>> particular TTL value that is within the current acceptable range,
>> registries are not obligated to maintain that value indefinitely and may
>> change the value when, for example, they update their acceptable TTL
>> value ranges."
> 
> In my working draft[1] I have added a new Section 5.3, which says:
> 
> "Registry operators may change their policies relating to TTL values from time to time. Previously configured TTL values may consequently fall outside a newly-applied policy. This document places no obligation on EPP server operators in respect of these values, and server operators may, as part of a policy change, change the TTL values specified by clients for domain and host objects. Section 4 describes how such out-of-band changes should be carried out."
> 
> Let me know what you think. If it looks good I can upload a new version.
> 
> G.
> 
> [1] https://github.com/gbxyz/epp-ttl-extension/commit/b8bf5d56779fb5a0123401558fd6cab654348c85#diff-e81d8d738f47db9115098e0fe66a7a9904ca10821206e12ff5229e5e384b648cR577

--
Gavin Brown
Principal Engineer, Global Domains & Strategy
Internet Corporation for Assigned Names and Numbers (ICANN)

https://www.icann.org