From bc566b7bb32d0e2686b19ef8d0944b91b77944b1 Mon Sep 17 00:00:00 2001
From: ID Bot
Date: Thu, 22 Feb 2024 11:34:09 +0000
Subject: [PATCH] Script updating gh-pages from 71cb7d3. [ci skip]
---
draft-lenders-core-dnr.html | 5 ++++-
draft-lenders-core-dnr.txt | 7 ++++++-
index.html | 2 +-
3 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/draft-lenders-core-dnr.html b/draft-lenders-core-dnr.html
index 5cc38a1..7aaf57a 100644
--- a/draft-lenders-core-dnr.html
+++ b/draft-lenders-core-dnr.html
@@ -1214,7 +1214,7 @@
DoH, DoQ or similar TLS-based solutions typically are not possible.
The Constrained Application Protocol (CoAP) [RFC7252], the transfer protocol for DoC, is mostly
agnostic to the transport layer, i.e., it can be transported over UDP, TCP, or WebSockets
-[RFC8323], and even more obscure transport such as Bluetooth GATT [I-D.amsuess-core-coap-over-gatt] or SMS
+[RFC8323], and even more obscure transports such as Bluetooth GATT [I-D.amsuess-core-coap-over-gatt] or SMS
[lwm2m] are discussed.
CoAP comes with 3 security modes that would need to be covered by the SvcParams:¶
@@ -1239,6 +1239,9 @@
keys can be set up by such an AS as described in the ACE OSCORE profile [RFC9203].¶
+In consequence, for a DoC server to be discoverable via DDR [RFC9462] and DNR [RFC9463], both transfer
+protocol and type and parameters for the security parameter need to be provided in the svcParams
+field of these mechanisms, which this document will discuss.¶
diff --git a/draft-lenders-core-dnr.txt b/draft-lenders-core-dnr.txt
index f569ae9..8a935dd 100644
--- a/draft-lenders-core-dnr.txt
+++ b/draft-lenders-core-dnr.txt
@@ -104,7 +104,7 @@ Table of Contents
Application Protocol (CoAP) [RFC7252], the transfer protocol for DoC,
is mostly agnostic to the transport layer, i.e., it can be
transported over UDP, TCP, or WebSockets [RFC8323], and even more
- obscure transport such as Bluetooth GATT
+ obscure transports such as Bluetooth GATT
[I-D.amsuess-core-coap-over-gatt] or SMS [lwm2m] are discussed. CoAP
comes with 3 security modes that would need to be covered by the
SvcParams:
@@ -129,6 +129,11 @@ Table of Contents
EDHOC, keys can be set up by such an AS as described in the ACE
OSCORE profile [RFC9203].
+ In consequence, for a DoC server to be discoverable via DDR [RFC9462]
+ and DNR [RFC9463], both transfer protocol and type and parameters for
+ the security parameter need to be provided in the svcParams field of
+ these mechanisms, which this document will discuss.
+
1.1. Problems
TODO transform into sentences:
diff --git a/index.html b/index.html
index fc96a63..5c0e8df 100644
--- a/index.html
+++ b/index.html
@@ -29,7 +29,7 @@ Preview for branch citations
CoRE DNR |
plain text |
- same as main |
+ diff with main |