[Csci551-talk] MED & load sensitive routing in proj B
coolrocks at tom.com
Sat Apr 24 23:41:25 PDT 2004
Reading the specs for "sensitive routing" and "oscillation" in project B, I got confused with MED. Is MED an attribute for
<A> a link. I.e. between neighbor routers? or
<B> for one of the "routes"(prefix/mask pair) which a "router" is responsible for ?
My doubts came from the following:
I refered to the specs in project A and it seemed that MED is defined as <B>(see, 3rd paragraph in subsection 5 in project A specs). If using this definition in Project B, one only needs to change the MED for an internal route (the one and only prefix/mask pair) which the router is responsible for. But the question is, if this is the case, it won't be necessary to run link-state routing at all! Link-state routing is run when a router's links' "states" change (i.e neighbor router up or down, etc). In our case, none of the links' states has changed since there are no two routers routing to the same prefix/mask pair, there won't be a prefered link to choose (unlike in project A where there are two or more external routers routing to the same AS where we need to make a routing decision). No matter what the MED value of the route has changed to, everyone will still have to route through that router to reach that domain.
If MED is for a link, which is different from project A, do all the links from a router take the same value, or each link has its own MED value? If the latter, how should one allocate the changes among links?
Please comment and enlighten!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Csci551-talk