Re: [Taps] User-Space Networking in iOS 11

[Zhen Cao]

Hello Tommy,

Thank you for sharing this.  Going through the slides of WWDC17, I
have some clarification questions: a) the slides only plot WiFi when
talking about the 'user-space', does that also apply to the cellular
link?  I ask this because the user-space packet io needs a different
driver for different links as far as i know.  b) does the user space
networking always performs better than the kernel counterpart?

Many thanks
Zhen

On Fri, Jun 9, 2017 at 3:50 AM, Tommy Pauly  wrote:
> Hello,
>
> I wanted to point the TAPS group to some of the work that we announced this
> week at WWDC that relates to the Post-Sockets API effort. You can see a
> video of the session here (relevant section at ~13:50), along with the
> slides:
>
> https://developer.apple.com/videos/play/wwdc2017/707
>
> In the current betas of iOS 11, we have introduced “User-Space Networking”
> beneath our networking APIs. The transport and IP protocols are now being
> co-located with the security and application protocols in the process,
> meaning that we are no longer using sockets within the implementation of
> these APIs. This shift allows us to reduce the context switches between
> protocol layers, and could potentially open opportunities for the kind of
> stack flexibility and customization that the TAPS group is looking at. We’re
> excited to be making some first steps into a truly “Post-Sockets” world!
>
> 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

[Taps] New Drafts on Transport Security Interface for TAPS

[Tommy Pauly]

Hello,

We’ve just posted two new documents that start addressing how to incorporate 
security protocols into the TAPS framework for use alongside transport 
protocols. 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.

A Survey of Transport Security Protocols
https://tools.ietf.org/html/draft-pauly-taps-transport-security-00 


The second document is an update of a draft that Mirja published earlier this 
year, which we would also like to bring into TAPS. This document takes a more 
normative approach, and suggests that transport security protocols should allow 
separation of the handshake and record protocols (similar to what QUIC does). 
This approach has an effect on the interaction between the security and 
transport layers, and adds some protocol-flexibility properties that complement 
the TAPS approach.

Separating Crypto Negotiation and Communication
https://tools.ietf.org/html/draft-kuehlewind-taps-crypto-sep-00 


Best,
Tommy___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

[Taps] Fwd: New Version Notification for draft-kuehlewind-taps-crypto-sep-00.txt

[Tommy Pauly]

> Begin forwarded message:
> 
> From: internet-dra...@ietf.org
> Subject: New Version Notification for draft-kuehlewind-taps-crypto-sep-00.txt
> Date: July 3, 2017 at 8:08:21 AM PDT
> To: Mirja Kuehlewind , Christopher Wood 
> , Tommy Pauly , "Christopher A. Wood" 
> 
> 
> 
> A new version of I-D, draft-kuehlewind-taps-crypto-sep-00.txt
> has been successfully submitted by Christopher A. Wood and posted to the
> IETF repository.
> 
> Name: draft-kuehlewind-taps-crypto-sep
> Revision: 00
> Title:Separating Crypto Negotiation and Communication
> Document date:2017-07-03
> Group:Individual Submission
> Pages:12
> URL:
> https://www.ietf.org/internet-drafts/draft-kuehlewind-taps-crypto-sep-00.txt
> Status: 
> https://datatracker.ietf.org/doc/draft-kuehlewind-taps-crypto-sep/
> Htmlized:   
> https://tools.ietf.org/html/draft-kuehlewind-taps-crypto-sep-00
> Htmlized:   
> https://datatracker.ietf.org/doc/html/draft-kuehlewind-taps-crypto-sep-00
> 
> 
> Abstract:
>   Due to the latency involved in connection setup and security
>   handshakes, there is an increasing deployment of cryptographic
>   session resumption mechanisms.  While cryptographic context and
>   endpoint capabilities need to be be known before encrypted
>   application data can be sent, there is otherwise no technical
>   constraint that the crypto handshake must be performed on the same
>   transport connection.  This document recommends a logical separation
>   between the mechanism(s) used to negotiate capabilities and set up
>   encryption context (handshake protocol), the application of
>   encryption and authentication state to data (record protocol), and
>   the associated transport connection(s).
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
> 

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

[Taps] Fwd: New Version Notification for draft-pauly-taps-transport-security-00.txt

[Tommy Pauly]

> A new version of I-D, draft-pauly-taps-transport-security-00.txt
> has been successfully submitted by Christopher A. Wood and posted to the
> IETF repository.
> 
> Name: draft-pauly-taps-transport-security
> Revision: 00
> Title:A Survey of Transport Security Protocols
> Document date:2017-07-03
> Group:Individual Submission
> Pages:22
> URL:
> https://www.ietf.org/internet-drafts/draft-pauly-taps-transport-security-00.txt
> Status: 
> https://datatracker.ietf.org/doc/draft-pauly-taps-transport-security/
> Htmlized:   
> https://tools.ietf.org/html/draft-pauly-taps-transport-security-00
> Htmlized:   
> https://datatracker.ietf.org/doc/html/draft-pauly-taps-transport-security-00
> 
> 
> 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 [RFC8095] by
>   describing the interfaces required to add security protocols.  It
>   examines Transport Layer Security (TLS), Datagram Transport Layer
>   Security (DTLS), Quick UDP Internet Connections with TLS (QUIC +
>   TLS), MinimalT, CurveCP, tcpcrypt, and Internet Key Exchange with
>   Encapsulating Security Protocol (IKEv2 + ESP).  This survey is not
>   limited to protocols developed within the scope or context of the
>   IETF.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
> 

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

Re: [Taps] New Version Notification for draft-tiesel-taps-communitgrany-00.txt

[Michael Welzl]

Hi,

+1 on discussing terminology: this is a painful read, because it’s a document 
that puts a finger deep into a wound  :-)

So it seems to me that it’s clear we need to agree on a common terminology. 
Since I won’t be there, just for the record: I don’t have strong opinions about 
terminology.
The one we’re using in minset (e.g. flow, ..) was a quick choice, I’ll be happy 
to update along with what the majority thinks.

Cheers,
Michael


> On Jun 28, 2017, at 11:42 AM, Philipp S. Tiesel  
> wrote:
> 
> Hi,
> 
> as promised, here is our second draft towards automatic selection of 
> transport option.
> 
> It is primarily focusing on endpoint- and path selection and still lacks 
> details about Transport Protocol Stack Instance Selection.
> 
> Thanks to Mirja for early feedback preventing unnecessary terminology issues.
> Nevertheless, I expect some discussion about terminology.
> 
> I welcome feedback and suggestions where more detail/discussion is needed. 
> 
>> Begin forwarded message:
>> 
>> From: internet-dra...@ietf.org
>> Subject: New Version Notification for draft-tiesel-taps-communitgrany-00.txt
>> Date: 27. June 2017 at 20:29:51 GMT+2
>> To: "Philipp Tiesel" , "Theresa Enghardt" 
>> , "Philipp S. Tiesel" 
>> 
>> 
>> A new version of I-D, draft-tiesel-taps-communitgrany-00.txt
>> has been successfully submitted by Philipp S. Tiesel and posted to the
>> IETF repository.
>> 
>> Name:draft-tiesel-taps-communitgrany
>> Revision:00
>> Title:   Communication Units Granularity Considerations for 
>> Multi-Path Aware Transport Selection
>> Document date:   2017-06-27
>> Group:   Individual Submission
>> Pages:   10
>> URL:
>> https://www.ietf.org/internet-drafts/draft-tiesel-taps-communitgrany-00.txt
>> Status: 
>> https://datatracker.ietf.org/doc/draft-tiesel-taps-communitgrany/
>> Htmlized:   
>> https://tools.ietf.org/html/draft-tiesel-taps-communitgrany-00
>> Htmlized:   
>> https://datatracker.ietf.org/doc/html/draft-tiesel-taps-communitgrany-00
>> 
>> 
>> Abstract:
>>  This document provides an abstract framework to reason about the
>>  composition of multi-path aware systems in a protocol-independent
>>  fashion.  It discusses basic mechanisms that are used in multi-path
>>  systems and their applicability to different granularities of
>>  communication units.  This document is targeted as consideration
>>  basis for automation of destination, path and transport protocol
>>  selection within the transport layer.
>> 
>> 
>> 
>> 
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>> 
>> The IETF Secretariat
>> 
> 
> AVE!
>   Philipp S. Tiesel
> 
> -- 
> Technische Universität Berlin – FG Internet Network Architectures (INET)
> office: MAR 4.024 / Sekr.: MAR 4.4, Marchstr. 23, 10587 Berlin
> e-mail: phil...@inet.tu-berlin.de • phone: +49-30-314-75763
> 
> 
> ___
> 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