Traffic flow (computer networking)
||This article may require cleanup to meet Wikipedia's quality standards. The specific problem is: This article may require cleanup to meet Wikipedia's quality standards. No cleanup reason has been specified. Please help improve this article if you can; the talk page may contain suggestions. (March 2017) (Learn how and when to remove this template message)|
In packet switching networks, traffic flow, packet flow or network flow is a sequence of packets from a source computer to a destination, which may be another host, a multicast group, or a broadcast domain. RFC 2722 defines traffic flow as "an artificial logical equivalent to a call or connection." RFC 3697 defines traffic flow as "a sequence of packets sent from a particular source to a particular unicast, anycast, or multicast destination that the source desires to label as a flow. A flow could consist of all packets in a specific transport connection or a media stream. However, a flow is not necessarily 1:1 mapped to a transport connection." Flow is also defined in RFC 3917 as "a set of IP packets passing an observation point in the network during a certain time interval."
Packet flow temporal efficiency can be affected by one-way delay (OWD) that is described as a combination of the following components:
- Processing delay (the time taken to process a packet in a network node)
- Queing delay (the time a job waits in a queue until it can be executed)
- Transmission delay (the amount of time necessary to push all the packet into the wire)
- Propagation delay (amount of time it takes the signal’s header to travel from the sender to the receiver)
||This section does not contain any content.|
Utility for network administration
The concept is important, since it may be that packets from one flow need to be handled differently from others, by means of separate queues in switches, routers and network adapters, to achieve traffic shaping, fair queueing or Quality of Service. It is also a concept used in Queueing Network Analyzers (QNAs) or in packet tracing.
Applied to Internet routers, a flow may be a host-to-host communication path, or a socket-to-socket communication identified by a unique combination of source and destination addresses and port numbers, together with transport protocol (for example, UDP or TCP). In the TCP case, a flow may be a virtual circuit, also known as a virtual connection or a byte stream.
Packet flow can be represented as a path in a network to model network performance. For example, a water flow network can be used to conceptualize packet flow. Channels can be thought of as pipes, with the pipe capacity corresponding to bandwidth and flows corresponding to data throughput. This visualization can help to understand bottlenecks, queuing, and help understand the unique requirements of tailored systems.
- Argus - Audit Record Generation and Utilization System
- Cisco NetFlow
- Communication channel
- Data flow (software engineering)
- Data stream
- Flow control
- Traffic shaping
- Traffic policing (communications)
- Flow network in graph theory
- IP Flow Information Export
- Path (graph theory)
- Stream (computing)
- Telecommunication connection
- Traffic generation model
- N. Brownlee; C. Mills & G. Ruth (October 1999). "RFC 2722 - Traffic Flow Measurement: Architecture". IETF. Retrieved 2010-02-11.
- J. Rajahalme, A. Conta, B. Carpenter and S. Deering (March 2004). "RFC 3697 - IPv6 Flow Label Specification". IETF. Retrieved 2010-02-11.
- J. Quittek; JT. Zseby; B. Claise & S. Zander (October 2004). "RFC 3917 - IPFIX Requirements". IETF. Retrieved 2010-02-11.
- "What is nodal delay?". networkengineering.stackexchange.com.