[RM Ch04] Metrics to be considered about anuket-specifications HOT 2 CLOSED

For table 3-8 (and also table 3-14), that's right that network throughput metrics must be associated to some specific conditions such as max allowed packet drop rate, but also frame/packet size and flow number. Moreover, those metrics, as well as latency-related and flow-related metrics, also depends on the path (eg N/S or E/W) and the processing type (eg w/ or w/o L4 statefull filtering) applied to the traffic.
So, that relevant question implies another one :
Which metric associated condition must be considered at which level (ie ref model, ref archi, ref implem or test program) ?

Regarding HyperThreading (or rather Simultaneous MultiThreading), it is related to NFVI HW profile (cf release 1 chapter 6), and it could also be considered in table 3-6 as an NFVI capability, but probably with a different wording: for example, it could be a precision on the capability "cpu pinning" which would be either "no", "dedicated physical core(s)" or "dedicated logical core(s)". In that case, a new issue occurs because 2 different options are possible for C and N instance types, so we would have 2 variants of C and N instance types...
Anyway, that is another relevant question, which would require other opinions.

from anuket-specifications.

Packet drop rate no longer referenced in RM documents

Hyperthreading is explicitly referenced in the NFVI profile types.

Thus, closing this issue as addressed.

from anuket-specifications.