> I see that this draft uses a syntax similar to RFC 8145 Trust Anchor > Telemetry RFC (which uses _ta-<hex_id>) albeit without the leading > underscore, i.e. .ta-<hex_id>. > > I'd like to propose instead <hex-id>._ta.<domain> > > This would allow _ta to be registered as a standalone entry in the > underscore label registry, whilst also avoid the risk of collisions with > "plain" labels that happen to match ta-<hex> > > FWIW, I think in retrospect that RFC 8145 should have taken a similar > approach too.
IIRC we discussed it, and were concerned that _ta. could be cached as nonexistent by servers implementing QNAME minimization. -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc. _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
