Script updating gh-pages from 6652c59. [ci skip]

john-comments/draft-ietf-core-groupcomm-bis.html

@@ -1860,7 +1860,7 @@ <h5 id="name-coap-groups">
             <h5 id="name-application-groups">
 <a href="#section-2.2.1.2" class="section-number selfRef">2.2.1.2. </a><a href="#name-application-groups" class="section-name selfRef">Application Groups</a>
             </h5>
-<p id="section-2.2.1.2-1">An application group can be named in many ways through different types of identifiers, such as name string, (integer) number, URI, or other types of string. The decision of whether and how exactly an application group name is encoded and transported is application specific.<a href="#section-2.2.1.2-1" class="pilcrow">¶</a></p>
+<p id="section-2.2.1.2-1">An application group can be named in many ways through different types of identifiers, such as name string, (integer) number, URI, or other types of strings. The decision of whether and how exactly an application group name is encoded and transported is application specific.<a href="#section-2.2.1.2-1" class="pilcrow">¶</a></p>
 <p id="section-2.2.1.2-2">The following discusses a number of possible methods to use, while full examples for the different methods are provided in <a href="#sec-examples-app-group-naming" class="auto internal xref">Appendix B</a>.<a href="#section-2.2.1.2-2" class="pilcrow">¶</a></p>
 <p id="section-2.2.1.2-3">An application group name can be explicitly encoded in a group URI. In such a case, it can be encoded within one of the following URI components.<a href="#section-2.2.1.2-3" class="pilcrow">¶</a></p>
 <ul class="normal">
@@ -1929,7 +1929,7 @@ <h5 id="name-application-groups">
             <h5 id="name-security-groups">
 <a href="#section-2.2.1.3" class="section-number selfRef">2.2.1.3. </a><a href="#name-security-groups" class="section-name selfRef">Security Groups</a>
             </h5>
-<p id="section-2.2.1.3-1">A security group is identified by a stable and invariant string used as group name. This is generally not related to other kinds of group identifiers that may be specific of the used security solution.<a href="#section-2.2.1.3-1" class="pilcrow">¶</a></p>
+<p id="section-2.2.1.3-1">A security group can be named in many ways through different types of identifiers, such as name string, (integer) number, URI, or other types of strings. Such a group name is generally not related to other kinds of group identifiers that may be specific of the used security solution.<a href="#section-2.2.1.3-1" class="pilcrow">¶</a></p>
 <p id="section-2.2.1.3-2">The name of a security group is not expected to be used in messages exchanged among its members, unless the application requires otherwise. At the same time, it is useful to identify the security group when performing a number of side tasks related to secure group communication, such as the following ones.<a href="#section-2.2.1.3-2" class="pilcrow">¶</a></p>
 <ul class="normal">
 <li class="normal" id="section-2.2.1.3-3.1">
@@ -3839,10 +3839,13 @@ <h3 id="name-version-09-to-10">
             <p id="appendix-E.1-1.1.1">Use of .example for example hostnames.<a href="#appendix-E.1-1.1.1" class="pilcrow">¶</a></p>
 </li>
           <li class="normal" id="appendix-E.1-1.2">
-            <p id="appendix-E.1-1.2.1">Changed "has to" to "should" for enforcing access control based on membership to security groups.<a href="#appendix-E.1-1.2.1" class="pilcrow">¶</a></p>
+            <p id="appendix-E.1-1.2.1">The name of a security group is not necessarily a string.<a href="#appendix-E.1-1.2.1" class="pilcrow">¶</a></p>
 </li>
           <li class="normal" id="appendix-E.1-1.3">
-            <p id="appendix-E.1-1.3.1">Editorial fixes and improvements.<a href="#appendix-E.1-1.3.1" class="pilcrow">¶</a></p>
+            <p id="appendix-E.1-1.3.1">Changed "has to" to "should" for enforcing access control based on membership to security groups.<a href="#appendix-E.1-1.3.1" class="pilcrow">¶</a></p>
+</li>
+          <li class="normal" id="appendix-E.1-1.4">
+            <p id="appendix-E.1-1.4.1">Editorial fixes and improvements.<a href="#appendix-E.1-1.4.1" class="pilcrow">¶</a></p>
 </li>
         </ul>
 </section>

john-comments/draft-ietf-core-groupcomm-bis.txt

@@ -598,7 +598,7 @@ Table of Contents
 
    An application group can be named in many ways through different
    types of identifiers, such as name string, (integer) number, URI, or
-   other types of string.  The decision of whether and how exactly an
+   other types of strings.  The decision of whether and how exactly an
    application group name is encoded and transported is application
    specific.
 
@@ -719,9 +719,11 @@ Table of Contents
 
 2.2.1.3.  Security Groups
 
-   A security group is identified by a stable and invariant string used
-   as group name.  This is generally not related to other kinds of group
-   identifiers that may be specific of the used security solution.
+   A security group can be named in many ways through different types of
+   identifiers, such as name string, (integer) number, URI, or other
+   types of strings.  Such a group name is generally not related to
+   other kinds of group identifiers that may be specific of the used
+   security solution.
 
    The name of a security group is not expected to be used in messages
    exchanged among its members, unless the application requires
@@ -3790,6 +3792,8 @@ E.1.  Version -09 to -10
 
    *  Use of .example for example hostnames.
 
+   *  The name of a security group is not necessarily a string.
+
    *  Changed "has to" to "should" for enforcing access control based on
       membership to security groups.