From b8da1ca7b3f4db0d747a8906c1a33227478cac0d Mon Sep 17 00:00:00 2001 From: ID Bot Date: Wed, 13 Dec 2023 13:54:28 +0000 Subject: [PATCH] Script updating gh-pages from 1dddae5. [ci skip] --- index.html | 52 +++++++++---------- .../draft-ietf-ace-key-groupcomm.html | 2 +- .../draft-ietf-ace-key-groupcomm.txt | 2 +- 3 files changed, 28 insertions(+), 28 deletions(-) diff --git a/index.html b/index.html index 6a648fe..0ce45ea 100644 --- a/index.html +++ b/index.html @@ -24,20 +24,12 @@

Editor's drafts for master branch of roman-danyliw-review

- - - - - - -
Key Provisioning for Group Communicationplain textdiff with master
-

Preview for branch erik-kline-review

- +

Preview for branch zaheduzzaman-sarker-review

+
- - - + + +
Key Provisioning for Group Communicationplain textdiff with masterKey Provisioning for Group Communicationplain textdiff with master

Preview for branch warren-kumari-review

@@ -48,6 +40,22 @@

Preview for branch warren-kumari-reviewdiff with master +

Preview for branch iana-reviews

+ + + + + + +
Key Provisioning for Group Communicationplain textdiff with master
+

Preview for branch roman-danyliw-review

+ + + + + + +
Key Provisioning for Group Communicationplain textdiff with master

Preview for branch martin-duke-review

@@ -56,20 +64,12 @@

Preview for branch martin-duke-review

diff with master
-

Preview for branch zaheduzzaman-sarker-review

- - - - - - -
Key Provisioning for Group Communicationplain textdiff with master
-

Preview for branch iana-reviews

- +

Preview for branch erik-kline-review

+
- - - + + +
Key Provisioning for Group Communicationplain textdiff with masterKey Provisioning for Group Communicationplain textdiff with master

Preview for branch artart-review

diff --git a/warren-kumari-review/draft-ietf-ace-key-groupcomm.html b/warren-kumari-review/draft-ietf-ace-key-groupcomm.html index 7fadab3..e520344 100644 --- a/warren-kumari-review/draft-ietf-ace-key-groupcomm.html +++ b/warren-kumari-review/draft-ietf-ace-key-groupcomm.html @@ -1483,7 +1483,7 @@

Candidate group members acting as Clients and authorized to join a group can interact with the Key Distribution Center (KDC) acting as Resource Server and responsible for that group, in order to obtain the necessary keying material and parameters to communicate with other group members.

In particular, this document defines the operations and interface available at the KDC, as well as general message formats for the interactions between Clients and KDC. At the same time, communications in the group can rely on different approaches, e.g., based on multicast [I-D.ietf-core-groupcomm-bis] or on publish-subscribe messaging [I-D.ietf-core-coap-pubsub], and can be protected in different ways.

Therefore, this document delegates details on the communication and security approaches used in a group to separate application profiles. These are specialized instances of this document, targeting a particular group communication approach and defining how communications in the group are protected, as well as the specific keying material and configuration parameters provided to group members. In order to ensure consistency and aid the development of such application profiles, this document defines a number of related compliance requirements (see Appendix A).

-

New keying material is intended to be generated and distributed to the group upon membership changes (rekeying). If the application requires backward security (i.e., new group members must be prevented from accessing communications in the group prior to their joining), then a rekeying has to occur every time new members join the group. If the application requires forward security (i.e., former group members must be prevented from accessing communications in the group after their leaving), a rekeying has to occur every time current members leave the group or are evicted from the group.

+

New keying material is intended to be generated and distributed to the group upon membership changes (rekeying). If the application requires backward security (i.e., new group members must be prevented from accessing communications in the group prior to their joining), then a rekeying has to occur every time new members join the group. If the application requires forward security (i.e., former group members must be prevented from accessing communications in the group after their leaving), then a rekeying has to occur every time current members leave the group or are evicted from the group.

A group rekeying scheme performs the actual distribution of the new keying material, by rekeying the current group members when a new Client joins the group, and the remaining group members when a Client leaves the group. This can rely on different approaches, including efficient group rekeying schemes such as [RFC2093], [RFC2094], and [RFC2627].

Consistently with what is recommended in the ACE framework, this document uses CBOR [RFC8949] for data encoding. However, using JSON [RFC8259] instead of CBOR is possible, by relying on the conversion method specified in Sections 6.1 and 6.2 of [RFC8949].

diff --git a/warren-kumari-review/draft-ietf-ace-key-groupcomm.txt b/warren-kumari-review/draft-ietf-ace-key-groupcomm.txt index a07104d..7332fa3 100644 --- a/warren-kumari-review/draft-ietf-ace-key-groupcomm.txt +++ b/warren-kumari-review/draft-ietf-ace-key-groupcomm.txt @@ -204,7 +204,7 @@ Table of Contents then a rekeying has to occur every time new members join the group. If the application requires forward security (i.e., former group members must be prevented from accessing communications in the group - after their leaving), a rekeying has to occur every time current + after their leaving), then a rekeying has to occur every time current members leave the group or are evicted from the group. A group rekeying scheme performs the actual distribution of the new