Re: [ippm] Adoption call for draft-olden-ippm-qoo-02

[LUIS MIGUEL CONTRERAS MURILLO <[e-mail]>]

Hi Charis, all,

Apologies for answering late to this adoption call. I support the adoption of the draft since it seems to be a useful mechanism for deriving probabilistic insight on the expected performance of applications.

From my review, there are some comments that I would like to be addressed by the authors:


  *   The draft is positioned as a kind of extension or complementary work of BBF TR-452.1. However, the development of the proposed ideas in the draft refer to distribution of percentile values of latency. Thus, in my understanding, whatever technique that could generate such latency distribution could work (e.g., any monitoring system). In other words, it is not clear to me if the solution can be claimed as generic and independent of BBF TR-452.1 (now, for instance, are claims such as “The foundation of the framework is Quality Attenuation”).
  *   Not clear to me the use and need of measuring the throughput. The examples are also unclear in that respect.
  *   The lowest threshold of the quality boundaries is called Network Requirement for Perfection (NRP). This marks the baseline on the performance, in other words, it refers to the behavior of the application on “ideal conditions”. That ideal conditions essentially mean the behavior observed without any impairment from the network. That is, no latency nor packet loss coming from the network, in a kind of performance observed in a back-to-back running of the application between its endpoints. Once impairments are introduced, the application performance will begin to degrade. In summary, such “perfection” correspond in fact to “ideal conditions”. The performance under ideal conditions can be maintained to some extent even when some impairments (latency, packet loss) are introduced. The NRP as described on the examples includes some latency and some packet loss, so it would be interesting to have as reference how far NRP is from ideal conditions. This is because NRP does not actually represents the 100% reference, but something lower than that. This is important to fix the expectations of the application user’s against how robust are the applications respect to the network effects.
  *   How compatible is this approach with adaptative applications? That applications are able to react to network conditions changing the NRP and NRPoU references dynamically.
  *   The paragraph about Volatile Networks of section 7 seems to be a subsection, so probably requires to be numbered as 7.1
  *   Section 9 is probably not needed.

Thanks,

Best regards

Luis

De: ippm <[e-mail]> En nombre de Tommy Pauly
Enviado el: martes, 16 de enero de 2024 18:13
Para: IETF IPPM WG ([e-mail]) <[e-mail]>
Asunto: [ippm] Adoption call for draft-olden-ippm-qoo-02

Hello IPPM,

This email starts a working group adoption call for "Quality of Outcome” (draft-olden-ippm-qoo).

https://datatracker.ietf.org/doc/draft-olden-ippm-qoo/
https://www.ietf.org/archive/id/draft-olden-ippm-qoo-02.html

The call will last for 3 weeks, and end on Tuesday, February 6. Please reply to this email with your review comments and indicate if you support adopting this work.

Please note that we did a previous adoption call that did not receive sufficient feedback. At the last meeting at IETF 118, we did have a good amount of comments and questions, so please do reply to this email if you have reviewed the document.

Thanks,
Tommy & Marcus

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is confidential and privileged information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição