Skip to content

Commit

Permalink
Script updating gh-pages from b11dff0. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Feb 22, 2024
1 parent aeac77e commit b9c2d11
Show file tree
Hide file tree
Showing 3 changed files with 62 additions and 19 deletions.
33 changes: 25 additions & 8 deletions draft-lenders-core-dnr.html
Original file line number Diff line number Diff line change
Expand Up @@ -1036,7 +1036,7 @@
</tr></thead>
<tfoot><tr>
<td class="left">Lenders, et al.</td>
<td class="center">Expires 24 August 2024</td>
<td class="center">Expires 25 August 2024</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
Expand All @@ -1049,12 +1049,12 @@
<dd class="internet-draft">draft-lenders-core-dnr-latest</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2024-02-21" class="published">21 February 2024</time>
<time datetime="2024-02-22" class="published">22 February 2024</time>
</dd>
<dt class="label-intended-status">Intended Status:</dt>
<dd class="intended-status">Informational</dd>
<dt class="label-expires">Expires:</dt>
<dd class="expires"><time datetime="2024-08-24">24 August 2024</time></dd>
<dd class="expires"><time datetime="2024-08-25">25 August 2024</time></dd>
<dt class="label-authors">Authors:</dt>
<dd class="authors">
<div class="author">
Expand Down Expand Up @@ -1115,7 +1115,7 @@ <h2 id="name-status-of-this-memo">
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."<a href="#section-boilerplate.1-3" class="pilcrow"></a></p>
<p id="section-boilerplate.1-4">
This Internet-Draft will expire on 24 August 2024.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
This Internet-Draft will expire on 25 August 2024.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
</section>
</div>
<div id="copyright">
Expand Down Expand Up @@ -1215,7 +1215,7 @@ <h2 id="name-introduction">
The Constrained Application Protocol (CoAP) <span>[<a href="#RFC7252" class="cite xref">RFC7252</a>]</span>, the transfer protocol for DoC, is mostly
agnostic to the transport layer, i.e., it can be transported over UDP, TCP, or WebSockets
<span>[<a href="#RFC8323" class="cite xref">RFC8323</a>]</span>, and even more obscure transport such as Bluetooth GATT <span>[<a href="#I-D.amsuess-core-coap-over-gatt" class="cite xref">I-D.amsuess-core-coap-over-gatt</a>]</span> or SMS
[tbd-citation] are discussed.
<span>[<a href="#lwm2m" class="cite xref">lwm2m</a>]</span> are discussed.
CoAP comes with 3 security modes that would need to be covered by the SvcParams:<a href="#section-1-2" class="pilcrow"></a></p>
<ul class="normal">
<li class="normal" id="section-1-3.1">
Expand All @@ -1229,9 +1229,14 @@ <h2 id="name-introduction">
</li>
<li class="normal" id="section-1-3.3">
<p id="section-1-3.3.1"><strong>Object Security:</strong> Application-layer based object encryption within CoAP based on OSCORE
<span>[<a href="#RFC8613" class="cite xref">RFC8613</a>]</span>. OSCORE can be either used as an alternative or in addition to transport security.
EDHOC <span>[<a href="#I-D.ietf-core-oscore-edhoc" class="cite xref">I-D.ietf-core-oscore-edhoc</a>]</span> is used to establish the encryption context between two hosts and OSCORE-ACE
[citation?] can be used for authentication of a server.<a href="#section-1-3.3.1" class="pilcrow"></a></p>
<span>[<a href="#RFC8613" class="cite xref">RFC8613</a>]</span>. OSCORE can be either used as an alternative or in addition to transport security.<a href="#section-1-3.3.1" class="pilcrow"></a></p>
<p id="section-1-3.3.2">
OSCORE keys are not usable indefinitely and need to be set up,
for example through an EDHOC key exchange <span>[<a href="#I-D.ietf-core-oscore-edhoc" class="cite xref">I-D.ietf-core-oscore-edhoc</a>]</span>,
which may use credentials from trusted authorization server (AS)
as described in the ACE EDHOC profile <span>[<a href="#I-D.ietf-ace-edhoc-oscore-profile" class="cite xref">I-D.ietf-ace-edhoc-oscore-profile</a>]</span>.
As an alternative to EDHOC,
keys can be set up by such an AS as described in the ACE OSCORE profile <span>[<a href="#RFC9203" class="cite xref">RFC9203</a>]</span>.<a href="#section-1-3.3.2" class="pilcrow"></a></p>
</li>
</ul>
<div id="problems">
Expand Down Expand Up @@ -1479,6 +1484,14 @@ <h3 id="name-informative-references">
<dd>
<span class="refAuthor">Amsüss, C.</span>, <span class="refTitle">"CoAP over GATT (Bluetooth Low Energy Generic Attributes)"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-amsuess-core-coap-over-gatt-05</span>, <time datetime="2023-10-23" class="refDate">23 October 2023</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-amsuess-core-coap-over-gatt-05">https://datatracker.ietf.org/doc/html/draft-amsuess-core-coap-over-gatt-05</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="I-D.ietf-ace-edhoc-oscore-profile">[I-D.ietf-ace-edhoc-oscore-profile]</dt>
<dd>
<span class="refAuthor">Selander, G.</span>, <span class="refAuthor">Mattsson, J. P.</span>, <span class="refAuthor">Tiloca, M.</span>, and <span class="refAuthor">R. Höglund</span>, <span class="refTitle">"Ephemeral Diffie-Hellman Over COSE (EDHOC) and Object Security for Constrained Environments (OSCORE) Profile for Authentication and Authorization for Constrained Environments (ACE)"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-ace-edhoc-oscore-profile-03</span>, <time datetime="2023-10-23" class="refDate">23 October 2023</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-ace-edhoc-oscore-profile-03">https://datatracker.ietf.org/doc/html/draft-ietf-ace-edhoc-oscore-profile-03</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="lwm2m">[lwm2m]</dt>
<dd>
<span class="refAuthor">OMA SpecWorks</span>, <span class="refTitle">"White Paper – Lightweight M2M 1.1"</span>, <time datetime="2018-10" class="refDate">October 2018</time>, <span>&lt;<a href="https://omaspecworks.org/white-paper-lightweight-m2m-1-1/">https://omaspecworks.org/white-paper-lightweight-m2m-1-1/</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7858">[RFC7858]</dt>
<dd>
<span class="refAuthor">Hu, Z.</span>, <span class="refAuthor">Zhu, L.</span>, <span class="refAuthor">Heidemann, J.</span>, <span class="refAuthor">Mankin, A.</span>, <span class="refAuthor">Wessels, D.</span>, and <span class="refAuthor">P. Hoffman</span>, <span class="refTitle">"Specification for DNS over Transport Layer Security (TLS)"</span>, <span class="seriesInfo">RFC 7858</span>, <span class="seriesInfo">DOI 10.17487/RFC7858</span>, <time datetime="2016-05" class="refDate">May 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc7858">https://www.rfc-editor.org/rfc/rfc7858</a>&gt;</span>. </dd>
Expand All @@ -1495,6 +1508,10 @@ <h3 id="name-informative-references">
<dd>
<span class="refAuthor">Hoffman, P.</span> and <span class="refAuthor">P. McManus</span>, <span class="refTitle">"DNS Queries over HTTPS (DoH)"</span>, <span class="seriesInfo">RFC 8484</span>, <span class="seriesInfo">DOI 10.17487/RFC8484</span>, <time datetime="2018-10" class="refDate">October 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc8484">https://www.rfc-editor.org/rfc/rfc8484</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC9203">[RFC9203]</dt>
<dd>
<span class="refAuthor">Palombini, F.</span>, <span class="refAuthor">Seitz, L.</span>, <span class="refAuthor">Selander, G.</span>, and <span class="refAuthor">M. Gunnarsson</span>, <span class="refTitle">"The Object Security for Constrained RESTful Environments (OSCORE) Profile of the Authentication and Authorization for Constrained Environments (ACE) Framework"</span>, <span class="seriesInfo">RFC 9203</span>, <span class="seriesInfo">DOI 10.17487/RFC9203</span>, <time datetime="2022-08" class="refDate">August 2022</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc9203">https://www.rfc-editor.org/rfc/rfc9203</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC9250">[RFC9250]</dt>
<dd>
<span class="refAuthor">Huitema, C.</span>, <span class="refAuthor">Dickinson, S.</span>, and <span class="refAuthor">A. Mankin</span>, <span class="refTitle">"DNS over Dedicated QUIC Connections"</span>, <span class="seriesInfo">RFC 9250</span>, <span class="seriesInfo">DOI 10.17487/RFC9250</span>, <time datetime="2022-05" class="refDate">May 2022</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc9250">https://www.rfc-editor.org/rfc/rfc9250</a>&gt;</span>. </dd>
Expand Down
46 changes: 36 additions & 10 deletions draft-lenders-core-dnr.txt
Original file line number Diff line number Diff line change
Expand Up @@ -5,12 +5,12 @@
Constrained RESTful Environments M. S. Lenders
Internet-Draft TU Dresden
Intended status: Informational C. Amsüss
Expires: 24 August 2024
Expires: 25 August 2024
T. C. Schmidt
HAW Hamburg
M. Wählisch
TU Dresden & Barkhausen Institut
21 February 2024
22 February 2024


