Hi Gavin! It seems to me that there is a case of use that is not being considered, when the NS and their glues are defined as an attribute of the domain object, without having a host object.
If we consider a create command with a domain object like the example
1.1 in RFC5731:
<domain:ns>
<domain:hostAttr>
<domain:hostName>ns1.example.net</domain:hostName>
<domain:hostAddr
ip="v4">192.0.2.2</domain:hostAddr>
<domain:hostAddr
ip="v6">1080:0:0:0:8:800:200C:417A</domain:hostAddr>
</domain:hostAttr>
<domain:hostAttr>
<domain:hostName>ns2.example.net</domain:hostName>
</domain:hostAttr>
</domain:ns>
then the ttl extension can't differentiate between a TTL for the NS
RRset and TTLs for the A/AAAA RR glue records.
If we want to allow different TTLs to be delivered for nameservers and
glues, an attribute could be added for the ttl:infData element such as
"rrtype=NS|A|AAAA".
Thanks,
Hugo
signature.asc
Description: PGP signature
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
