Packet Reordering Metrics

Abstract

Packet Reordering Metrics Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Benchmarking Virtual Switches in the Open Platform for NFV (OPNFV)

“…o Methodology for IP Multicast Benchmarking [RFC3918] o Packet Reordering Metrics [RFC4737] As one might expect, the most fundamental internetworking characteristics of throughput and latency remain important when the switch is virtualized, and these benchmarks figure prominently in the specification.…”

Real-Time Traffic over the Cognitive Packet Network

“…However the reordering buffer at the receiver is necessarily of finite length, so that packets arriving to a buffer that is full will be discarded, and packets will have to be forwarded after a given time-out even when their predecessors have not arrived in order to avoid excessive time gaps with their predecessors that have already been played back. Packet reordering is done according to the recommendation from [20], which is based on the monotonic ordering of sequence numbers. Specifically, we add a 4-byte field in the CPN header to store the unique sequence identifier which is incremented by 1 each time a new packet is sent into a traffic flow.…”

“…Real-time needs for enhanced reality and telepresence [17] are also creating specific needs in on-line QoS management for multimedia systems [18]. Thus in the past decade, many QoS approaches have been proposed including IntServ & RSVP, DiffServ and MPLS, which specify a coarse-grained mechanism for providing QoS, but fully satisfactory results are not yet available in this area and there is space for further investigation and research [19][20][21].…”

RFC 4148 and the IP Performance Metrics (IPPM) Registry of Metrics Are Obsolete

“…This memo updates all previous memos that registered new metrics, including [RFC4737] and [RFC5560], so that the registry's Obsolete status will be evident.…”