Watson,
I have two major comments. The draft recapitulates bits and pieces of
the TLS 1.3 draft, but it's not clear why this is done instead of
citing that draft. I also don't understand what it means to support a
bare public key: what exactly is to be done with this key, how is it
distinguished from the case of X509 certificate, is there are RFC
already defining this feature in TLS 1.2, etc. Similar questions apply
to TOFU.
The phrase "bare public key" (or raw public key) refers to a public key
not embedded in a cert. The term has been used in several IPsec RFCs,
e.g., 5386
and 6701. The intent is to define a standard way to convey a public key
w/o any implied authentication. Are you asking for additional clarification
for how such keys are used in 1.3?
You can look at RFCs 7435 and 7469 for discussions of TOFU.
I have not read TLS 1.3 yet, but I would anticipate that the two cases
you cite
are explicitly intended to accommodate non-cert based key management,
e.g., in support
of OS.
Steve
_______________________________________________
Tcpinc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/tcpinc
