[TLS] Last Call: <draft-ietf-tls-keylogfile-01.txt> (The SSLKEYLOGFILE Format for TLS) to Informational RFC

The IESG <iesg-secretary@ietf.org> Thu, 04 April 2024 20:00 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
CC: draft-ietf-tls-keylogfile@ietf.org, paul.wouters@aiven.io, sean@sn3rd.com, tls-chairs@ietf.org, tls@ietf.org
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <171226083558.18757.11643657580362532089@ietfa.amsl.com>
Date: Thu, 04 Apr 2024 13:00:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/aGCCuzSqgd_VcRG6K8Wzo92XOJ4>
Subject: [TLS] Last Call: <draft-ietf-tls-keylogfile-01.txt> (The SSLKEYLOGFILE Format for TLS) to Informational RFC

The IESG has received a request from the Transport Layer Security WG (tls) to
consider the following document: - 'The SSLKEYLOGFILE Format for TLS'
  <draft-ietf-tls-keylogfile-01.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2024-04-18. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   A format that supports the logging information about the secrets used
   in a TLS connection is described.  Recording secrets to a file in
   SSLKEYLOGFILE format allows diagnostic and logging tools that use
   this file to decrypt messages exchanged by TLS endpoints.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-tls-keylogfile/



No IPR declarations have been submitted directly on this I-D.

[TLS] Last Call: <draft-ietf-tls-keylogfile-01.tx… The IESG