Hi Srihari, It seems that the complexity why this procedure is proposed lies in suggestion to exchange those 4 messages:
*SleepPrepareAck 1 Receiver accepts preparationSleepPrepareNak 2 Receiver rejects preparation* *GoSleep 3 Sender authorizes power-sleepGoSleepAck 4 Receiver confirms power-sleep* In respect to the first reply the draft just says this: " If it cannot participate, it continues to be in Operating mode and sends negative acknowledgement. If it can participate, it sends acknowledgement and transitions to Ready mode." What are the criteria the receiver should use to make the above judgement ? Also how is this related to timing of flooding "sleep capable" state for a link in ISIS ? Should Sender even attempt to send anything to the peer here if there was no indication in flooding that specific interface of specific power group is sleep capable ? Or is that flooding to start after SleepPrepare Ack ? Not clear. Now what happens after sending GoSleep and never receiving the GoSleepAck ? Last but not least ... why for this p2p communication would one use the RSVP protocol ? Couldn't those indications be instead part of ISIS new Hello Capabilities Les is proposing ? Kind regards, Robert On Sun, Oct 4, 2026 at 5:55 AM Sangli, Srihari Ramachandra <srihari.sangli= [email protected]> wrote: > Here is a draft that provides additional info for power state > coordination, many people on both LSR and TEAS may be interested in > reviewing this. Please let us know comments. > > Thanks & Regards, > > srihari… (on behalf of my co-authors) > > *From: *[email protected] <[email protected]> > *Date: *Wednesday, 30 September 2026 at 11:59 PM > *To: *Vishnu P. Beeram <[email protected]>; Colby Barth < > [email protected]>; Ron Bonica <[email protected]>; Ronald Bonica < > [email protected]>; Sangli, Srihari Ramachandra <[email protected]>; > Tony Li <[email protected]>; Vishnu Beeram <[email protected]> > *Subject: *New Version Notification for draft-many-teas-rsvp-power-00.txt > > A new version of Internet-Draft draft-many-teas-rsvp-power-00.txt has been > successfully submitted by Srihari Sangli and posted to the > IETF repository. > > Name: draft-many-teas-rsvp-power > Revision: 00 > Title: Power Transition Framework for TE Resources > Date: 2026-09-30 > Group: Individual Submission > Pages: 12 > URL: > https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-many-teas-rsvp-power-00.txt__;!!NpxR!mcr37WP1ugRQAo4d4DAe_6f1y9QdWV6e4vGDFbP5WRz6Wy-0SKjvqCdIftykJJknZ4QqpF4BEVTg0nTivEzyPeF5OUg$ > Status: > https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-many-teas-rsvp-power/__;!!NpxR!mcr37WP1ugRQAo4d4DAe_6f1y9QdWV6e4vGDFbP5WRz6Wy-0SKjvqCdIftykJJknZ4QqpF4BEVTg0nTivEzyHVWnfeA$ > HTML: > https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-many-teas-rsvp-power-00.html__;!!NpxR!mcr37WP1ugRQAo4d4DAe_6f1y9QdWV6e4vGDFbP5WRz6Wy-0SKjvqCdIftykJJknZ4QqpF4BEVTg0nTivEzymD70BJw$ > HTMLized: > https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-many-teas-rsvp-power__;!!NpxR!mcr37WP1ugRQAo4d4DAe_6f1y9QdWV6e4vGDFbP5WRz6Wy-0SKjvqCdIftykJJknZ4QqpF4BEVTg0nTivEzy3SauvGQ$ > > > Abstract: > > Traffic-engineered networks are commonly provisioned for peak demand. > However, during off-peak periods, some traffic-engineered resources > in the network may be lightly used. This leads to unnecessary power > consumption. A coordinated power transition can reduce power > consumption while preserving the control-plane and traffic- > engineering state needed to restore service safely. > > This document defines a generic power management framework for > coordinating power-sleep and wakeup transitions between adjacent > nodes. It defines the roles, resource scope, procedures, collision > handling, failure behavior, and traffic-engineering preservation > requirements. It then specifies an RSVP-TE signaling extension for > supporting the power management framework. > > > > The IETF Secretariat > > > _______________________________________________ > Lsr 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]
