Script updating gh-pages from 60d4ae5. [ci skip]

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

@@ -2476,7 +2476,7 @@ <h4 id="name-post-handler">
 When receiving the authentication credential of a Client in the 'client_cred' parameter of a Join Request (see <a href="#ssec-key-distribution-exchange" class="auto internal xref">Section 4.3.1.1</a>) or of an Authentication Credential Update Request (see <a href="#update-pub-key" class="auto internal xref">Section 4.9.1.1</a>), the KDC is not expected to check that the authentication credential indicates the role(s) that the Client can have or has in the group in question. When preparing a Join Response, the KDC can decide about including or not the 'peer_roles' parameter depending on the specific set of authentication credentials specified in the 'creds' parameter of that Join Response.<a href="#section-4.3.1-32.2.3" class="pilcrow">¶</a></p>
 </li>
             <li class="normal" id="section-4.3.1-32.3">
-              <p id="section-4.3.1-32.3.1">'peer_identifiers', MUST be present if 'creds' is also present, otherwise it MUST NOT be present. This parameter is a CBOR array of n elements, with n the number of authentication credentials included in the 'creds' parameter (at most the number of members in the group). The i-th element of the array specifies the node identifier that the group member associated with the i-th authentication credential in 'creds' has in the group. In particular, the i-th array element is encoded as a CBOR byte string, with value the node identifier of the group member.<a href="#section-4.3.1-32.3.1" class="pilcrow">¶</a></p>
+              <p id="section-4.3.1-32.3.1">'peer_identifiers', MUST be present if 'creds' is also present, otherwise it MUST NOT be present. This parameter is a CBOR array of n elements, with n the number of authentication credentials included in the 'creds' parameter (at most the number of members in the group). The i-th element of the array specifies the node identifier that the group member associated with the i-th authentication credential in 'creds' has in the group. In particular, the i-th array element is encoded as a CBOR byte string, with value the node identifier of the group member. The specific format of node identifiers of group members is specified by the application profile (REQ25).<a href="#section-4.3.1-32.3.1" class="pilcrow">¶</a></p>
 </li>
             <li class="normal" id="section-4.3.1-32.4">
               <p id="section-4.3.1-32.4.1">'group_policies', with value a CBOR map, whose entries specify how the group handles specific management aspects. These include, for instance, approaches to achieve synchronization of sequence numbers among group members. The elements of this field are registered in the "ACE Groupcomm Policies" registry. This specification defines the three elements "Sequence Number Synchronization Methods", "Key Update Check Interval", and "Expiration Delta", which are summarized in <a href="#fig-ACE-Groupcomm-Policies" class="auto internal xref">Figure 12</a>. Application profiles that build on this document MUST specify the exact content format and default value of included map entries (REQ20).<a href="#section-4.3.1-32.4.1" class="pilcrow">¶</a></p>
@@ -4684,7 +4684,7 @@ <h3 id="name-mandatory-to-address-requir">
             <p id="appendix-A.1-1.24.1">REQ24: Specify how the communication is secured between Client and KDC. Optionally, specify transport profile of ACE <span>[<a href="#RFC9200" class="cite xref">RFC9200</a>]</span> to use between Client and KDC (see <a href="#ssec-key-distribution-exchange" class="auto internal xref">Section 4.3.1.1</a>).<a href="#appendix-A.1-1.24.1" class="pilcrow">¶</a></p>
 </li>
           <li class="normal" id="appendix-A.1-1.25">
-            <p id="appendix-A.1-1.25.1">REQ25: Specify the format of the identifiers of group members (see <a href="#gid-post" class="auto internal xref">Section 4.3.1</a>).<a href="#appendix-A.1-1.25.1" class="pilcrow">¶</a></p>
+            <p id="appendix-A.1-1.25.1">REQ25: Specify the format of the identifiers of group members (see <a href="#gid-post" class="auto internal xref">Section 4.3.1</a> and <a href="#pubkey-fetch" class="auto internal xref">Section 4.4.1</a>).<a href="#appendix-A.1-1.25.1" class="pilcrow">¶</a></p>
 </li>
           <li class="normal" id="appendix-A.1-1.26">
             <p id="appendix-A.1-1.26.1">REQ26: Specify policies at the KDC to handle ids that are not included in 'get_creds' (see <a href="#pubkey-fetch" class="auto internal xref">Section 4.4.1</a>).<a href="#appendix-A.1-1.26.1" class="pilcrow">¶</a></p>

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

@@ -1761,7 +1761,9 @@ Table of Contents
       identifier that the group member associated with the i-th
       authentication credential in 'creds' has in the group.  In
       particular, the i-th array element is encoded as a CBOR byte
-      string, with value the node identifier of the group member.
+      string, with value the node identifier of the group member.  The
+      specific format of node identifiers of group members is specified
+      by the application profile (REQ25).
 
    *  'group_policies', with value a CBOR map, whose entries specify how
       the group handles specific management aspects.  These include, for
@@ -4811,7 +4813,7 @@ A.1.  Mandatory-to-Address Requirements
       use between Client and KDC (see Section 4.3.1.1).
 
    *  REQ25: Specify the format of the identifiers of group members (see
-      Section 4.3.1).
+      Section 4.3.1 and Section 4.4.1).
 
    *  REQ26: Specify policies at the KDC to handle ids that are not
       included in 'get_creds' (see Section 4.4.1).