From b0317fdf83fc9f3d158c1319b4bcabace7ad1da6 Mon Sep 17 00:00:00 2001
From: ID Bot <idbot@example.com>
Date: Thu, 25 Jan 2024 10:19:00 +0000
Subject: [PATCH] Script updating gh-pages from f40b5e0. [ci skip]

---
 draft-ietf-core-oscore-capable-proxies.html | 4 ++--
 draft-ietf-core-oscore-capable-proxies.txt  | 8 ++++----
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/draft-ietf-core-oscore-capable-proxies.html b/draft-ietf-core-oscore-capable-proxies.html
index d22fe21..edc767d 100644
--- a/draft-ietf-core-oscore-capable-proxies.html
+++ b/draft-ietf-core-oscore-capable-proxies.html
@@ -8,7 +8,7 @@
 <meta content="Marco Tiloca" name="author">
 <meta content="Rikard Höglund" name="author">
 <meta content="
-       Object Security for Constrained RESTful Environments (OSCORE) can be used to protect CoAP messages end-to-end between two endpoints at the application layer, also in the presence of intermediaries such as proxies. This document defines how to use OSCORE for protecting CoAP messages also between an origin application endpoint and an intermediary, or between two intermediaries. Also, it defines rules to selectively escalate the protection of a CoAP option, in order to encrypt and integrity-protect it whenever possible. Finally, it defines how to secure a CoAP message by applying multiple, nested OSCORE protections, e.g., both end-to-end between origin application endpoints, as well as between an application endpoint and an intermediary or between two intermediaries. Thus, this document updates RFC 8613. The same approach can be seamlessly used with Group OSCORE, for protecting CoAP messages when group communication is used in the presence of intermediaries. 
+       Object Security for Constrained RESTful Environments (OSCORE) can be used to protect CoAP messages end-to-end between two endpoints at the application layer, also in the presence of intermediaries such as proxies. This document defines how to use OSCORE for protecting CoAP messages also between an origin application endpoint and an intermediary, or between two intermediaries. Also, it defines rules to escalate the protection of a CoAP option, in order to encrypt and integrity-protect it whenever possible. Finally, it defines how to secure a CoAP message by applying multiple, nested OSCORE protections, e.g., both end-to-end between origin application endpoints, as well as between an application endpoint and an intermediary or between two intermediaries. Thus, this document updates RFC 8613. The same approach can be seamlessly used with Group OSCORE, for protecting CoAP messages when group communication is used in the presence of intermediaries. 
     " name="description">
 <meta content="xml2rfc 3.19.1" name="generator">
 <meta content="Internet-Draft" name="keyword">
@@ -1068,7 +1068,7 @@
 <h1 id="title">OSCORE-capable Proxies</h1>
 <section id="section-abstract">
       <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
-<p id="section-abstract-1">Object Security for Constrained RESTful Environments (OSCORE) can be used to protect CoAP messages end-to-end between two endpoints at the application layer, also in the presence of intermediaries such as proxies. This document defines how to use OSCORE for protecting CoAP messages also between an origin application endpoint and an intermediary, or between two intermediaries. Also, it defines rules to selectively escalate the protection of a CoAP option, in order to encrypt and integrity-protect it whenever possible. Finally, it defines how to secure a CoAP message by applying multiple, nested OSCORE protections, e.g., both end-to-end between origin application endpoints, as well as between an application endpoint and an intermediary or between two intermediaries. Thus, this document updates RFC 8613. The same approach can be seamlessly used with Group OSCORE, for protecting CoAP messages when group communication is used in the presence of intermediaries.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
+<p id="section-abstract-1">Object Security for Constrained RESTful Environments (OSCORE) can be used to protect CoAP messages end-to-end between two endpoints at the application layer, also in the presence of intermediaries such as proxies. This document defines how to use OSCORE for protecting CoAP messages also between an origin application endpoint and an intermediary, or between two intermediaries. Also, it defines rules to escalate the protection of a CoAP option, in order to encrypt and integrity-protect it whenever possible. Finally, it defines how to secure a CoAP message by applying multiple, nested OSCORE protections, e.g., both end-to-end between origin application endpoints, as well as between an application endpoint and an intermediary or between two intermediaries. Thus, this document updates RFC 8613. The same approach can be seamlessly used with Group OSCORE, for protecting CoAP messages when group communication is used in the presence of intermediaries.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
 </section>
 <section class="note rfcEditorRemove" id="section-note.1">
       <h2 id="name-discussion-venues">
diff --git a/draft-ietf-core-oscore-capable-proxies.txt b/draft-ietf-core-oscore-capable-proxies.txt
index 9fe48ac..38d5638 100644
--- a/draft-ietf-core-oscore-capable-proxies.txt
+++ b/draft-ietf-core-oscore-capable-proxies.txt
@@ -20,10 +20,10 @@ Abstract
    proxies.  This document defines how to use OSCORE for protecting CoAP
    messages also between an origin application endpoint and an
    intermediary, or between two intermediaries.  Also, it defines rules
-   to selectively escalate the protection of a CoAP option, in order to
-   encrypt and integrity-protect it whenever possible.  Finally, it
-   defines how to secure a CoAP message by applying multiple, nested
-   OSCORE protections, e.g., both end-to-end between origin application
+   to escalate the protection of a CoAP option, in order to encrypt and
+   integrity-protect it whenever possible.  Finally, it defines how to
+   secure a CoAP message by applying multiple, nested OSCORE
+   protections, e.g., both end-to-end between origin application
    endpoints, as well as between an application endpoint and an
    intermediary or between two intermediaries.  Thus, this document
    updates RFC 8613.  The same approach can be seamlessly used with