IETF Logo Mail Archive

Re: [Uta] RFC 9525 on Service Identity in TLS

Valery Smyslov <valery@smyslov.net> Thu, 09 November 2023 07:47 UTC

Return-Path: <valery@smyslov.net>
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 3A2F9C151066 for <uta@ietfa.amsl.com>; Wed, 8 Nov 2023 23:47:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.807
X-Spam-Level:
X-Spam-Status: No, score=-2.807 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=smyslov.net
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 9k20lXa3RAQ5 for <uta@ietfa.amsl.com>; Wed, 8 Nov 2023 23:47:45 -0800 (PST)
Received: from direct.host-care.com (direct.host-care.com [198.136.54.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2193C151064 for <uta@ietf.org>; Wed, 8 Nov 2023 23:47:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smyslov.net ; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID :Date:Subject:In-Reply-To:References:Cc:To:From:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=+nLESivXkDpSbLr1LGQf+0Z8f3J1qfl0tstsIFs/M0g=; b=g44q5a3Yj2Xt72+AoX+4naz+1U DZA5fdrcaJTisc0vO7aWgwfgTJY8VPBGN2xiyr4RVIcqNI6DHvMQxKwiu4BUcFfZIJZm65o4GaEQz FPksiq9qLxqxrdhlRj8F0Qv/6IsJdO/Yc3ErHUxk5RNEFcymDn67a6Ojy0brJ9h5vgsjti7dsEKe1 8bPaxIM2TYcbRVo+mVvH5XxV4gdaRJZ6ZCiOMQm+LMghBPgtITT7iADiBLGwhwyLs6fitgunymZ9p 2B5Gj6lwZAHpqA6Ww4Az+UFvPlSb3DBkckUCbwlnECiVQ7Aw3qK6HJoGAHeCwexnh7Y496tWJTQ+D uxe4DZjw==;
Received: from [93.188.44.204] (port=49594 helo=buildpc) by direct.host-care.com with esmtpsa (TLS1.2) tls TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <valery@smyslov.net>) id 1r0zlO-0003c1-Ij; Thu, 09 Nov 2023 02:47:42 -0500
From: Valery Smyslov <valery@smyslov.net>
To: 'Peter Saint-Andre' <stpeter@stpeter.im>
Cc: uta@ietf.org
References: <20231108124518.E9BD2119CD@rfcpa.amsl.com> <624109b1-409b-4678-8498-8b7c8eee82d0@stpeter.im>
In-Reply-To: <624109b1-409b-4678-8498-8b7c8eee82d0@stpeter.im>
Date: Thu, 09 Nov 2023 10:47:34 +0300
Message-ID: <001001da12e1$02a15500$07e3ff00$@smyslov.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQG6UD7qrqJulee/Jzw7ApPcW+bdBwHYoOcNsKJadwA=
Content-Language: ru
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - direct.host-care.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - smyslov.net
X-Get-Message-Sender-Via: direct.host-care.com: authenticated_id: valery@smyslov.net
X-Authenticated-Sender: direct.host-care.com: valery@smyslov.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/uta/a_k36W4UgZDL0rnsjXiuMiy1B3g>
Subject: Re: [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: Thu, 09 Nov 2023 07:47:50 -0000

Hi Peter,

thank you so much for your work on this RFC and on 9325 too!
And also thanks to your co-authors and to those who participated
in reviews and discussions!

Regards,
Valery.

> -----Original Message-----
> From: Uta [mailto:uta-bounces@ietf.org] On Behalf Of Peter Saint-Andre
> Sent: Wednesday, November 08, 2023 6:59 PM
> To: uta@ietf.org
> Subject: Re: [Uta] RFC 9525 on Service Identity in TLS
> 
> 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-editor@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:    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 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

v2.23.0 | Report a Bug | By Email