In revision 2023-10-16 the performance-data container (based on the container-performance-type grouping) has 2 performance counters which seem to be duplicates:
fragmented-frames-input
fragmented-frames-ingress (introduced in #52)
Is there a difference or can one of them be eliminated?
Decision during the 5G-xhaul call at 10th of January 2024:
The comment at the ContainerPerformanceType::fragmentedFramesInput : Integer attribute shall be changed from
"Total number of fragmented frames received at this interface."
to
"The total number of frames received that were less than 64 octets in length (excluding framing bits but including FCS octets) and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error)."
The ContainerPerformanceType::fragmentedFramesIngress : Integer attribute shall be deleted from the modelling.
In revision 2023-10-16 the
performance-data
container (based on thecontainer-performance-type
grouping) has 2 performance counters which seem to be duplicates:fragmented-frames-input
fragmented-frames-ingress
(introduced in #52)Is there a difference or can one of them be eliminated?