{"component": "clause", "props": {"groups": [{"snippet": "Tree T5 Tree T5 <0,0> <0,0> <1,0> <1,1> <1,0> <1,1> <2,0> <2,1> <2,2> <2,3> M3 <3,6> <3,7> <2,0> <2,1> <2,2> <2,3> M1 M2 M1 M2 M4 M5 M4 M5 Sponsor", "snippet_links": [], "samples": [{"hash": "gZ6qwGPKdDq", "uri": "/contracts/gZ6qwGPKdDq#leave-protocol", "label": "Group Key Agreement", "score": 25.3696098563, "published": true}, {"hash": "j8rFjDb8v8s", "uri": "/contracts/j8rFjDb8v8s#leave-protocol", "label": "Group Key Agreement", "score": 19.0, "published": true}], "size": 3, "hash": "ea5a760e706c334c8540efb01056398c", "id": 1}, {"snippet": "^ Such as Join protocol, we start with n members and assume that member Md leaves the group. The sponsor in this case is the rightmost leaf node of the subtree rooted at leaving member\u2019s sibling node. First, if the number of leaving member\u2019s sibling node is two, each member updates its key tree by deleting the leaf node corresponding to Md. Then the former sibling of Md is updated to replace Md\u2019s parent node. Otherwise each member only deleting the leaf node corresponding to Md. The sponsor generates a new key share, computes all [key, bkey] pairs on the key-path up to the root, and broadcasts the new set of bkey. This allows all members to compute the new group key. In Fig. 3, if member M7 leaves the group, every remaining member deletes < 1, 2 > and < 2, 6 >. After updating the tree, the sponsor (M10) picks a new share K<2,8>, recomputes \u2587<\u2587,\u2587>, \u2587<\u2587,\u2587>, \u2587\u2587<\u2587,\u2587> and BK<1,2>, and broadcasts the updated tree T10 with BK1\u22170. Upon receiving the broadcast message, all members compute the group key. Note that M7 cannot compute the group key, though he knows all the bkeys, because his share is no longer a part of the group key.", "snippet_links": [{"key": "join-protocol", "type": "clause", "offset": [10, 23]}, {"key": "the-group", "type": "clause", "offset": [82, 91]}, {"key": "the-sponsor", "type": "clause", "offset": [93, 104]}, {"key": "number-of", "type": "clause", "offset": [215, 224]}, {"key": "each-member", "type": "definition", "offset": [263, 274]}, {"key": "all-members", "type": "definition", "offset": [634, 645]}, {"key": "new-group", "type": "definition", "offset": [661, 670]}, {"key": "remaining-member", "type": "definition", "offset": [724, 740]}, {"key": "new-share", "type": "definition", "offset": [823, 832]}, {"key": "upon-receiving", "type": "clause", "offset": [937, 951]}], "samples": [{"hash": "bATtEI7gCxO", "uri": "/contracts/bATtEI7gCxO#leave-protocol", "label": "Group Key Agreement", "score": 19.0, "published": true}], "size": 3, "hash": "728a6e773e3733cb6689950c349314fd", "id": 2}, {"snippet": "Employees will obtain testing following the most current DOH recommendations in such situations and will share the results with the District immediately upon receipt. The District has a right to investigate suspected misuse of this leave.", "snippet_links": [{"key": "employees-will", "type": "clause", "offset": [0, 14]}, {"key": "the-most-current", "type": "definition", "offset": [40, 56]}, {"key": "the-district", "type": "clause", "offset": [128, 140]}, {"key": "immediately-upon-receipt", "type": "clause", "offset": [141, 165]}, {"key": "right-to-investigate", "type": "clause", "offset": [186, 206]}], "samples": [{"hash": "jaC2RGtEM51", "uri": "/contracts/jaC2RGtEM51#leave-protocol", "label": "Collective Bargaining Agreement", "score": 31.3093186709, "published": true}, {"hash": "91FYKpKOoWS", "uri": "/contracts/91FYKpKOoWS#leave-protocol", "label": "Collective Bargaining Agreement", "score": 25.3203285421, "published": true}], "size": 2, "hash": "9dcc4ba585d0318caf4016507122324b", "id": 3}, {"snippet": "Once again, we start with members and assume that member leaves the group. The sponsor in this case is the rightmost leaf node of the subtree rooted at the leaving member\u2019s sibling node. First off, as shown in Figure 4, each member updates its key tree by deleting the leaf node corresponding to . The former sibling of is promoted to replace \u2019s parent node. The sponsor generates a new key share, computes all pairs on the key-path up to the root, and broadcasts the new set of bkeys. This allows all members to compute the new group key. , and broadcasts the updated tree with . Upon receiving the broadcast message, all members compute the group key. Note that cannot compute the group key, though it knows all the bkeys, because its share is no longer part of the group key. One round and one message are required to complete a leave protocol. The number of modular exponentiation depends on the location of the leaving member and tree structure. Its upper bound is if all pairs on the key-path of the deepest node need to be recomputed. When either left or right subtree has single node and it is the sponsor (i.e. for example, its sibling leaves the group), 3 modular exponentiations are required (two by the sponsor and one by all other members).", "snippet_links": [{"key": "the-group", "type": "clause", "offset": [64, 73]}, {"key": "the-sponsor", "type": "clause", "offset": [75, 86]}, {"key": "as-shown", "type": "definition", "offset": [198, 206]}, {"key": "figure-4", "type": "definition", "offset": [210, 218]}, {"key": "each-member", "type": "definition", "offset": [220, 231]}, {"key": "all-members", "type": "definition", "offset": [498, 509]}, {"key": "new-group", "type": "definition", "offset": [525, 534]}, {"key": "upon-receiving", "type": "clause", "offset": [581, 595]}, {"key": "number-of", "type": "clause", "offset": [852, 861]}, {"key": "location-of", "type": "definition", "offset": [900, 911]}, {"key": "upper-bound", "type": "definition", "offset": [955, 966]}, {"key": "for-example", "type": "definition", "offset": [1120, 1131]}, {"key": "all-other-members", "type": "clause", "offset": [1234, 1251]}], "samples": [{"hash": "gZ6qwGPKdDq", "uri": "/contracts/gZ6qwGPKdDq#leave-protocol", "label": "Group Key Agreement", "score": 25.3696098563, "published": true}, {"hash": "j8rFjDb8v8s", "uri": "/contracts/j8rFjDb8v8s#leave-protocol", "label": "Group Key Agreement", "score": 19.0, "published": true}], "size": 2, "hash": "bf60c7a0293a7241cabe4a9f47f93e3d", "id": 4}, {"snippet": "Assume that a member ML wishes to leave a n-member group. First ML initiates the leave protocol by sending a leave request. When the other group members receive the request, they independently determine the sponsor node, which is defined as in [1] to be the right-most leaf node of the subtree rooted at the leaving member\u2019s sibling node. The leave protocol works as shown in Algorithm 2. Algorithm 2 Leave Protocol in AFTD", "snippet_links": [{"key": "a-member", "type": "clause", "offset": [12, 20]}, {"key": "member-group", "type": "definition", "offset": [44, 56]}, {"key": "leave-request", "type": "clause", "offset": [109, 122]}, {"key": "group-members", "type": "clause", "offset": [139, 152]}, {"key": "the-request", "type": "clause", "offset": [161, 172]}, {"key": "the-sponsor", "type": "clause", "offset": [203, 214]}, {"key": "the-right", "type": "clause", "offset": [254, 263]}, {"key": "as-shown", "type": "definition", "offset": [364, 372]}], "samples": [{"hash": "gZOELLyw0wi", "uri": "/contracts/gZOELLyw0wi#leave-protocol", "label": "Key Agreement Protocol", "score": 19.0, "published": true}], "size": 2, "hash": "c8c0c7e4fc6c30d11ed7f35b4546dfbf", "id": 5}, {"snippet": "Step 1: Each sponsor Msi in Tsi for i \u2208 [1, k] \u2022 broadcasts tree BT(si \u27e9 BT\u27e8s \u27e9 k Msi i \u2212\u2192 \u222ai=1 Ci Step 2: Each member \u2022 updates key tree by merging all trees, \u2022 removes all keys and bkeys from the sponsor node, The sponsor Ms (additionally) \u2022 generates new share rs and computes brs, \u2022 computes all keys and bkeys from its parent to the node just below root, \u2022 broadcasts updated tree BT(s\u27e9 k BT\u27e8s\u27e9 M \u222ai=1 Ci \u2190 \u2212 s Step 3: Each member computes group key using BT(s\u27e9 c.", "snippet_links": [{"key": "step-1", "type": "clause", "offset": [0, 6]}, {"key": "step-2", "type": "definition", "offset": [99, 105]}, {"key": "each-member", "type": "definition", "offset": [107, 118]}, {"key": "the-sponsor", "type": "clause", "offset": [194, 205]}, {"key": "new-share", "type": "definition", "offset": [254, 263]}, {"key": "step-3", "type": "clause", "offset": [416, 422]}], "samples": [{"hash": "eCfUwSez7OD", "uri": "/contracts/eCfUwSez7OD#leave-protocol", "label": "Group Key Agreement", "score": 25.2600958248, "published": true}], "size": 1, "hash": "e3c8670bd0ddf30c172551ea93cdfe17", "id": 6}, {"snippet": "The leave protocol is relatively simple. Assume that it has a group of n members and member Ml leaves the group. The rightmost leaf node of Ml\u2019s sibling subtree is selected as the sponsor. After notification from system about the leave event, each remaining member updates its key tree by deleting Ml. The former sibling of Md is promoted to replace Md\u2019s parent node. The sponsor must additionally refresh keys in its key-path. The process of leave protocol is illustrated as follows:\n1) Each member removes the leaving member and relevant parent node, removes all keys and blinded keys pairs from sponsor to root node. The Sponsor Ms additionally, updates its share, computes then all keys and blinded keys in its key-path, and broadcasts updated key tree including all blinded keys.\n2) Every member computes the group key using new key tree.", "snippet_links": [{"key": "the-group", "type": "clause", "offset": [102, 111]}, {"key": "the-sponsor", "type": "clause", "offset": [176, 187]}, {"key": "after-notification", "type": "clause", "offset": [189, 207]}, {"key": "remaining-member", "type": "definition", "offset": [248, 264]}, {"key": "the-process", "type": "clause", "offset": [428, 439]}, {"key": "each-member", "type": "definition", "offset": [488, 499]}], "samples": [{"hash": "lwqibfPc9IB", "uri": "/contracts/lwqibfPc9IB#leave-protocol", "label": "Dissertation", "score": 20.4042695686, "published": true}], "size": 1, "hash": "5b2a2d6984ff689df5863ed580ff92d5", "id": 7}, {"snippet": "The leave protocol in CLIQUES is relatively simple. It needs only one round. Let Mc be group controller, and Ml be the member which leaves the group. First, Mc updates its secret Sc. Mc constructs then a broadcast message by embedding its new secret. Finally Mc broadcasts the message to the group. After running leave protocol, all remaining members compute the new group key. Although the contribution Sl is still factored into the new group key, the left member \u2587\u2587 is unable ScS1S2\u2219\u2219\u2219Sn to compute the new group key, due to the absence of the subkey g Sl .", "snippet_links": [{"key": "group-controller", "type": "definition", "offset": [87, 103]}, {"key": "the-member", "type": "clause", "offset": [115, 125]}, {"key": "the-group", "type": "clause", "offset": [139, 148]}, {"key": "remaining-members", "type": "definition", "offset": [333, 350]}, {"key": "new-group", "type": "definition", "offset": [363, 372]}, {"key": "the-contribution", "type": "clause", "offset": [387, 403]}], "samples": [{"hash": "lwqibfPc9IB", "uri": "/contracts/lwqibfPc9IB#leave-protocol", "label": "Dissertation", "score": 20.4042695686, "published": true}], "size": 1, "hash": "6ac4743dff960d085f7f2eda50c4b904", "id": 8}, {"snippet": "Authenticated key tree that M3 receives from director, M2", "snippet_links": [], "samples": [{"hash": "lwqibfPc9IB", "uri": "/contracts/lwqibfPc9IB#leave-protocol", "label": "Dissertation", "score": 20.4042695686, "published": true}], "size": 1, "hash": "3c98d0c1d03d079e02399742f30be738", "id": 9}, {"snippet": "The main security requirement of member leaving is the secrecy of the subsequent (future) group key with respect to both outsiders and former group members.\n1) When Mj wants to leave the group, intimates the GC and then GC, Ml generates a random number Rjj . Klj\n2) Ml sends \u03a3Rj x\u22121 \u03a3 P by encrypting with xK to the corresponding group member Mi, i = j, (i.e) except leaving member. However, it is often times necessary to either to add a Klj EK \u03a3Rt x\u22121 \u03a3P new member (or) delete an existing group member of the initial group creation. Naturally, it is desirable to do so without executing entire protocol a new. To address this issue we extend CGKA to DCGKA by proposing join pro-", "snippet_links": [{"key": "security-requirement", "type": "definition", "offset": [9, 29]}, {"key": "with-respect-to", "type": "clause", "offset": [100, 115]}, {"key": "group-members", "type": "clause", "offset": [142, 155]}, {"key": "the-group", "type": "clause", "offset": [183, 192]}, {"key": "corresponding-group", "type": "definition", "offset": [316, 335]}, {"key": "new-member", "type": "definition", "offset": [457, 467]}, {"key": "existing-group", "type": "definition", "offset": [483, 497]}, {"key": "member-of-the", "type": "clause", "offset": [498, 511]}], "samples": [{"hash": "gbNvrwDIzhZ", "uri": "/contracts/gbNvrwDIzhZ#leave-protocol", "label": "Contributory Group Key Agreement Protocol", "score": 22.6991993019, "published": true}], "size": 1, "hash": "31e296cd076b3c68b4d420e0591abe2e", "id": 10}], "next_curs": "ClcSUWoVc35sYXdpbnNpZGVyY29udHJhY3RzcjMLEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2IhdsZWF2ZS1wcm90b2NvbCMwMDAwMDAwYQyiAQJlbhgAIAA=", "clause": {"title": "Leave Protocol", "children": [], "size": 16, "parents": [["proposed-system", "PROPOSED SYSTEM"], ["cryptographic-properties", "Cryptographic Properties"], ["group", "\u2013 Group"], ["partition-protocol", "Partition Protocol"], ["concept-of-purposed-protocol", "Concept of Purposed Protocol"]], "id": "leave-protocol", "related": [["sick-leave-verification-process", "Sick Leave Verification Process", "Sick Leave Verification Process"], ["protocol", "Protocol", "Protocol"], ["access-control", "Access Control", "Access Control"], ["signaling-protocol", "Signaling protocol", "Signaling protocol"], ["system-access-control", "System Access Control", "System Access Control"]], "related_snippets": [], "updated": "2025-07-07T12:36:17+00:00"}, "json": true, "cursor": ""}}