From 4587d97861b3437ef9cc46c6bdb69c5711085173 Mon Sep 17 00:00:00 2001 From: Sean Turner Date: Fri, 29 Mar 2024 11:50:39 -0400 Subject: [PATCH] Update HTTP/1.1 ref RFC 7230 was obsoleted by 9112. Not entirely sure we need to do this but it will get rid of one more IDnit. --- draft-ietf-tls-rfc8446bis.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/draft-ietf-tls-rfc8446bis.md b/draft-ietf-tls-rfc8446bis.md index c67cfb4e..31fb0013 100644 --- a/draft-ietf-tls-rfc8446bis.md +++ b/draft-ietf-tls-rfc8446bis.md @@ -77,7 +77,6 @@ informative: RFC6091: RFC6520: RFC8305: - RFC7230: RFC7250: RFC7465: RFC7568: @@ -87,6 +86,7 @@ informative: RFC8849: RFC9345: RFC8870: + RFC9112: RFC9162: RFC9146: RFC8844: @@ -5327,7 +5327,7 @@ Clients SHOULD NOT reuse a ticket for multiple connections. Reuse of a ticket allows passive observers to correlate different connections. Servers that issue tickets SHOULD offer at least as many tickets as the number of connections that a client might use; for example, a web browser -using HTTP/1.1 {{RFC7230}} might open six connections to a server. Servers SHOULD +using HTTP/1.1 {{RFC9112}} might open six connections to a server. Servers SHOULD issue new tickets with every connection. This ensures that clients are always able to use a new ticket when creating a new connection.