Thanks to everyone who provided feedback on this document.

This will be my final RFC. [1] It was a pleasure working with you all.

Peter

[1] https://stpeter.im/journal/1829.html

On 11/8/23 5:45 AM, rfc-edi...@rfc-editor.org wrote:
A new Request for Comments is now available in online RFC libraries.

RFC 9525

         Title:      Service Identity in TLS
         Author:     P. Saint-Andre,
                     R. Salz
         Status:     Standards Track
         Stream:     IETF
         Date:       November 2023
         Mailbox:    stpe...@stpeter.im,
                     rs...@akamai.com
         Pages:      25
         Obsoletes:  RFC 6125

         I-D Tag:    draft-ietf-uta-rfc6125bis-15.txt

         URL:        https://www.rfc-editor.org/info/rfc9525

         DOI:        10.17487/RFC9525

Many application technologies enable secure communication between two
entities by means of Transport Layer Security (TLS) with Internet
Public Key Infrastructure using X.509 (PKIX) certificates. This
document specifies procedures for representing and verifying the
identity of application services in such interactions.

This document obsoletes RFC 6125.

This document is a product of the Using TLS in Applications Working Group of 
the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
   https://www.ietf.org/mailman/listinfo/ietf-announce
   https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
Uta mailing list
Uta@ietf.org
https://www.ietf.org/mailman/listinfo/uta

_______________________________________________
Uta mailing list
Uta@ietf.org
https://www.ietf.org/mailman/listinfo/uta

Reply via email to