Ron,
Thanks for the note.  I'll keep a list.
John
    On Friday, September 11, 2026 at 08:41:35 AM PDT, Bonica, Ron 
<[email protected]> wrote:  
 
 John,
I think that you are raising some interesting questions about the sleep 
management component. Among them are:
   
   - What the criteria for putting an interface to sleep?  
   
   - Is persistent low utilization among them? If so, how persistent and how 
low.
   - Is the total absence of LSPs among them?
   - Can the local node determine whether the sleep criteria are satisfied?
   
   - What are the criteria for waking up an interface?
   
   - Is increasing utilization among them? If so, how big an increase and over 
what period of time?
   - Is an upstream node’s inability to compute a path due to bandwidth 
scarcity among them?
   - Is a warning about upcoming load among them?
   - Can the local node determine whether the wake-up criteria are satisfied?

While these are interesting questions, they are questions about the sleep 
management component and are beyond the scope of this document.
                                         Ron

Get Outlook for Mac
From: John Drake <[email protected]>
Date: Thursday, September 10, 2026 at 10:07 AM
To: John Drake <[email protected]>; TEAS WG <[email protected]>; lsr 
<[email protected]>; Bonica, Ron <[email protected]>; Barth, Colby 
<[email protected]>
Subject: Re: [Teas] Re: [Lsr] Fw: I-D Action: 
draft-many-teas-power-steering-02.txt

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 toput a "link to sleep" in coordination with the node on 
the other end.  This isa 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/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-many-teas-power-steering-02.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-many-teas-power-steering-02

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]
  
_______________________________________________
Lsr mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to