Hi Shigeya, (speaking for myself)
On 11/9/26 05:12, Shigeya Suzuki wrote:
We separated OPKEY from TLSA following the precedent of SMIMEA
(RFC 8162) and OPENPGPKEY (RFC 7929), which have types of their own,
so as to keep a record that means "this key is current for this name
in the Originator Profile Framework" apart from the TLS association
that TLSA means.
TLSA does not mean "TLS assocation". See RFC 6698 Section 1.2:
"TLSA" does not stand for anything; it is just the name of the RRtype.
Ben made a related point: SVCB identifies endpoints, and this record
names none. The next revision will move this record off SVCB, and PTR
is now among the candidates, with a dedicated type as Ben suggests,
TXT, and URI (RFC 7553). PTR has clear attractions here: it is an
existing type, its RDATA is a domain name and needs no parsing, and
an originator that accepts several CP issuers publishes several RRs.
What it would still need is a way to say that the originator has no
profile at all, which the AliasMode "." of SVCB gave us; I would be
interested in your view on how best to express that with PTR.
Well, do you think "." could be an option? It seems like there is some prior
art for that semantic :-)
Best,
Peter
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]