Dear all,

Since this draft has been mentioned in the "Adoption of draft-many-lsr-power-group" email thread, and since draft-many-lsr-power-group is referenced, I thought about forwarding this message to LSR.

Regards, Benoit (on behalf of the authors)


-------- Forwarded Message --------
Subject: [Green] Fwd: New Version Notification for draft-claise-green-capability-discovery-01.txt
Date:   Thu, 10 Sep 2026 12:31:58 +0200
From:   [email protected] <[email protected]>
To:     [email protected] <[email protected]>
CC:     [email protected]



Dear all,

Here is an update to YANG Data Model for Power State Capability Discovery.

Changes since draft-claise-green-capability-discovery-00
- New sections: Applicability,, Applicability to the GREEN Use Cases, Open Issues - Added four per-Power-State transition-time leaves: typical-exit-time, max-exit-time, typical-entry-time, and max-entry-time (reintroducing the wake/transition-time concept that was absent in -00). - Removed the unit-multiplier leaf and the multiplier-based scaling; nominal-power and max-power are now fixed in Watts (uint32), to be aligned with draft-ietf-green-power-and-energy-yang - Distinguished nominal-power (expected operating draw) from max-power (rated per-state ceiling, the per-state counterpart of Nameplate Power), with max-power for power-state-on required not to exceed nameplate-power. - Clarified that the model is operational-state (config false) data in the operational datastore (NMDA-consistent). - Expanded the Operational Considerations: weigh exit/entry time against the Energy Saving

Thanks and regards, Benoit (on behalf of the co-authors)

-------- Forwarded Message --------
Subject: New Version Notification for draft-claise-green-capability-discovery-01.txt
Date:   Thu, 10 Sep 2026 03:27:52 -0700
From:   [email protected]
To: Benoit Claise <[email protected]>, Gen Chen <[email protected]>, Nils Warnke <[email protected]>, Nils Warnke <[email protected]>, Reshad Rahman <[email protected]>



A new version of Internet-Draft draft-claise-green-capability-discovery-01.txt
has been successfully submitted by Benoit Claise and posted to the
IETF repository.

Name: draft-claise-green-capability-discovery
Revision: 01
Title: A YANG Data Model for Power State Capability Discovery
Date: 2026-09-10
Group: Individual Submission
Pages: 25
URL: https://www.ietf.org/archive/id/draft-claise-green-capability-discovery-01.txt Status: https://datatracker.ietf.org/doc/draft-claise-green-capability-discovery/ HTML: https://www.ietf.org/archive/id/draft-claise-green-capability-discovery-01.html HTMLized: https://datatracker.ietf.org/doc/html/draft-claise-green-capability-discovery Diff: https://author-tools.ietf.org/iddiff?url2=draft-claise-green-capability-discovery-01

Abstract:

This document defines a YANG data model that augments the system
capabilities model of RFC 9196 to allow a network element to
advertise, per hardware Component, the set of Power States that the
Component supports, together with a static characterization of each
such state: the expected and maximum Power the Component draws in it,
and the time to enter and exit it.

This capability model complements the operational Power and Energy
data model defined in the GREEN Power and Energy YANG module, which
reports the current Power State and the measured Power of a
Component, but not which Power States are available, how much Power
each draws, or how long transitions between them take. It is
anchored to the hardware inventory of RFC 8348, reuses the Power
State identities of the GREEN Power and Energy model, and, because it
is static, may be provided at implementation time as YANG instance
data per RFC 9195 so that an Energy Management System can learn a
platform's Power State capabilities before the equipment is deployed
or even powered on.



The IETF Secretariat

_______________________________________________
Green 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