From 5bb2003afc292a06e7831919702684561b75b681 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Lo=C3=AFc=20Hoguin?= <essen@ninenines.eu>
Date: Thu, 20 Jul 2017 18:30:17 +0200
Subject: Add a related RFC for Websocket

This is important because it clarifies that sec-websocket-protocol
is case sensitive when matching. Only the registry is case
insensitive.
---
 doc/src/guide/specs.asciidoc | 1 +
 1 file changed, 1 insertion(+)

(limited to 'doc/src/guide/specs.asciidoc')

diff --git a/doc/src/guide/specs.asciidoc b/doc/src/guide/specs.asciidoc
index 3bcd45e..db4abe4 100644
--- a/doc/src/guide/specs.asciidoc
+++ b/doc/src/guide/specs.asciidoc
@@ -80,6 +80,7 @@ for or related to HTTP.
 * https://tools.ietf.org/html/rfc7804[RFC 7804]: Salted Challenge Response HTTP Authentication Mechanism
 * https://tools.ietf.org/html/rfc7838[RFC 7838]: HTTP Alternative Services
 * https://tools.ietf.org/html/rfc7932[RFC 7932]: Brotli Compressed Data Format
+* https://tools.ietf.org/html/rfc7936[RFC 7936]: Clarifying Registry Procedures for the WebSocket Subprotocol Name Registry
 * https://tools.ietf.org/html/rfc8053[RFC 8053]: HTTP Authentication Extensions for Interactive Clients
 * https://tools.ietf.org/html/rfc8164[RFC 8164]: Opportunistic Security for HTTP/2
 * https://tools.ietf.org/html/rfc8188[RFC 8188]: Encrypted Content-Encoding for HTTP
-- 
cgit v1.2.3

