Update 8/17/2021: this is all available now, come and get it! https://aka.ms/smboverquic
Hi folks, Ned Pyle guest-posting today about SMB over QUIC, a game-changer coming to Windows, Windows S...
Updated Aug 17, 2021
Version 3.0
Blog Post
2021 should be an amazing year, because it will be possible to compare several approaches to Multipathing for SMB and NFS.
I have in mind according to different use cases, comparing:
- SMB over QUIC on Windows with multipathing managed by SMB Mutli-channel
- SMB (w/o Multi-channel) over Multipath TCP (on Linux, iOS, Android, MacOS)
- NFS 4.1 with Session Trunking
- NFS 4 w/o Session Trunking but over Multipath TCP
in follow-up to some early https://packetpushers.net/multipathing-nfs4-1-kvm/ performed by Martin Houry during his internship in 2016.
NedPyle, I would be useful that you share too your point of view according to the current IETF WG discussions about Multipathing requirements support for QUIC (aka MP-QUIC, MPQUIC, ...) and especially about SMB Multi-channel requirements both in LAN and WAN scenarios.
The same exact question applies also for NFS Session Trunking to either use Multipath QUIC (when defined and implemented) and/or Multipath TCP (once implemented on Windows).
According to me, one a the key learning is the upper layer knows the application needs and the lower layer may "knows" the network capabilities.
That's where new APIs to manage these traffic engineering questions would be required and protocol implementation should become extensible and no longer monolithic (e.g MS tcpip stack, lwIP, ...).
I can share on this topics the excellent research currently in progress at https://pluginized-protocols.org/tcp/