Re: [Taps] Prague agenda planning

Tommy Pauly <tpauly@apple.com> Thu, 29 June 2017 17:10 UTC

Return-Path: <tpauly@apple.com>
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 67978129B5E for <taps@ietfa.amsl.com>; Thu, 29 Jun 2017 10:10:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level:
X-Spam-Status: No, score=-4.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.com
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 JdJ92asF8Fpd for <taps@ietfa.amsl.com>; Thu, 29 Jun 2017 10:10:00 -0700 (PDT)
Received: from mail-in21.apple.com (mail-out21.apple.com [17.171.2.31]) (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 9CF9C1200C1 for <taps@ietf.org>; Thu, 29 Jun 2017 10:10:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple; q=dns/txt; i=@apple.com; t=1498756199; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-transfer-encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=4Xb9pczO3335mXwO3QBYcUEYCPPsTYnCY2ejRLUNAuQ=; b=T5OSFDI18rnX+G9sV7D72qn3hVP/SxghuU4qWAVrlKd+s4BdWiJV0TfEH87AZSjw R8mCqQ94IjBfIRAcP/bXG4CfXOofSUM3e+b1l71cpkSeAB0LGyWwHOkCl8OuLFdf 8ekkZVYNnYxbQAHkvkk77lbKGpOTrVrdnAVkQLkG8kK0Vkr9sGowKZDjxpYc/w/w ZRd82Lzrm1mDJjv84RkmeOFb8PVaO5TaUDse0U5jy9vnBHd5sDGhzk+eoiIt51Ss apSTaKsdTN+sJwwYk+IpS3bnMKQPN/tktUuGRVbAxN9yUBjHA/3zU7SX8NtNVXif sIpBuLo7phtWlmmljdUTcg==;
Received: from relay5.apple.com (relay5.apple.com [17.128.113.88]) (using TLS with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail-in21.apple.com (Apple Secure Mail Relay) with SMTP id 4F.F0.07017.76435595; Thu, 29 Jun 2017 10:09:59 -0700 (PDT)
X-AuditID: 11ab0215-43f899c000001b69-14-59553467e31d
Received: from nwk-mmpp-sz10.apple.com (nwk-mmpp-sz10.apple.com [17.128.115.122]) by relay5.apple.com (Apple SCV relay) with SMTP id B1.29.09344.76435595; Thu, 29 Jun 2017 10:09:59 -0700 (PDT)
MIME-version: 1.0
Content-type: text/plain; charset="utf-8"
Received: from da0602a-dhcp103.apple.com (da0602a-dhcp103.apple.com [17.226.23.103]) by nwk-mmpp-sz10.apple.com (Oracle Communications Messaging Server 8.0.1.2.20170210 64bit (built Feb 10 2017)) with ESMTPSA id <0OSB009VZJON1560@nwk-mmpp-sz10.apple.com>; Thu, 29 Jun 2017 10:09:59 -0700 (PDT)
Sender: tpauly@apple.com
From: Tommy Pauly <tpauly@apple.com>
In-reply-to: <CEA46958-6620-4138-BA2F-B55D1F87674A@trammell.ch>
Date: Thu, 29 Jun 2017 10:09:58 -0700
Cc: Aaron Falk <aaron.falk@gmail.com>, taps WG <taps@ietf.org>
Content-transfer-encoding: quoted-printable
Message-id: <EDC3DBF5-8463-42AD-BB31-D8EE93CB0BB5@apple.com>
References: <C582EEC8-8762-4CB6-9CA3-4E5AF92C5A68@gmail.com> <3A3686B5-FF60-448E-9E13-4B493B472C6D@gmail.com> <CEA46958-6620-4138-BA2F-B55D1F87674A@trammell.ch>
To: "Brian Trammell (IETF)" <ietf@trammell.ch>
X-Mailer: Apple Mail (2.3435)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrELMWRmVeSWpSXmKPExsUi2FAYoZtuEhpp0LnEwqLt9zRWi40t79gs 7sQ4MHvsnHWX3WPJkp9MHk/2z2QJYI7isklJzcksSy3St0vgyri5ZiFTwULJiv5t51kbGG+J dDFyckgImEh833WEpYuRi0NIYA2TxMvle9hhEj/+b2WFSBxilPi0fQEjSIJXQFDix+R7QB0c HMwC6hJTpuRC1KxlkvhyqYsZJC4sICGxeU8iSLmwgJbEs1MP2UBsNgEViePfNoCVcArYS+zs qgEJswioSmyYu58ZxGYWsJOYdm8WlK0t8eTdBVaIrTYS10/uBrOFBJYwStzqdwCxRQT0JFb+ +ccCcbKsxJa24+wg50gIbGCTePfyOdMERuFZSK6ehXD1LCQrFjAyr2IUzk3MzNHNzDMy1Ess KMhJ1UvOz93ECAr01UyiOxjnvzI8xCjAwajEw7tBIzRSiDWxrLgy9xCjNAeLkjivunZIpJBA emJJanZqakFqUXxRaU5q8SFGJg5OqQbG2MO32yZ8WLF3/pxYrqkFVmvEvk5rZG9JLLg1qaNU P3Nuz9yvPtdDVD1ZGewe/9zdHHkoYcaFiqXWLMrM1u1LO/Pia8OL7hoF/92uK5W1P5w/3U7J 6NV5Pl+njmUlOlz3XebMLX39wq0mkYkj+freY89Z1a/UfHn1m5NJ1HfVUc2i9d1d5/yVWIoz Eg21mIuKEwHzC7tvVQIAAA==
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprMIsWRmVeSWpSXmKPExsUi2FBcpZtuEhppsG2dsEXb72msFhtb3rFZ 3IlxYPbYOesuu8eSJT+ZPJ7sn8kSwBzFZZOSmpNZllqkb5fAlXFzzUKmgoWSFf3bzrM2MN4S 6WLk5JAQMJH48X8raxcjF4eQwCFGiU/bFzCCJHgFBCV+TL7H0sXIwcEsoC4xZUouRM1aJokv l7qYQeLCAhISm/ckgpQLC2hJPDv1kA3EZhNQkTj+bQNYCaeAvcTOrhqQMIuAqsSGufuZQWxm ATuJafdmQdnaEk/eXWCF2Gojcf3kbjBbSGAJo8StfgcQW0RAT2Lln38sECfLSmxpO84+gVFg FpJDZyEcOgvJ1AWMzKsYBYpScxIrTfUSCwpyUvWS83M3MYLDsjBiB+P/ZVaHGAU4GJV4eDdo hEYKsSaWFVfmAkOCg1lJhLdIHSjEm5JYWZValB9fVJqTWnyIsQrol4nMUqLJ+cCYySuJNzQx MTAxNjYzNjY3MaeKsJI474rbwZFCAumJJanZqakFqUUwy5k4OKUaGJuqe7X6/rtOrWib484Z tCQlemqzof/bE3KtBlPXLZjWr6mgsO6fyQKFrWe00g49tU6emnblxPQPCirftr8qtLw0b2ar 1/5rvoKiFWkCJrq7Z7O2lvKyzNwe1R3Xd/oYY17ig/Vfzh+Jm/ho7nOPS8raXU/eObR2Vt7+ +Dcw+pFx6LHcQ2yh7kosxRmJhlrMRcWJAPgM5eSmAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/fKOdVPnS6VRGVthC7pBa5o2dNsQ>
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, 29 Jun 2017 17:10:02 -0000


> On Jun 29, 2017, at 9:07 AM, Brian Trammell (IETF) <ietf@trammell.ch> wrote:
> 
> hi Aaron,
> 
>> On 29 Jun 2017, at 17:36, Aaron Falk <aaron.falk@gmail.com> wrote:
>> 
>> Updating. Our agenda time is much more productive if we can home in on specific questions to discuss rather than just give document overviews. Authors & other folk: what’s interesting, unclear, or controversial here?
> 
> I think it's time to level up and have a discussion about "policy" and how it relates to TAPS.
> 
> I'm going to leave the definition of "policy" here deliberately vague with the hope that we can start to build some terminology around it at the meeting.

+1 to having a general discussion on the topic of policy (both application-specified and system-specified), likely following onto the presentation of intents. Getting a formal set of definitions would really help moving forward in our discussions.
> 
>> 
>> 	• draft-gjessing-taps-minset-05.txt
>> 
>> 		• There’s been some interesting discussion on the draft. Are there any specific topics we should set aside time to discuss?
>> 	• Socket Intents, Philipp
>> 
>> 		• Again, what specific topics should we discuss?
>> 		• We’ve been told to expect 3 drafts: on general concepts, BSD implementation, & communication granularity. What’s worth discussing?
> 
> Given the focus of the socket intents and granularity work, I think starting the policy discussion here makes sense.
> 
>> 	• Michio Honda HotNets paper “PASTE: Network Stacks Must Integrate with NVMM Abstractions”
>> 
>> 		• “These days I'm working on networking interface for non-volatile main memory (a.k.a. persistent memory and storage-class memory), because with such devices networking stack/API becomes a bottleneck in the end-to-end communication that involves persistent media (disk or SSDs for now). I saw some post-socket discussion in the minutes of the last meeting, so I wonder if this type of work could give some useful information to IETFers who design new transport API standards.”
>> 		• Is there interest in this topic? AFAIK, there’s no Internet Draft. I will inquire whether Michio intends to submit one.
> 
> IMO this is very interesting stuff. Might be better as a tsvarea presentation?
> 
> Cheers,
> 
> Brian
> 
>> 	• Transport Security Protocol Survey, Tommy

Since the security part of the protocols is a bit new in TAPS, we’ll probably want to give a bit of document overview, but I think the interesting discussion points here are in:
- The common features/interface presented by various security protocols
- The ability to separate security handshakes from data encryption

Thanks,
Tommy

>> 
>> _______________________________________________
>> Taps mailing list
>> Taps@ietf.org
>> https://www.ietf.org/mailman/listinfo/taps
> 
> _______________________________________________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps