Dear all, we continued our effort in describing strategies to cope with multipath caused packet scrambling due to disjoint path latencies.
We see this along with the efforts of https://datatracker.ietf.org/doc/draft-bonaventure-iccrg-schedulers/ and https://datatracker.ietf.org/doc/draft-dawkins-quic-multipath-selection/ which all describe protocol independent multipath strategies on sender and receiver side. This makes perfectly sense for multipath capable protocols like MP-DCCP, MPTCP, MP-QUIC and SCTP. I wonder if those works on mutlipath topics can be somewhere consolidated and move from an individual state to a WG adopted state? That would also help other SDOs like 3GPP and BBF to implement multipath support in their architectures. Br Markus > -----Original Message----- > From: [email protected] <[email protected]> > Sent: Montag, 25. Oktober 2021 20:39 > To: von Hugo, Dirk <[email protected]>; von Hugo, Dirk <Dirk.von- > [email protected]>; Amend, Markus <[email protected]>; Amend, > Markus <[email protected]> > Subject: New Version Notification for draft-amend-iccrg-multipath-reordering- > 03.txt > > > A new version of I-D, draft-amend-iccrg-multipath-reordering-03.txt > has been successfully submitted by Markus Amend and posted to the > IETF repository. > > Name: draft-amend-iccrg-multipath-reordering > Revision: 03 > Title: Multipath sequence maintenance > Document date: 2021-10-25 > Group: Individual Submission > Pages: 16 > URL: https://www.ietf.org/archive/id/draft-amend-iccrg-multipath- > reordering-03.txt > Status: https://datatracker.ietf.org/doc/draft-amend-iccrg-multipath- > reordering/ > Html: https://www.ietf.org/archive/id/draft-amend-iccrg-multipath- > reordering-03.html > Htmlized: > https://datatracker.ietf.org/doc/html/draft-amend-iccrg-multipath- > reordering > Diff: https://www.ietf.org/rfcdiff?url2=draft-amend-iccrg-multipath- > reordering-03 > > Abstract: > This document discusses the issue of packet reordering which occurs > as a specific problem in multi-path connections without reliable > transport protocols such as TCP. The topic is relevant for devices > connected via multiple accesses technologies towards the network as > is foreseen, e.g., within Access Traffic Selection, Switching, and > Splitting (ATSSS) service of 3rd Generation Partnership Project > (3GPP) enabling fixed mobile converged (FMC) scenario. > > > > > The IETF Secretariat >
