[rfc-dist] RFC 9149 on TLS Ticket Requests

rfc-editor@rfc-editor.org Mon, 25 April 2022 23:44 UTC

Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D2FD1C3AB7AD; Mon, 25 Apr 2022 16:44:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1650930258; bh=k58Tgj+RQ9jywg31tsyuwy3erRf9B0rWTS2brlDic4Q=; h=To:From:Cc:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=xm/Zw8kjKnXDcSZI4dxpI4I5sdohoJFB/bMR0UJ/EAkTtb4C3rbYTql/9ZMd93edx 4FV1jm6u0Af+ZQdOEF+fDzAKUOYAKZvEETXh3sPR/ZCuax9P10m1letut7Lt6+IkwV L+tnAM1YS5VerLvaW2RpFarYFN2cUoAuNJL5JV9U=
X-Mailbox-Line: From rfc-dist-bounces@rfc-editor.org Mon Apr 25 16:44:18 2022
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 976A5C3CA2AF; Mon, 25 Apr 2022 16:44:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1650930258; bh=k58Tgj+RQ9jywg31tsyuwy3erRf9B0rWTS2brlDic4Q=; h=To:From:Cc:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=xm/Zw8kjKnXDcSZI4dxpI4I5sdohoJFB/bMR0UJ/EAkTtb4C3rbYTql/9ZMd93edx 4FV1jm6u0Af+ZQdOEF+fDzAKUOYAKZvEETXh3sPR/ZCuax9P10m1letut7Lt6+IkwV L+tnAM1YS5VerLvaW2RpFarYFN2cUoAuNJL5JV9U=
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4C12C3A9DF1; Mon, 25 Apr 2022 16:44:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.255
X-Spam-Level:
X-Spam-Status: No, score=0.255 tagged_above=-999 required=5 tests=[HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 eqlBbKxQY9uw; Mon, 25 Apr 2022 16:44:07 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [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 1DE73C2D7351; Mon, 25 Apr 2022 16:44:07 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id CC6A41330E9; Mon, 25 Apr 2022 16:44:06 -0700 (PDT)
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, tls@ietf.org
Message-Id: <20220425234406.CC6A41330E9@rfcpa.amsl.com>
Date: Mon, 25 Apr 2022 16:44:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/NW4e9u9CrpKEpxtrQ9V7FpfE6pM>
Subject: [rfc-dist] RFC 9149 on TLS Ticket Requests
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9149

        Title:      TLS Ticket Requests 
        Author:     T. Pauly,
                    D. Schinazi,
                    C.A. Wood
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2022
        Mailbox:    tpauly@apple.com,
                    dschinazi.ietf@gmail.com,
                    caw@heapingbits.net
        Pages:      8
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tls-ticketrequests-07.txt

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

        DOI:        10.17487/RFC9149

TLS session tickets enable stateless connection resumption for
clients without server-side, per-client state.  Servers vend an
arbitrary number of session tickets to clients, at their discretion,
upon connection establishment.  Clients store and use tickets when
resuming future connections.  This document describes a mechanism by
which clients can specify the desired number of tickets needed for
future connections.  This extension aims to provide a means for
servers to determine the number of tickets to generate in order to
reduce ticket waste while simultaneously priming clients for future
connection attempts.

This document is a product of the Transport Layer Security 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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org