Hi Aijun, > Let’s give you one another example that demonstrates that bandwidth > management is different from the power-aware TE:
Power-aware TE is part of bandwidth management. It is an optional portion used to also save power under low bandwidth utilization. > Image the hotel booking scenario, if you book one room(similar with bandwidth > usage is full), no other guest will book again. > But if the room isn’t reserved (no traffic via it), the manager will not take > the room out of their website.------Because he can’t assure there will be no > other guest to book this vacant room in future. I’m sorry, I can’t parse this. > Back to our scenario, if fortunately, the traffic on some links are cleared, > the nodes connecting these links shouldn’t still make these idle links sleep, > because these nodes don’t know the LSP requirements from other headend. If a link is idle, then there are no LSPs assigned to that link. By definition, for the link to be idle all LSPs must be assigned to other acceptable paths. > If the headend doesn’t know when to sleep the idle links, how to save costs > (“millions of dollar?”)? The headend is not responsible for sleeping idle links. It is only responsible for placing LSPs on other links. The nodes that are the link endpoints are responsible for putting the link to sleep. > And, we should be aware, as the operator, to keep the service uninterrupted > is the first aim. That is very much the primary goal. Tony
_______________________________________________ Lsr mailing list -- [email protected] To unsubscribe send an email to [email protected]
