We mean multihoming in a very broad sense -- A has multiple "things"
to B. Those "things" may be separate fibers/wires, or MPLS tunnels, or ...
As to possible solutions above the IP/Internet layer -- that is interesting,
but outside of our scope.
Frank Kastenholz
At 01:03 PM 3/5/02 -0500, Howard C. Berkowitz wrote:
>3.11 Multi-homing
>Is multihoming really the right term here? The problem as seen by users is
fault tolerance, and its solution may properly involve sub-IP, network
layer, and higher layers. Should this definition be constrained to focus on
multiple routed paths to all elements, without prejudicing mechanisms above
and below the routing layer?
>
>
>see both multi6 and draft-berkowitz-multreq-02.txt for possible
terminology.
==================================================
My preferrred signature is:
This information is for the sole use of
whoever receives it and may contain confusing,
enlightening, enraging, entertaining,
irritating, or just plain stupid information,
including without limitation, double-secret-
probation information belonging to [CENSORED
BY THE NSA/FBI/MOUSE]. Any unauthorized review,
use, disclosure, or distribution outside of an
establishment serving alchohol is prohibited on
days that do not end in Y.
But our ******'d lawyers would rather have:
=======================================
This email message is for the sole use of the intended recipient (s) and may
contain confidential and privileged information, including without
limitation, Confidential and/or Proprietary Information belonging to
Unisphere Networks, Inc. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply email and destroy all copies of the original
message.
This archive was generated by hypermail 2b29 : Mon Aug 04 2003 - 04:10:04 EDT