Hey Gunter, > It doesn’t make sense to have Application specific values if a particular metric is obtained only dynamically,
It sure does. Please notice what ASLA RFCs say up front in the abstract. ASLA is useful for: A) application- specific values for a given attribute AND B) indication of which applications are using the advertised value for a given link. It does not matter if the value is same or different ... what matters is automated and consistent indication which of my applications given new metric applies to. I already mentioned this to Ron here: https://mailarchive.ietf.org/arch/msg/lsr/OgGLI8yezUDWU-EZePoIj6y6ENk/ Can anyone explain how do I map generic metric to selected network applications I am to run in the network ? Thx, Robert. On Fri, Jul 30, 2021 at 11:05 AM Van De Velde, Gunter (Nokia - BE/Antwerp) < [email protected]> wrote: > A little late in the discussion... (PTO events do happen) > > a quick opinion on the below discussion on whether Generic metric sub-tlv > should be encoded on a ASLA or not. > For me, it depends on how the metric for the corresponding metric-type is > obtained and if it can be configured (static). > It doesn’t make sense to have Application specific values if a particular > metric is obtained only dynamically, for eg, dynamically measured delay is > going to be same for all applications. > On the contrary, te-metric can be configured, and we can in principle > configure different values for different applications. > > My opinion is that if any of the metric-types in the Generic metric > sub-tlv can be configured, it should be inside the ASLA. > > G/ > >
_______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
