From f169d38fddb9ce9546674c9467a232ef0abb08d7 Mon Sep 17 00:00:00 2001 From: Mike Bishop Date: Tue, 29 May 2018 10:40:37 -0700 Subject: [PATCH] Encourage kramdown to use brackets --- draft-ietf-httpbis-http2-secondary-certs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-httpbis-http2-secondary-certs.md b/draft-ietf-httpbis-http2-secondary-certs.md index 211a80e0c..32308be56 100644 --- a/draft-ietf-httpbis-http2-secondary-certs.md +++ b/draft-ietf-httpbis-http2-secondary-certs.md @@ -66,7 +66,7 @@ code and issues list for this draft can be found at HTTP clients need to know that the content they receive on a connection comes from the origin that they intended to retrieve in from. The traditional form of server authentication in HTTP has been in the form of a single X.509 certificate -provided during the TLS [RFC5246][I-D.ietf-tls-tls13] handshake. +provided during the TLS ([RFC5246], [I-D.ietf-tls-tls13]) handshake. Many existing HTTP [RFC7230] servers also have authentication requirements for the resources they serve. Of the bountiful authentication options available for