You seem to be asking about a problem that the draft is not trying to
address.
Yours,
Joel
On 9/10/2026 1:40 PM, John Drake wrote:
Hi,
I don't think it's sufficient to locally decide at a particular point
in time whether to power on or off a link based upon its utilization.
So, the first question is whether, at a particular point in time, it
is possible to pre-empt particular LSPs, in such a way that their
traffic is not interrupted, while not pre-empting other LSPs? And
adjust the link's power status accordingly?
The second question is whether it is poosible to anticipate the advent
if traffic on a given link so that its is fully powered on before the
traffic arrives.
Thanks,
John
On Thursday, September 10, 2026 at 07:18:55 AM PDT, Tony Li
<[email protected]> wrote:
Hi John,
I’m quite sure he did. Which part did you not understand?
Tony
On Sep 10, 2026, at 7:05 AM, John Drake
<[email protected]> wrote:
Hi,
I'm not sure you answered my questions.
Thanks,
John
On Thursday, September 10, 2026 at 05:37:26 AM PDT, Barth, Colby
<[email protected]> wrote:
Inline <cB>
-- Colby
*From: *John Drake <[email protected]>
*Date: *Wednesday, September 9, 2026 at 3:24 PM
*To: *TEAS WG <[email protected]>; lsr <[email protected]>; Bonica, Ron
<[email protected]>
*Subject: *[Teas] Re: [Lsr] Fw: I-D Action:
draft-many-teas-power-steering-02.txt
Ron,
I'm sure I missed it so I apologize in advance, but how do you deal
with a link which should be powered off but which can't be due to the
presence on LSPs which should be re-routed, or a link which appears
to be ready to power off but which shouldn't be because the LSPs on
it are crucial and which can't be rerouted?
<cb> If a link is both power-save-capable and there are currently no
LSPs traversing it, then it is a candidate to be put to power-sleep.
A node may make a local decision to put a "link tosleep" in
coordination with the node on the other end. This is a function of
the sleep management component that Ron has described and is beyond
the scope of this document.
Or, how do you power on a link in anticipation of a huge traffic
surge which should be non-disruptively handled?
<cb> Waking up a link can be triggered by an ingress node if it fails
to find a path for a new bandwidth request.
—Colby
Thanks,
John
On Wednesday, September 9, 2026 at 06:58:41 AM PDT, Bonica, Ron
<[email protected]> wrote:
Folks,
Many of the comments regarding draft-many-lsr-power-groups are
resolved in this teas document. So, I am informing LSR and TEAS that
this new version has been posted.
Ron
------------------------------------------------------------------------
*From:* [email protected] <[email protected]>
*Sent:* Wednesday, September 9, 2026 9:51 AM
*To:* [email protected] <[email protected]>
*Cc:* [email protected] <[email protected]>
*Subject:* [Teas] I-D Action: draft-many-teas-power-steering-02.txt
Internet-Draft draft-many-teas-power-steering-02.txt is now
available. It is a
work item of the Traffic Engineering Architecture and Signaling
(TEAS) WG of
the IETF.
Title: A Power Conserving Path Placement Strategy (PCPPS)
Authors: Colby Barth
Tony Li
Vishnu Pavan Beeram
Ron Bonica
Name: draft-many-teas-power-steering-02.txt
Pages: 13
Dates: 2026-09-09
Abstract:
This document introduces a Power Conserving Path Placement Strategy
(PCPPS). During periods of low demand, PCPPS concentrates traffic
onto a small set of network resources. This causes other network
resources to become idle or nearly idle. When demand increases,
PCPPS redistributes traffic as required.
The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-many-teas-power-steering/
<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-many-teas-power-steering/__;!!NpxR!mw3pWRU0THOTHq_Gm0h_fyVEWfVEAVaG5R7PLc0rSZikxQ701T8gpkdSQ2MgNEz7I4McJgECsRbSI3tt35852B57dzY9sVCTXQ$>
There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-many-teas-power-steering-02.html
<https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-many-teas-power-steering-02.html__;!!NpxR!mw3pWRU0THOTHq_Gm0h_fyVEWfVEAVaG5R7PLc0rSZikxQ701T8gpkdSQ2MgNEz7I4McJgECsRbSI3tt35852B57dzafLYY_Kw$>
A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-many-teas-power-steering-02
<https://urldefense.com/v3/__https://author-tools.ietf.org/iddiff?url2=draft-many-teas-power-steering-02__;!!NpxR!mw3pWRU0THOTHq_Gm0h_fyVEWfVEAVaG5R7PLc0rSZikxQ701T8gpkdSQ2MgNEz7I4McJgECsRbSI3tt35852B57dzam9GzmKg$>
Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts
_______________________________________________
Teas mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
Lsr mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
Teas mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
Teas mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
Teas mailing list [email protected]
To unsubscribe send an email [email protected]
_______________________________________________
Lsr mailing list -- [email protected]
To unsubscribe send an email to [email protected]
