[47042] in North American Network Operators' Group
What extent do ISPs care about diff types of Traffic Engineering?
daemon@ATHENA.MIT.EDU (Shivkuma)
Wed Apr 24 15:48:04 2002
Date: Wed, 24 Apr 2002 15:47:38 -0400 (EDT)
From: Shivkuma <shivkuma@networks.ecse.rpi.edu>
To: nanog@merit.edu
Message-ID: <Pine.GSO.4.10.10204241522300.11229-100000@chapman.ecse.rpi.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
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
