I actually think that the question of where one should put end-point
identification and where one should put path agility is somewhere more
complicated than just assuming that we should put a session layer on top
of transport.
While that approach works, it has drawbacks.
One example of the drawback is that the way MPTCP is architected, since
it is using vanilla TCP, it can not switch which path it is using for a
piece of data it has already sent unless that path is declared
completely dead. retransmission have to use the same path as the
original (or else you stall that connection.
While I have opinions about how to do that, and there are some choices
that seem to work well focusing on transport and above, the RRG is not
the place to work out solutions for re-architecting the Internet
Transport layer. Among other things, there are quite a number of other
experts who should be involved in that discussion, but have no interest
in how routing works.
Yours,
Joel
_______________________________________________
rrg mailing list
[email protected]
http://www.irtf.org/mailman/listinfo/rrg