[Uta] RFC 9525 on Service Identity in TLS
rfc-editor@rfc-editor.org Wed, 08 November 2023 12:45 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: uta@ietfa.amsl.com
Delivered-To: uta@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5DC8C151996; Wed, 8 Nov 2023 04:45:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.467
X-Spam-Level:
X-Spam-Status: No, score=-4.467 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h0P08t-wcQUd; Wed, 8 Nov 2023 04:45:38 -0800 (PST)
Received: from rfcpa.amsl.com (unknown [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41509C151557; Wed, 8 Nov 2023 04:45:19 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id E9BD2119CD; Wed, 8 Nov 2023 04:45:18 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, uta@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20231108124518.E9BD2119CD@rfcpa.amsl.com>
Date: Wed, 08 Nov 2023 04:45:18 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/uta/eya2pqroiW8ztb1ymlhqePoj-Vw>
Subject: [Uta] RFC 9525 on Service Identity in TLS
X-BeenThere: uta@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: UTA working group mailing list <uta.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uta>, <mailto:uta-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uta/>
List-Post: <mailto:uta@ietf.org>
List-Help: <mailto:uta-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uta>, <mailto:uta-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Nov 2023 12:45:41 -0000
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: stpeter@stpeter.im,
rsalz@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-editor@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] RFC 9525 on Service Identity in TLS rfc-editor
- Re: [Uta] RFC 9525 on Service Identity in TLS Peter Saint-Andre
- Re: [Uta] RFC 9525 on Service Identity in TLS Valery Smyslov
- Re: [Uta] RFC 9525 on Service Identity in TLS Sean Turner