Script updating gh-pages from da59b93. [ci skip]

zaheduzzaman-sarker-review/draft-ietf-ace-key-groupcomm.html

@@ -1551,7 +1551,7 @@ <h3 id="name-terminology">
             <p id="section-1.1-9.3.1">Authentication credential, as the set of information associated with an entity, including that entity's public key and parameters associated with the public key. Examples of authentication credentials are CBOR Web Tokens (CWTs) and CWT Claims Sets (CCSs) <span>[<a href="#RFC8392" class="cite xref">RFC8392</a>]</span>, X.509 certificates <span>[<a href="#RFC5280" class="cite xref">RFC5280</a>]</span>, and C509 certificates <span>[<a href="#I-D.ietf-cose-cbor-encoded-cert" class="cite xref">I-D.ietf-cose-cbor-encoded-cert</a>]</span>.<a href="#section-1.1-9.3.1" class="pilcrow">¶</a></p>
 </li>
           <li class="normal" id="section-1.1-9.4">
-            <p id="section-1.1-9.4.1">Individual keying material: information exclusively pertaining to a group member, as associated with its group membership and related to other keying material and parameters used in the group. For example, this can be a member identifier that is unique within the group. The specific nature and format of individual keying material used in a group is defined in application profiles of this specification. The individual keying material of a group member is not related to the secure association between that group member and the KDC.<a href="#section-1.1-9.4.1" class="pilcrow">¶</a></p>
+            <p id="section-1.1-9.4.1">Individual keying material: information exclusively pertaining to a group member, as associated with its group membership and related to other keying material and parameters used in the group. For example, this can be an identifier that the secure communication protocol employs to uniquely identify a node as a group member (e.g., a cryptographic key identifier uniquely associated with the group member in question). The specific nature and format of individual keying material used in a group is defined in application profiles of this specification. The individual keying material of a group member is not related to the secure association between that group member and the KDC.<a href="#section-1.1-9.4.1" class="pilcrow">¶</a></p>
 </li>
         </ul>
 <p id="section-1.1-10">Examples throughout this document are expressed in CBOR diagnostic notation without the tag and value abbreviations.<a href="#section-1.1-10" class="pilcrow">¶</a></p>

zaheduzzaman-sarker-review/draft-ietf-ace-key-groupcomm.txt

@@ -320,12 +320,14 @@ Table of Contents
    *  Individual keying material: information exclusively pertaining to
       a group member, as associated with its group membership and
       related to other keying material and parameters used in the group.
-      For example, this can be a member identifier that is unique within
-      the group.  The specific nature and format of individual keying
-      material used in a group is defined in application profiles of
-      this specification.  The individual keying material of a group
-      member is not related to the secure association between that group
-      member and the KDC.
+      For example, this can be an identifier that the secure
+      communication protocol employs to uniquely identify a node as a
+      group member (e.g., a cryptographic key identifier uniquely
+      associated with the group member in question).  The specific
+      nature and format of individual keying material used in a group is
+      defined in application profiles of this specification.  The
+      individual keying material of a group member is not related to the
+      secure association between that group member and the KDC.
 
    Examples throughout this document are expressed in CBOR diagnostic
    notation without the tag and value abbreviations.