Hi lsr-wg, green-wg, et al.,

The authors of draft-many-lsr-power-group-02 
(<https://datatracker.ietf.org/doc/draft-many-lsr-power-group/>) have requested 
early code-point allocation. As this is normally done after WG adoption we 
would like to move forward on that front first.

The GREEN wg chairs have expressed interest in this draft as far as not wanting 
to be developing at cross-purposes with the work from GREEN.

A proposed way forward that came from discussions between the LSR and GREEN 
chairs and ADs would be for LSR to adopt this document as experimental and move 
it forward with the addition of some text. The text would state that work is on 
going in the IETF to define a broad power framework and that future solutions 
may be proposed to incorporate this work.

Additionally, GREEN is asking the authors to review the green framework draft 
(<https://datatracker.ietf.org/doc/draft-bcmj-green-power-and-energy-yang/>) 
and attempt to align where possible, and avoid incompatabilty if possible 
(e.g., consider terminology and hierarchy where different).

If the work is adopted then LSR would request constructive review and feedback 
from GREEN for any changes that can be made to improve the LSR work with the 
goal of moving the work forward.

The LSR chairs and ADs believe the intention of the authors is to get solution 
quickly deployed to start making immediate progress on power saving. The 
interest from GREEN WG is that if we do this we indicate it’s an experimental 
approach and we make an effort to allow for later solutions that would 
incorporate the more comprehensive framework that they are working on.

Additionally, it has been pointed out that GREEN WG should be able to benefit 
from the real-world experience gained from deployments of the experiment LSR 
RFC.

This email services as an opportunity to raise concerns with this plan to move 
forward.

Thanks,
Lsr Chairs.
_______________________________________________
Lsr mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to