Hi Vijay, Jan, Let me give some update on the performance metrics. We continued our discussions on this document. For example, during the weekly meeting yesterday, some of the authors (Luis, Sabine, and I) discussed the potential impact of Prometheus ( https://prometheus.io/docs/prometheus/latest/), which is used in related context, on the draft. For example, we looked at the list of statistics from Prometheus (min, max, avg, stddev, stdvar, quintile, topk, bottomk) to compare with our list. We found that there are design points from Prometheus which we may consider in future work but keep the simplicity of the current design. We will upload an update by the end of next week before the July 13 deadline.
Any comments are greatly welcome! Richard On Wed, Jul 1, 2020 at 11:42 PM Vijay Gurbani <vijay.gurb...@gmail.com> wrote: > Folks: There are three drafts that we need to progress: path vector, > performance metrics, and unified properties. > > Jan and I will like to get a clear idea from the authors of each of these > documents as to where things stand. > > The WG list has been rather silent on progress on the drafts. For unified > properties, Sabine had posted an email on Jun-10, but there has not been > anything else on that draft since. > > Performance metrics saw some action on the WG list on May-17, but that is > it. > > I don't see anything for path vector. > > Can we kindly have the authors of the draft please put forward where they > are and whether the work is done enough to start WGLC on them.. Please do > so ASAP. > > Thanks, > > - vijay > _______________________________________________ > alto mailing list > alto@ietf.org > https://www.ietf.org/mailman/listinfo/alto > -- Richard
_______________________________________________ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
