TE goals

[marcelo bagnulo braun <marcelo@it.uc3m.es>]

Hi,

After all the discussion about TE and shim, it seems
that the first thing that is needed is to identify a
set of TE requirements for shim. In order to do that,
i guess that we could start but identifying the goals
that the current multihomed sites are after when they
use the TE engineering capabilities. By this i mean
the high level goals that they are trying to achieve,
as opposed to the actual configurations that they use
to achieve them.

It is very important to keep in mind that the focus
here is TE for multihomed end sites, as opposed to TE
for providers.

I have tried to make a list of the goals that have
been brought up to the list and expressed in some
other documents

Goal 1: Use the "best"/"shortest" path to get to a
        given destination

Goal 2: Use one link as primary and the other backup

Goal 3: Use one link for exchanging traffic between
        the sites (peering) and the other link for
        exchanging traffic with the rest of the
        Internet (transit)

Goal 4: Use one link for peering and backup and the
        other link for transit

Goal 5: Load spreading across the different links.
        An important aspect here is granularity i.e.
        how much granularity is available to express
        the percentage of traffic routed through each
        link

Are there other goals that multihomed end-sites
performing TE are commonly after?

Regards, marcelo