[168406] in North American Network Operators' Group
Re: OSPF Costs Formula that include delay.
daemon@ATHENA.MIT.EDU (Owen DeLong)
Fri Jan 24 16:17:58 2014
From: Owen DeLong <owen@delong.com>
In-Reply-To: <0bca01cf1944$a0a4d020$e1ee7060$@oneunified.net>
Date: Fri, 24 Jan 2014 12:59:19 -0800
To: Raymond Burkholder <ray@oneunified.net>
Cc: "<nanog@nanog.org>" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Jan 24, 2014, at 12:41 PM, Raymond Burkholder <ray@oneunified.net> =
wrote:
>>=20
>> Some networks I have worked with took the average latency of each =
link and
>> assigned that (with some constant multiple) as the interface cost.
>>=20
>> Of course this all fails miserably if you are using anything like =
MPLS
>> underneath your OSPF.
>>=20
>=20
> But then when using MPLS underneath, then MPLS Traffic Engineering can =
be
> used to do some interesting path computations and resiliency =
configurations.
I wasn=92t attempting to promote or discourage use of MPLS. I was merely =
endeavoring to point out that in an MPLS world, OSPF costs are not how =
you want to manage your traffic.
Owen
