Hi, Tony, and Vishnu:
Let’s give you one another example that demonstrates that bandwidth management is different from the power-aware TE: 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. 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 the headend doesn’t know when to sleep the idle links, how to save costs (“millions of dollar?”)? And, we should be aware, as the operator, to keep the service uninterrupted is the first aim. Best Regards Aijun Wang China Telecom From: [email protected] [mailto:[email protected]] On Behalf Of Tony Li Sent: Friday, September 18, 2026 11:00 PM To: Aijun Wang <[email protected]> Cc: Vishnu Pavan Beeram <[email protected]>; Vishnu Pavan Beeram <[email protected]>; Adrian Farrel <[email protected]>; Barth, Colby <[email protected]>; Robert Raszuk <[email protected]>; John Drake <[email protected]>; John Drake <[email protected]>; WG TEAS <[email protected]>; lsr <[email protected]> Subject: [Lsr] Re: [Teas] Re: Re: Re: Re: Re: Re: Re: Re: [Green] 【Distributed Power-aware TE is Impossilbe】RE: RV: Call for adoption: draft-many-teas-power-steering-01 (Ends 2026-09-10) Hi Aijun, Then, from the operator’s side, why will they deploy such non-deterministic (network-wide polarization) solution in their network? It can save them millions of dollars. It should also be noted that basic distributed bandwidth-engineering is already non-deterministic: path selection is a function of previous path placements. Since bandwidth management is a vital benefit for operators, they are very happy to make use of it and have been doing so for 30 years. Perhaps the key insight here is that systems need not be deterministic to be useful. And we should aware that “put the interface into sleep state” is more strict requirement than the “bandwidth adjustment”: You should make sure all the services from each headend are not passing the sleeping links, and WILL NOT the passing the sleeping links, or else there will be service disrupt during the sleeping procedures. Sorry, I cannot parse this. Again, we do not seek an absolute solution that forces all traffic away from power-save capable links unconditionally. That’s not the point. We seek to consolidate traffic within TE constraints, and then if components are vacated, place them in power-sleep. Without coordination of the LSPs requirements on each headend, when will you end the “network-wide polarization” process and begin the sleeping management procedures, which is the integral part of the overall proposal, but the authors avoid touching it? LSP optimization is an ongoing periodic process. It does not end. Sleep management is an ongoing periodic process. It does begin or end. Ron has already described sleep management. Regards, Tony
_______________________________________________ Lsr mailing list -- [email protected] To unsubscribe send an email to [email protected]
