In message <[EMAIL PROTECTED]> "Yue Wang" writes: > > Dear Acee and Joel, > > Yes, I was wrong. Thanks a lot. > > The last thing: please look at Case 2 section 3.5.1 in my draft. > There is only one route (e.g. the 1-hop route) for a anycast address > maintained > by the current OSPF. If the route is withdrawn due to some reason > (e.g. server power off or network disconnection), the alternative > route (e.g. the 2-hop one) will be rediscovered until the next LSA > refreshment (Sec 12.4, RFC2328). Note that the default LSRefreshTime > is 30 minutes. > > I hope OSPF WG would define it clearly for anycast. > Thanks a lot for your discussions so far.
FYI - OSPF LSRefreshTime is related to the refresh time for a given LSA ***if nothing changes*** in that LSA. Propogation of the addition or withdrawl of a route is propogated more or less immediately. In the case of a network disconnect affecting a stub or link, a router adjacent to the disconnect would propogate an LSA change immediately. In the case of a router going down, the routers adjacent to it would immediately propogate LSA changes withdrawing links to it. The down router would be isolated (disconnected, partitioned) from the topology. Once isolated anything in the way of stubs, inter-area or ASE would be irrelevant even if not immediately removed by aging. By "more or less immediately" I mean the following. In a quiescent network, origination of a new LSA will occur within link failure detection time with for framings such as SONET is typically on the order of 10msec. In a hypothetical case where the network is unstable and already propogating lots of LSA changes, origination and propogation could be delayed but only to the extent needed to limit transfer on information between neighbors. Maybe you should learn more about how OSPF works or check with someone who thoroughly understands OSPF before further lecturing the work group on what is wrong with it. There is no need draft-wang-aospf-00 and it should not be a WG item. Curtis _______________________________________________ OSPF mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ospf
