Göran Selander
2018-03-19 17:05:16 UTC
During the OSCORE presentation in the CoRE WG meeting today Carsten
proposed yet another name for the HTTP header field: OSCORE. As a
consequence we would also rename the CoAP option OSCORE, in which case we
have the same name for protocol, protocol message, CoAP option and HTTP
header field.
Any objections to this change?
Göran
proposed yet another name for the HTTP header field: OSCORE. As a
consequence we would also rename the CoAP option OSCORE, in which case we
have the same name for protocol, protocol message, CoAP option and HTTP
header field.
Any objections to this change?
Göran
We also followed the suggestion to rename the HTTP header field
CoAP-Object-Security.
CoAP-Object-Security.