Re: The internet architecture

["Randy Presuhn" <randy_presuhn at mindspring.com>]

Hi -

> From: "John Day" <jeanjour at comcast.net>
> To: "Rémi Després" <remi.despres at free.fr>; "John C Klensin" <john-ietf at jck.com>
> Cc: "Bryan Ford" <baford at mpi-sws.org>; <ietf at ietf.org>
> Sent: Monday, December 29, 2008 7:24 AM
> Subject: Re: The internet architecture
>
> No it isn't Transport's job.  Transport has one
> and only one purpose: end-to-end reliability and
> flow control.
>
> "Managing" the resources of the network is the network layer's job.
>
> Although, these distinctions of Network and
> Transport Layer are . . . shall we say, quaint.
>
> Multihoming is fundamentally a routing problem.

Depends on what one is routing *to* - application,
host, or attachment point.

...
> It is a problem of routing not be able to
> recognize that two points of attachment go to the
> same place.  Portraying it as anything else is
> just deluding yourself.

The multiple-entrance, multiple exit problem could also
be attacked with a variation on good ol' multi-link
procedure, but done just below (or as a sublayer of)
transport, but above (connectionless) network, and
not restrict it to datalink.

Randy


_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www.ietf.org/mailman/listinfo/ietf