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

Benjamin Kaduk <kaduk@mit.edu> Sun, 06 October 2019 16:12 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06D2A120073 for <saag@ietfa.amsl.com>; Sun, 6 Oct 2019 09:12:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MwoWHO3gF8hd for <saag@ietfa.amsl.com>; Sun, 6 Oct 2019 09:12:15 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 C6CD712004F for <saag@ietf.org>; Sun, 6 Oct 2019 09:12:14 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x96GCAdn013547 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <saag@ietf.org>; Sun, 6 Oct 2019 12:12:12 -0400
Date: Sun, 6 Oct 2019 09:12:10 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: saag@ietf.org
Message-ID: <20191006161144.GV6722@kduck.mit.edu>
References: <157019735697.1122.6295466344059123434.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <157019735697.1122.6295466344059123434.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/1NmAnryKvZv0HSo2TyvHx_oLvDk>
Subject: [saag] Fwd: Last Call: <draft-ietf-taps-transport-security-09.txt> (A Survey of Transport Security Protocols) to Informational RFC
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Oct 2019 16:12:17 -0000

I think several folks have taken an early look at this one; now would be a
great time to take a second look.

-Ben

On Fri, Oct 04, 2019 at 06:55:56AM -0700, The IESG wrote:
> 
> 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.
> 
> 
> 
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce