On 8. Jun 2017, at 15:50, Tommy Pauly <[email protected]> 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! Hi Tommy,
so this means I can run my own TCP stack and my own IPv6 stack in my application, if I understood that correctly. How is the port number space managed between the different applications? I'm wondering how the demultiplexing is done? Can I also use the API for a transport protocol supporting the port number concept, but not being UDP or TCP, like SCTP or UDP-Lite or DCCP or whatever might come up in the future? Best regards Michael > > Thanks, > Tommy > _______________________________________________ > Taps mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/taps _______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
