Tim,
Yes, what is meant as host-level is using the TTL extension for host objects in
RFC 5732, as opposed to using the TTL extension domain name objects in RFC
5731. There is one TTL attribute set at the domain-level or at the host-level,
so the question is what resource records that
On Tue, Sep 27, 2022 at 9:17 AM Gould, James wrote:
> Gavin,
>
> I believe the domain-level TTL applies to the records it owns, which
> include the DS, NS, and DNAME. The host-level TTL applies to the records
> it owns, which include the A and . In your examples, if we're talking
> about
Gavin,
I believe the domain-level TTL applies to the records it owns, which include
the DS, NS, and DNAME. The host-level TTL applies to the records it owns,
which include the A and . In your examples, if we're talking about the NS
TTL of the example.com delegating name server
Submitted version -02 with a first stab at both domain and host mapping.
G.
> Begin forwarded message:
>
> From: internet-dra...@ietf.org
> Subject: New Version Notification for draft-regext-brown-epp-ttl-02.txt
> Date: 27 September 2022 at 13:48:36 BST
> To: "Gavin Brown"
>
>
> A new
Thanks Rick and Jim for the feedback. I am happy to accept the idea of the
extension working for both domain and host objects and will work towards making
that a part of the next version.
One point for possible further discussion is the "priority" of TTL values: I am
going to state that the