Discovery of Network-designated CoRE Resolvers
Expand Down Expand Up @@ -52,7 +52,7 @@ Status of This Memo
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."

This Internet-Draft will expire on 24 August 2024.
This Internet-Draft will expire on 25 August 2024.

Copyright Notice

Expand Down Expand Up @@ -105,9 +105,9 @@ Table of Contents
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 [tbd-citation] are
discussed. CoAP comes with 3 security modes that would need to be
covered by the SvcParams:
[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:

* *No Security:* No encryption, just plain CoAP. While not
recommended with [I-D.ietf-core-dns-over-coap], this mode provides
Expand All @@ -119,10 +119,15 @@ Table of Contents

* *Object Security:* Application-layer based object encryption
within CoAP based on OSCORE [RFC8613]. OSCORE can be either used
as an alternative or in addition to transport security. EDHOC
[I-D.ietf-core-oscore-edhoc] is used to establish the encryption
context between two hosts and OSCORE-ACE [citation?] can be used
for authentication of a server.
as an alternative or in addition to transport security.

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

1.1. Problems

Expand Down Expand Up @@ -302,6 +307,20 @@ Table of Contents
<https://datatracker.ietf.org/doc/html/draft-amsuess-core-
coap-over-gatt-05>.

[I-D.ietf-ace-edhoc-oscore-profile]
Selander, G., Mattsson, J. P., Tiloca, M., and R. Höglund,
"Ephemeral Diffie-Hellman Over COSE (EDHOC) and Object
Security for Constrained Environments (OSCORE) Profile for
Authentication and Authorization for Constrained
Environments (ACE)", Work in Progress, Internet-Draft,
draft-ietf-ace-edhoc-oscore-profile-03, 23 October 2023,
<https://datatracker.ietf.org/doc/html/draft-ietf-ace-
edhoc-oscore-profile-03>.

[lwm2m] OMA SpecWorks, "White Paper – Lightweight M2M 1.1",
October 2018, <https://omaspecworks.org/white-paper-
lightweight-m2m-1-1/>.

[RFC7858] Hu, Z., Zhu, L., Heidemann, J., Mankin, A., Wessels, D.,
and P. Hoffman, "Specification for DNS over Transport
Layer Security (TLS)", RFC 7858, DOI 10.17487/RFC7858, May
Expand All @@ -322,6 +341,13 @@ Table of Contents
(DoH)", RFC 8484, DOI 10.17487/RFC8484, October 2018,
<https://www.rfc-editor.org/rfc/rfc8484>.

[RFC9203] Palombini, F., Seitz, L., Selander, G., and M. Gunnarsson,
"The Object Security for Constrained RESTful Environments
(OSCORE) Profile of the Authentication and Authorization
for Constrained Environments (ACE) Framework", RFC 9203,
DOI 10.17487/RFC9203, August 2022,
<https://www.rfc-editor.org/rfc/rfc9203>.

[RFC9250] Huitema, C., Dickinson, S., and A. Mankin, "DNS over
Dedicated QUIC Connections", RFC 9250,
DOI 10.17487/RFC9250, May 2022,
Expand Down
2 changes: 1 addition & 1 deletion index.html
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ <h2>Preview for branch <a href="citations">citations</a></h2>
<tr>
<td><a href="citations/draft-lenders-core-dnr.html" class="html draft-lenders-core-dnr" title="Discovery of Network-designated CoRE Resolvers (HTML)">CoRE DNR</a></td>
<td><a href="citations/draft-lenders-core-dnr.txt" class="txt draft-lenders-core-dnr" title="Discovery of Network-designated CoRE Resolvers (Text)">plain text</a></td>
<td><a href="https://author-tools.ietf.org/api/iddiff?url_1=https://anr-bmbf-pivot.github.io/draft-lenders-core-dnr/draft-lenders-core-dnr.txt&amp;url_2=https://anr-bmbf-pivot.github.io/draft-lenders-core-dnr/citations/draft-lenders-core-dnr.txt" class="diff draft-lenders-core-dnr">diff with main</a></td>
<td>same as main</td>
</tr>
</table>
<script>
Expand Down

0 comments on commit b9c2d11

Please sign in to comment.