Hi Benoit,
>> There is no tracking of interfaces in power-state-off, nor of interfaces >> that are power-state-on but have not formed an adjacency. There is no >> tracking of power state of higher levels of hardware. Presumably when all >> relevant interfaces are sleeping, the platform can put higher level hardware >> to sleep. Once again, we are not trying to perform management plane >> functions, only control plane traffic engineering. > You know, this is exactly my point. And I have seen this pattern in the past. > "It's just routing, not mgmt, so we don't care" That’s grossly unfair. We do care. But we also have other requirements. We are proposing to carry this information in the IGP, as we have done for TE information for 30 years. However, the IGP is not a limitless storage system. In fact, it has a very finite capacity and the more that we add to it, the more it degrades IGP performance. We are carrying the information that we need in the IGP to do routing’s job. We have no objection to the GREEN YANG model and support that effort, but carrying YANG in the IGP does not make sense. > Operators don't manage the control plane or the management plane (or the data > plance) independently.. > They look at all planes (mgmt, control, data) for troubleshooting, anomaly > detection, and assurance. See the NMOP "sharing your incidents" sessions. > And yes, we could map, as an example, a BGP Flowspect Type 1 - Destination > Prefix > <https://www.rfc-editor.org/info/rfc8955/#name-type-1-destination-prefix> to > destinationIPv4Prefix ... oh wait, maybe this is destinationIPv6Prefix? > Explained differntly, here is the issue we face in operations: "Network > Automation: the costly Data Models Integration and Mediation > <https://www.claise.be/network-automation-and-the-costly-data-model-integration-mediation/>" This may surprise you, but I do understand that. I do have some history as a network operator (USC, Los Nettos, NTT). > I really would like to understand (see described somewhere) how an operator > would use the LSR power groups, optimize routing, and use the YANG module > power state at the same time. To me, this would be a prerequisite before > adopting. Please see draft-many-teas-power-steering. > Btw, a specific operator told me: config management is so complex, with many > frozen windows, that I will not allow energy-related configuration > independently. No one is proposing that. All configuration changes are all part of normal system configuration. Tony
_______________________________________________ Lsr mailing list -- [email protected] To unsubscribe send an email to [email protected]
