From 5c1fb50ebb4dbe3eb63369ef269898caf2694b24 Mon Sep 17 00:00:00 2001 From: Sean Turner Date: Fri, 29 Mar 2024 11:46:48 -0400 Subject: [PATCH] Update 6125bis ref RFC 9525 is now published. --- 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..a01dd3a0 100644 --- a/draft-ietf-tls-rfc8446bis.md +++ b/draft-ietf-tls-rfc8446bis.md @@ -464,7 +464,7 @@ certificates exchanged are left to the judgment of the designers and implementors of protocols that run on top of TLS. Application protocols using TLS MUST specify how TLS works with their application protocol, including how and when handshaking -occurs, and how to do identity verification. {{?I-D.ietf-uta-rfc6125bis}} +occurs, and how to do identity verification. {{?RFC9525}} provides useful guidance on integrating TLS with application protocols. @@ -6143,7 +6143,7 @@ Since -05 - close_notify should be warning (PR 1290) - Reference RFC 8773 (PR 1296) - Add some more information about application bindings and cite - 6125-bis (PR 1297) + RFC 9525 (PR 1297) Since -04