Update the specs submodule, move clients that only implement +draft/channel-context to partial support. (#618)

* channel-context ratified
* oper-tag added
* Updates to account-registration, metadata, chathistory, network-icon, standard-replies

Author: sadiepowell

_data/irc_versions.yml

@@ -204,7 +204,15 @@ stable:
       link: /specs/extensions/whox.html
       isupport:
         - WHOX
-      
+
+    channel-context-client-tag:
+      name: +channel-context
+      description: Channel context client tag
+      link: /specs/client-tags/channel-context.html
+      hide-if-no-support: true
+      tags:
+        - +channel-context
+
     reply-client-tag:
       name: +reply
       description: Reply client tag
@@ -307,14 +315,6 @@ stable:
       caps:
         - draft/read-marker
 
-    channel-context-client-tag:
-      name: +draft/channel-context
-      description: Channel context client tag DRAFT
-      link: /specs/client-tags/channel-context.html
-      draft: true
-      tags:
-        - +draft/channel-context
-
     react-client-tag:
       name: +draft/react
       description: React and unreact client tags DRAFT
@@ -324,6 +324,16 @@ stable:
         - +draft/react
         - +draft/unreact
 
+    oper-tag:
+      name: draft/oper-tag
+      description: oper-tag Extension DRAFT
+      link: /specs/extensions/oper-tag.html
+      draft: true
+      caps:
+        - draft/oper-tag
+      tags:
+        - draft/oper
+
 proposed:
   name: Proposed Pull Requests
   specs: {}

_data/registry.yml

@@ -327,6 +327,10 @@
       specs:
         - channel-context-client-tag
       description: Indicates the channel a private message should be displayed in.
+    - name: draft/oper
+      specs:
+        - oper-tag
+      description: Indicates that the source of the message is an IRC operator.
 
 - name: Batches
   include_numeric: false

_data/sw_clients.yml

@@ -436,7 +436,6 @@
           cap-notify:
           cap-3.1:
           cap-3.2:
-          channel-context-client-tag:
           chathistory:
           echo-message:
           extended-monitor:
@@ -452,6 +451,9 @@
           standard-replies:
           typing-client-tag:
           whox:
+      partial:
+        stable:
+          channel-context-client-tag: "draft cap"
         SASL:
           plain:
     - name: Srain
@@ -581,7 +583,6 @@
           cap-notify:
           chghost:
           account-registration:
-          channel-context-client-tag:
           chathistory:
           echo-message:
           extended-join:
@@ -598,6 +599,9 @@
           server-time:
           setname:
           whox:
+      partial:
+        stable:
+          channel-context-client-tag: "draft cap"
         SASL:
           - plain
           - oauthbearer
@@ -615,7 +619,6 @@
           cap-3.1:
           cap-3.2:
           channel-rename:
-          channel-context-client-tag:
           chghost:
           echo-message:
           extended-join:
@@ -641,6 +644,9 @@
           react-client-tag:
           reply-client-tag:
           typing-client-tag:
+      partial:
+        stable:
+          channel-context-client-tag: "draft cap"
         SASL:
           - plain
           - scram-sha-256
@@ -1004,14 +1010,14 @@
           server-time:
           setname:
           whox:
-          channel-context-client-tag:
           react-client-tag:
           typing-client-tag:
           reply-client-tag:
         SASL:
           - plain
       partial:
         stable:
+          channel-context-client-tag: "draft cap"
           no-implicit-names: "draft cap"
 
 - name: Bouncers
@@ -1372,7 +1378,6 @@
           cap-3.1:
           cap-3.2:
           cap-notify:
-          channel-context-client-tag:
           chghost:
           echo-message:
           extended-join:
@@ -1401,6 +1406,7 @@
             - scram-sha-256
       partial:
         stable:
+          channel-context-client-tag: "draft cap"
           reply-client-tag: "draft cap"
     - name: Moon Moon
       # ref: https://github.com/wiseguiz/Moon-Moon/blob/master/irc.moon

_irc/index.md

@@ -222,7 +222,7 @@ and as such we detail them in their own section here.
 
 Here are the client-only tags the IRCv3 WG defines:
 
-* [The `channel-context` client-only tag]({{site.baseurl}}/specs/client-tags/channel-context.html) **[draft]** indicates the channel a private message should be displayed in.
+* [The `channel-context` client-only tag]({{site.baseurl}}/specs/client-tags/channel-context.html) indicates the channel a private message should be displayed in.
 * [The `reply` client-only tag]({{site.baseurl}}/specs/client-tags/reply.html) marks that a given message is intended as a reply to a specific sent message.
 * [The `react` client-only tag]({{site.baseurl}}/specs/client-tags/react.html) **[draft]** sends a reaction to a specific sent message, allowing such functionality from other chat systems.
 * [The `typing` client-only tag]({{site.baseurl}}/specs/client-tags/typing.html) lets users know when another user is typing a message in their channel or private message.
@@ -302,6 +302,10 @@ allows clients to disable the implicit `NAMES` responses sent after `JOIN` in
 case they don't always need that information for all channels. Clients can
 still query that information as needed via the `NAMES` or `WHO` command.
 
+The **work-in-progress** [`oper-tag` spec]({{site.baseurl}}/specs/extensions/oper-tag.html)
+defines a way for clients to receive a message tag on messages specifying that
+the source of the message is from an IRC operator. This is useful for letting
+users know that a message is from a trusted source.
 
 ## [Message IDs]({{site.baseurl}}/specs/extensions/message-ids.html)
 

docs/sasl-mechs.md

@@ -8,6 +8,7 @@ page-header: >
 IRC SASL authentication primarily uses the same mechanisms as SASL in other protocols. Most commonly:
 
 * [PLAIN](https://tools.ietf.org/html/rfc4616) as defined by RFC 4616
+* [OAUTHBEARER](https://tools.ietf.org/html/rfc7628) as defined by RFC 7628
 * [EXTERNAL](https://tools.ietf.org/html/rfc4422#appendix-A) as defined by RFC 4422
 * [SCRAM-SHA-256](https://tools.ietf.org/html/rfc7677) as defined by RFC 7677