Thats a unique idea.You should consider the following idea to enhance your idea so that it would impact uniquely:  consider the definition of the expedited forwarding per-hop behavior (EF PHB) as given in RFC 2598 and its impact on worst case end-to-end delay jitter. On the one hand, the definition in RFC 2598 can be used to predict extremely low end-to-end delay jitter, independent of the network scale. On the other hand,  find that the worst case delay jitter can be made arbitrarily large, while each flow traverses at most a specified number of hops, if  allow networks to become arbitrarily large; this is in contradiction with the previous statement.  analyze where the contradiction originates and find the explanation. It resides in the fact that the definition in RFC 2598 is not easily implementable in schedulers  know of, mainly because it is not formal enough, and also because it does not contain an error term.  propose a new definition for the EF PHB, called "packet scale rate guarantee" (PSRG) that preserves the spirit of RFC 2598 while allowing a number of reasonable implementations and has very useful properties for per-node and end-to-end network engineering.  show that this definition implies a rate-latency service curve property.  also show that it is equivalent, in some sense, to the stronger concept of "adaptive service guarantee." Then  propose some proven bounds on delay jitter for networks implementing this new definition, both in cases without loss and with loss.
['Jon C. R. Bennett', 'K. Benson', 'Anna Charny', 'William F. Courtney', 'Jean-Yves Le Boudec']
I am writing a research paper on a idea Delay jitter bounds and packet scale rate guarantee for expedited forwarding
[{"from": "human", "value": "I am writing a research paper on a idea Delay jitter bounds and packet scale rate guarantee for expedited forwarding"}, {"from": "gpt", "value": "Thats a unique idea.You should consider the following idea to enhance your idea so that it would impact uniquely:  consider the definition of the expedited forwarding per-hop behavior (EF PHB) as given in RFC 2598 and its impact on worst case end-to-end delay jitter. On the one hand, the definition in RFC 2598 can be used to predict extremely low end-to-end delay jitter, independent of the network scale. On the other hand,  find that the worst case delay jitter can be made arbitrarily large, while each flow traverses at most a specified number of hops, if  allow networks to become arbitrarily large; this is in contradiction with the previous statement.  analyze where the contradiction originates and find the explanation. It resides in the fact that the definition in RFC 2598 is not easily implementable in schedulers  know of, mainly because it is not formal enough, and also because it does not contain an error term.  propose a new definition for the EF PHB, called \"packet scale rate guarantee\" (PSRG) that preserves the spirit of RFC 2598 while allowing a number of reasonable implementations and has very useful properties for per-node and end-to-end network engineering.  show that this definition implies a rate-latency service curve property.  also show that it is equivalent, in some sense, to the stronger concept of \"adaptive service guarantee.\" Then  propose some proven bounds on delay jitter for networks implementing this new definition, both in cases without loss and with loss."}]