On 24/09/2012 12:51, Paul Hoffman wrote:
I'm starting this as a new thread because Richard conflated two
topics *and* missed the fact that there is already a WG document.
The question becomes what the registration of an RRtype "means". If
it means the bits on the wire of the *response* and their semantics,
then I think the S/MIME document can use the TLSA RRtype. If an
RRtype also means the bits on the wire of the request and response,
we can't.
Personally, I think that the RRtype is defined just by the bits in
the response, so we could reuse, but others might disagree.
--Paul Hoffman
There are are two parts to TLSA reuse.
1) the RDATA format
2) The registries created for TLSA RR fields.
a) TLSA Certificate Usages
b) TLSA Selectors
c) TLSA Matching Types
Reuse of the TLSA format under another name can specify a different set
of registries to use for the different fields.
Reuse of TLSA RR by a protocol means subscribing to supporting new
entries in the above registries and even allowing new entries in there
that only make sense in one context.
Current draft is silent on registry usage, which I take to mean that the
TLSA registries are shared/inherited.
Having said this I'm not sure if I care if TLSA is used or SMIMEA.
PaulW, there is nothing in RFC6698 that says that NON-TLS uses of TLSA
MUST use the same naming schema as TLS uses.
Olafur
_______________________________________________
dane mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dane
