Re: Multiple Address Service for Transport (MAST)

[Pekka Nikander <pekka.nikander@nomadiclab.com>]

(Discussing TCP vs. wedge approaches)

Dave Crocker wrote:
> Three other arguments worth considering:
>
>           c) working with mobility, as well as multi-homing
>
>           d) not incurring the per-packet option overhead with a larger
>           packet and with option processing.
>
>           e) moving the multi-homing/mobility negotiations out of the
>           critical path to transport activity; hence it does not impose
>           any start-of-connection delays. on the other hand, my
>           impression is that the tcp option approach does not impose a
>           delay, either.

There are a couple of other issues worth consider, too:

            f) transport layer implementation requires more signalling,
            i.e., separately for each connection, than a wedge one,
            which is basically host-to-host (or end-point-to-end-point)

            g) a wedge implementation will have interesting interplay
            with transport layer RTT and throughput estimates.  OTOH,
            that information is actually more host-to-host (or path
            related) in nature than connection related.

--Pekka Nikander