Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explain EDHOC or alternatives as OSCORE boostraps, add citations #1

Merged
merged 2 commits into from
Feb 22, 2024
Merged

Explain EDHOC or alternatives as OSCORE boostraps, add citations #1

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e4220c1
Add citation for CoAP-over-SMS
chrysn Feb 22, 2024
3e8bba0
Explain EDHOC or alternatives as OSCORE boostraps, add citations for …
chrysn Feb 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 16 additions & 4 deletions draft-lenders-core-dnr.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,14 @@ informative:
RFC8484: doh
RFC9250: doq
I-D.amsuess-core-coap-over-gatt: coap-gatt

lwm2m:
title: White Paper – Lightweight M2M 1.1
author:
org: OMA SpecWorks
date: 2018-10
target: https://omaspecworks.org/white-paper-lightweight-m2m-1-1/
chrysn marked this conversation as resolved.
Show resolved Hide resolved
I-D.ietf-ace-edhoc-oscore-profile: ace-edhoc
RFC9203: ace-oscore

--- abstract

Expand All @@ -88,7 +95,7 @@ DoH, DoQ or similar TLS-based solutions typically are not possible.
The Constrained Application Protocol (CoAP) {{-coap}}, the transfer protocol for DoC, is mostly
agnostic to the transport layer, i.e., it can be transported over UDP, TCP, or WebSockets
{{-coap-tcp}}, and even more obscure transport such as Bluetooth GATT {{-coap-gatt}} or SMS
[tbd-citation] are discussed.
{{lwm2m}} are discussed.
CoAP comes with 3 security modes that would need to be covered by the SvcParams:

- **No Security:** No encryption, just plain CoAP. While not recommended with {{-doc}}, this mode
Expand All @@ -98,8 +105,13 @@ CoAP comes with 3 security modes that would need to be covered by the SvcParams:
transfered over TCP {{-coap-tcp}}.
- **Object Security:** Application-layer based object encryption within CoAP based on OSCORE
{{-oscore}}. OSCORE can be either used as an alternative or in addition to transport security.
EDHOC {{-edhoc}} is used to establish the encryption context between two hosts and OSCORE-ACE
[citation?] can be used for authentication of a server.

OSCORE keys are not usable indefinitely and need to be set up,
for example through an EDHOC key exchange {{-edhoc}},
which may use credentials from trusted authorization server (AS)
as described in the ACE EDHOC profile {{-ace-edhoc}}.
As an alternative to EDHOC,
keys can be set up by such an AS as described in the ACE OSCORE profile {{-ace-oscore}}.

## Problems

Expand Down
Loading