What extent do ISPs care about diff types of Traffic Engineering?
Dear NANOGers, I'd like to get a sense of how much ISPs care about different types of traffic engineering (at the routing level): Intra-domain: - multiple-paths between selected nodes - different (previleged) routing for specific traffic classes - traffic trunking and mapping to routing (eg: through MPLS) - OSPF/IS-IS parameter tweaking(i.e. link weights) for TE purposes - Dont care at all: use plain OSPF/IS-IS Inter-domain: - Hot potato/cold potato routing - Inbound load balancing (between peering links) - Inbound load balancing (between transit links or a mix of peering/transit) - Outbound load balancing (between peering links) - Outbound load balancing (between transit links or a mix of peering/transit) - Dont care about TE Are there other important categories of TE missed above? best -Shiv
On Wednesday, April 24, 2002, at 03:47 , Shivkuma wrote:
Inter-domain: - Hot potato/cold potato routing - Inbound load balancing (between peering links) - Inbound load balancing (between transit links or a mix of peering/transit) - Outbound load balancing (between peering links) - Outbound load balancing (between transit links or a mix of peering/transit) - Dont care about TE
Are there other important categories of TE missed above?
What about outbound path (exit) selection based on performance criteria like latency, loss, jitter or route stability? Joe
participants (2)
-
Joe Abley
-
Shivkuma