… Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)" [ RFC7525 ] for recommendations on improving the security of software and services using TLS. Whenever TLS is used, the identity of the service provider encoded in the TLS server certificate MUST be ver…

… Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)" [ RFC7525 ] for recommendations on improving the security of software and services using TLS. Whenever TLS is used, the identity of the service provider encoded in the TLS server certificate MUST be ver…

… Parties and Repository Servers follow the Best Current Practices outlined in [ RFC7525 ] on the use of HTTP over TLS (HTTPS) [ RFC7230 ]. Relying Parties SHOULD do TLS certificate and host name validation using subjectAltName dNSName identities as described in [ RFC6125 ]. The r…

… client with 'dns-01', etc. ACME servers SHOULD follow the recommendations of [ RFC7525 ] when configuring their TLS implementations. ACME servers that support TLS 1.3 MAY allow clients to send early data (0-RTT). This is safe because the ACME protocol itself includes anti-replay…

…raft-ietf-uta-rfc6125bis) Done Recommendations for Secure Use of TLS and DTLS ( rfc7525 -bis) to IETF LC rfc9325 (was draft-ietf-uta-rfc7525bis) Done Use of TLS for Email Submission and Access to IETF LC