Last Call: <draft-ietf-taps-transport-security-09.txt> (A Survey of Transport Security Protocols) to Informational RFC

The IESG <iesg-secretary@ietf.org> Fri, 04 October 2019 13:55 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>
Subject: Last Call: <draft-ietf-taps-transport-security-09.txt> (A Survey of Transport Security Protocols) to Informational RFC
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
CC: magnus.westerlund@ericsson.com, philipp@tiesel.net, taps-chairs@ietf.org, Philipp Tiesel <philipp@tiesel.net>, draft-ietf-taps-transport-security@ietf.org, taps@ietf.org
Content-Transfer-Encoding: 7bit
Reply-To: ietf@ietf.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <157019735697.1122.6295466344059123434.idtracker@ietfa.amsl.com>
Date: Fri, 04 Oct 2019 06:55:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/WCxuHv4yvixfX7ldNVi3kx3ZwRc>

The IESG has received a request from the Transport Services WG (taps) to
consider the following document: - 'A Survey of Transport Security Protocols'
  <draft-ietf-taps-transport-security-09.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
ietf@ietf.org mailing lists by 2019-10-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


   This document provides a survey of commonly used or notable network
   security protocols, with a focus on how they interact and integrate
   with applications and transport protocols.  Its goal is to supplement
   efforts to define and catalog transport services by describing the
   interfaces required to add security protocols.  This survey is not
   limited to protocols developed within the scope or context of the
   IETF, and those included represent a superset of features a Transport
   Services system may need to support.  Moreover, this document defines
   a minimal set of security features that a secure transport system
   should provide.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-taps-transport-security/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-taps-transport-security/ballot/


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

Last Call: <draft-ietf-taps-transport-security-09… The IESG