Flow (Internet Protocol): Difference between revisions
Jump to navigation
Jump to search
imported>Howard C. Berkowitz No edit summary |
imported>Howard C. Berkowitz No edit summary |
||
| Line 1: | Line 1: | ||
While the [[Internet Protocol]] is [[connectionless]], capacity planning of networks needs an understanding of aggregate traffic, which is commonly defined in measurement of '''flows'''. At a minimum, a flow is identified by a source and destination IP address; it may be further refined by information such as IP protocol identifier, and [[Transmission Control Protocol|TCP]] or [[User Datagram Protocol|UDP]] source and destination port numbers. Yet additional distinctions may be made among flows based on their [[quality of service]] flags. | While the [[Internet Protocol]] is [[connectionless]], capacity planning of networks needs an understanding of aggregate traffic, which is commonly defined in measurement of '''flows'''. At a minimum, a flow is identified by a source and destination IP address; it may be further refined by information such as IP protocol identifier, and [[Transmission Control Protocol|TCP]] or [[User Datagram Protocol|UDP]] source and destination port numbers. Yet additional distinctions may be made among flows based on their [[quality of service]] flags. | ||
[[Internet Protocol flow export]] is the general term for methods to collect and report flow statistics.<ref name=RFC3917>{{citation | [[Internet Protocol flow information export]] is the general term for methods to collect and report flow statistics.<ref name=RFC3917>{{citation | ||
| author = Quittek, J., Zseby, T., Claise, B., and S. Zander, | | author = Quittek, J., Zseby, T., Claise, B., and S. Zander, | ||
| title = Requirements for IP Flow Information Export | | title = Requirements for IP Flow Information Export | ||
Revision as of 21:01, 22 February 2009
While the Internet Protocol is connectionless, capacity planning of networks needs an understanding of aggregate traffic, which is commonly defined in measurement of flows. At a minimum, a flow is identified by a source and destination IP address; it may be further refined by information such as IP protocol identifier, and TCP or UDP source and destination port numbers. Yet additional distinctions may be made among flows based on their quality of service flags.
Internet Protocol flow information export is the general term for methods to collect and report flow statistics.[1]
References
- ↑ Quittek, J., Zseby, T., Claise, B., and S. Zander, (October 2004), Requirements for IP Flow Information Export, RFC 3917