S. Handelman, S. Stibler, N. Brownlee, and G. Ruth, "RTFM: New attributes for traffic flow measurement," Request for Comments 2724, Oct. 1999. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
DNS Root/gTLD Performance Measurements - Brownlee, claffy, Nemeth (2001) (6 citations) (Correct)
....rates for the global root servers. Even so, our New Zealand data correlates well with that collected at San Diego. Our traffic meter [3] 6] 7] 8] is an open source implementation of the IETF s Realtime Traffic Flow Measurement (RTFM) architecture for network traffic flow measurement [9] 10] [11]. It is a highly configurable, passive, real time link measurement tool, and has been extended to use the CoralReef library [4] to read packet headers from either a live network or from a trace file. We used the traffic meter to measure response times for the global DNS root and gTLD nameservers ....
S. Handelman, S. Stibler, G. Ruth, RTFM: New Attributes for Traffic Flow Measurement, RFC 2724, October 1999
Deriving Traffic Demands for Operational IP.. - Feldmann.. (2000) (78 citations) (Correct)
....prohibitively expensive. In addition, traffic engineering does not necessarily need to operate at the small time scale of individual packets. Instead, we propose that flow level statistics should be collected at each ingress link. These measurements can be collected directly by the incident router [15, 16]. A flow is defined as a set of packets that match in the key IP and TCP UDP header fields (such as the source and destination addresses, and port numbers) and arrive on the same ingress link. The router should generate a record summarizing the traffic statistics on a regular basis, either after ....
S. Handelman, S. Stibler, N. Brownlee, and G. Ruth, "RTFM: New attributes for traffic flow measurement." Request for Comments 2724, October 1999.
Deriving Traffic Demands for Operational IP.. - Feldmann.. (2000) (78 citations) (Correct)
....prohibitively expensive. In addition, traffic engineering does not necessarily need to operate at the small time scale of individual packets. Instead, we propose that flow level statistics should be collected at each ingress link. These measurements can be collected directly by the incident router [14, 15]. A flow is defined as a set of packets that match in the key IP and TCP UDP header fields (such as the source and destination addresses, and port numbers) and arrive on the same ingress link. The router should generate a record summarizing the traffic statistics on a regular basis, either after ....
S. Handelman, S. Stibler, N. Brownlee, and G. Ruth, "RTFM: New attributes for traffic flow measurement." Request for Comments 2724, October 1999.
Unknown - Self-citation (Brownlee) (Correct)
No context found.
Handelman, S., Stibler, S., Brownlee, N. and G. Ruth, "RTFM: New Attributes for Traffic Flow Measurement", RFC 2724, October 1999.
NetFlow: Information loss or win? - Robin Sommer And (Correct)
No context found.
S. Handelman, S. Stibler, N. Brownlee, and G. Ruth, "RTFM: New attributes for traffic flow measurement," Request for Comments 2724, Oct. 1999.
Provisioning IP Backbone Networks Based on Measurements - Papagiannaki (2003) (Correct)
No context found.
S. Handelman, S. Stibler, N. Brownlee, and G. Ruth, "RTFM: New attributes for traffic flow measurement," RFC 2724, Oct. 1999.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC