Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Traffic policing (communications)
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== Effects == The recipient of traffic that has been ''policed'' will observe [[packet loss]] distributed throughout periods when incoming traffic exceeded the contract. If the source does not limit its sending rate (for example, through a [[#Impact on Congestion-Controlled Sources|feedback mechanism]]), this will continue, and may appear to the recipient as if [[link errors]] or some other disruption is causing random packet loss. The received traffic, which has experienced policing en route, will typically comply with the contract, although [[jitter]] may be introduced by elements in the network downstream of the policer. With reliable protocols, such as [[Transmission Control Protocol|TCP]] as opposed to [[User Datagram Protocol|UDP]], the dropped packets will not be acknowledged by the receiver, and therefore will be resent by the emitter, thus generating more traffic. === Impact on congestion-controlled sources === Sources with feedback-based [[congestion control]] mechanisms (for example [[Transmission Control Protocol|TCP]]) typically adapt rapidly to static policing, converging on a rate just below the policed sustained rate.{{Citation needed|date=November 2013}} <!-- The sentence below seems to be off-topic with respect to the title of this section. Also, the reference that might help verify it is not publicly accessible (reserved to IEEE members)--> Co-operative policing mechanisms, such as packet-based discard<ref>Design and applications of ATM LAN/WAN adapters. Bonjour, D.; De Hauteclocque, G.; Le Moal, J. ATM, 1998. ICATM-98., IEEE International Conference, 22-24 Jun 1998 Page(s):191 - 198 Digital Object Identifier 10.1109/ICATM.1998.688177</ref> facilitate more rapid convergence, higher stability and more efficient resource sharing. As a result, it may be hard for endpoints to distinguish TCP traffic that has been merely policed from TCP traffic that has been [[traffic shaping|shaped]]. === Impact in the case of ATM === Where [[cell relay|cell]]-level dropping is enforced (as opposed to that achieved through packet-based policing) the impact is particularly severe on longer packets. Since cells are typically much shorter than the maximum packet size, conventional policers discard cells which do not respect packet boundaries, and hence the total amount of traffic dropped will typically be distributed throughout a number of packets. Almost all known [[ATM Adaptation Layer 5#Convergence, segmentation, and reassembly|packet reassembly]] mechanisms will respond to a missing cell by dropping the packet entirely, and consequently a very large number of packet losses can result from moderately exceeding the policed contract.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)