IETF Logo Mail Archive

Re: [Taps] Prague agenda planning

Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch> Thu, 06 July 2017 15:20 UTC

Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49C3D1317A2 for <taps@ietfa.amsl.com>; Thu, 6 Jul 2017 08:20:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 Pl9ZmMyqH-RG for <taps@ietfa.amsl.com>; Thu, 6 Jul 2017 08:20:12 -0700 (PDT)
Received: from virgo01.ee.ethz.ch (virgo01.ee.ethz.ch [129.132.2.226]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 518611315F7 for <taps@ietf.org>; Thu, 6 Jul 2017 08:20:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by virgo01.ee.ethz.ch (Postfix) with ESMTP id 3x3Lyd11ZZzMmm7; Thu, 6 Jul 2017 17:20:09 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at virgo01.ee.ethz.ch
Received: from virgo01.ee.ethz.ch ([127.0.0.1]) by localhost (virgo01.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GnI5FpmMN96q; Thu, 6 Jul 2017 17:20:07 +0200 (CEST)
X-MtScore: NO score=0
Received: from [192.168.178.33] (p5DEC23D8.dip0.t-ipconnect.de [93.236.35.216]) by virgo01.ee.ethz.ch (Postfix) with ESMTPSA; Thu, 6 Jul 2017 17:20:07 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch>
In-Reply-To: <83292426-F72C-4B29-BF39-3567BCDBFF4C@gmail.com>
Date: Thu, 06 Jul 2017 17:20:06 +0200
Cc: taps@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <6181D4C3-5CD9-4380-BEF6-0869F2F0CF30@tik.ee.ethz.ch>
References: <C582EEC8-8762-4CB6-9CA3-4E5AF92C5A68@gmail.com> <3A3686B5-FF60-448E-9E13-4B493B472C6D@gmail.com> <77C2BA95-F95B-4597-9159-7D5FC4068860@gmail.com> <c28912d7-79a0-273b-8bc4-3206eb5a8bd8@kau.se> <A9D4A0BD-CFA1-471D-A2C4-9E2AED925448@gmail.com> <83292426-F72C-4B29-BF39-3567BCDBFF4C@gmail.com>
To: Aaron Falk <aaron.falk@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/AN1yhHhp0sSaizll7ZgVoKuyFsU>
Subject: Re: [Taps] Prague agenda planning
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussions on Transport Services <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jul 2017 15:20:17 -0000

I believe the idea was actually to have the policy after the socket intents talk; maybe even after HE?

Mirja


> Am 06.07.2017 um 16:56 schrieb Aaron Falk <aaron.falk@gmail.com>:
> 
> Updated. Still need a policy framing preso (#4) and timing.
> 
> 	• Minimal Set of Transport Services for TAPS Systems, Naeem Khademi (presenting for authors)
> 
> 		• draft-gjessing-taps-minset-05.txt
> 		• What’s new: the abstract API
> 	• Transport Security Protocol Survey, Tommy Pauly
> 
> 		• At the meeting in Chicago, the question of how security protocols should be handled was brought up, and we suggested writing a draft to do a survey of Transport Security protocols, similar to the work done in RFC 8095 and the transport usage drafts. This document goes over several common transport security protocols and analyzes their features and interfaces, particularly with regards to how they interact with their associated transport protocols and applications. For consideration as a TAPS working group doc.
> 		• draft-pauly-taps-transport-security-00.txt: The common features/interface presented by various security protocols
> 		• draft-kuehlewind-taps-crypto-sep-00.txt: The ability to separate security handshakes from data encryption
> 	• Application- & System-Specified Policy & TAPS, [[XX someone needs to frame this topic. who? Brian? Tommy? XX]]
> 
> 	• Socket Intents, Concepts & Communication Granularity, Phillipp Tiesel
> 
> 		• Socket Intents allow applications to share their knowledge about upcoming communication and express their performance preferences in an API independent way. Therefore, thy can be used by an OS/API to gain enough knowledge to perform access as well as transport protocol selection and tuning.
> 		• draft-tiesel-taps-socketintents-00.txt: concepts
> 		• draft-tiesel-taps-communitgrany-00.txt: endpoint and path selection
> 		• draft-tiesel-taps-socketintents-bsdsockets-00.txt: prototype
> 	• Happy Eyeballs update, Anna Brunstrom
> 
> 		• draft-grinnemo-taps-he-03.txt
> 		• The interface between the HE algorithm and the policy management
> 		• What should be detailed in the specification of the HE algorithm and what should be left open for implementation?
> _______________________________________________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps

v2.23.0 | Report a Bug | By Email