From c2f6f8d8b81764c7bbeca4230a7174acb6c2f8a6 Mon Sep 17 00:00:00 2001 From: ID Bot Date: Mon, 10 Feb 2025 08:57:42 +0000 Subject: [PATCH] Script updating gh-pages from 5ff3d56. [ci skip] --- carsten-wglc-2/draft-ietf-core-groupcomm-bis.html | 2 +- carsten-wglc-2/draft-ietf-core-groupcomm-bis.txt | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/carsten-wglc-2/draft-ietf-core-groupcomm-bis.html b/carsten-wglc-2/draft-ietf-core-groupcomm-bis.html index 1b02770..54948f0 100644 --- a/carsten-wglc-2/draft-ietf-core-groupcomm-bis.html +++ b/carsten-wglc-2/draft-ietf-core-groupcomm-bis.html @@ -2218,7 +2218,7 @@

A server endpoint MUST process an ETag Option in a GET or FETCH group request in the same way it processes an ETag Option for a unicast request. A server endpoint that includes an ETag Option in a response to a group request SHOULD construct the ETag Option value in such a way that the value will be unique to this particular server with a high probability. This practically prevents a collision of the ETag values from different servers in the same CoAP group and application group, which in turn allows the client to effectively validate a particular response of an origin server. This can be accomplished, for example, by embedding a compact ID (or hash) of the server within the ETag value, where the ID is unique (or unique with a high probability) in the scope of the CoAP/application groups.

-

Note: a CoAP server implementation that is unaware of the updates to [RFC7252] made by this document will expect group requests to never contain an ETag Option (see Section 8.2.1 of [RFC7252]). Such a server treats an ETag Option in a group request as an unrecognized option per Sections 5.4 and 8.2.1 of [RFC7252], causing it to ignore this (elective) ETag Option regardless of its value, and process the request normally as if that ETag Option was not included.

+

Note: a CoAP server implementation that is unaware of the updates to [RFC7252] made by this document will expect group requests to never contain an ETag Option (see Section 8.2.1 of [RFC7252]). Such a server treats an ETag Option in a group request as an unrecognized option per Sections 5.4 and 8.2.1 of [RFC7252], causing it to ignore this (elective) ETag Option regardless of its value, and processes the request normally as if that ETag Option was not included.

diff --git a/carsten-wglc-2/draft-ietf-core-groupcomm-bis.txt b/carsten-wglc-2/draft-ietf-core-groupcomm-bis.txt index 2f566fc..2807b6e 100644 --- a/carsten-wglc-2/draft-ietf-core-groupcomm-bis.txt +++ b/carsten-wglc-2/draft-ietf-core-groupcomm-bis.txt @@ -1361,8 +1361,8 @@ Table of Contents contain an ETag Option (see Section 8.2.1 of [RFC7252]). Such a server treats an ETag Option in a group request as an unrecognized option per Sections 5.4 and 8.2.1 of [RFC7252], causing it to ignore - this (elective) ETag Option regardless of its value, and process the - request normally as if that ETag Option was not included. + this (elective) ETag Option regardless of its value, and processes + the request normally as if that ETag Option was not included. 3.3. URI Path Selection