1 / 18

Internet2 Measurement Perspective

Internet2 Measurement Perspective. Guy T. Almes Matt Zekauskas SD Measurement Workshop June, 1999. General Goal of Internet2. Support advanced applications High bandwidth flows Low latency Low loss Advanced services Multicast Quality of service guarantees.

heba
Download Presentation

Internet2 Measurement Perspective

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Internet2 Measurement Perspective Guy T. Almes Matt Zekauskas SD Measurement Workshop June, 1999

  2. General Goal of Internet2 • Support advanced applications • High bandwidth flows • Low latency • Low loss • Advanced services • Multicast • Quality of service guarantees

  3. ‘My application has a problem’ • Application, End-host, Network? • Passive measurements could help divide the problem • Consistent measurements throughout Internet2 infrastructure could help diagnose network problems

  4. Backbone ‘A’ Backbone ‘B’

  5. Backbone ‘A’ Backbone ‘B’

  6. Backbone ‘A’ Backbone ‘B’

  7. Other Measurement Goals • (Forward) network engineering • Enable network research • Feedback to applications • Operational data • performance, flows, anomalies • Network characterization • how used? load response? SLS?

  8. Measurement Classification • Utilization [usually SNMP] • Active measurements • ~Performance (one-way delay, loss, throughput) • Passive measurements • ~Traffic characterization • Routing [usually BGP/traceroute]

  9. Utilization • Technically “easy”; “boring” • Coordinate type, frequency… and reporting • A small number of frequency multiples • 15 sec, 1 min, 4 min

  10. Utilization II • Standardize file format • Single access mode • Example: relative URL for routers • Example: single I2 measurement page

  11. Active measurements • delay • loss • throughput? (don’t want to interfere with apps) • my point of view: approximately Surveyor, +(?) throughput • Packet sizes? Distribution?

  12. Passive Measurements • Question: how apply passive measurements effectively in a consistent fashion? • Something that is useful to all? • Each additional probe adds value? • Perhaps flow data • What about packet headers? And security...

  13. Routing • Can’t just measure one point: policy • E-E measurements: • surveyor • AMP • consistency/access problems a-la utilization • RA? Routing protocol sniffing? Traceroute observatories?

  14. Examples • Remote microscope • UDP, blasting packets • OCxMON shows more packets than capacity • Videoconference from Lund to Pittsburgh • Packet loss… don’t know why

  15. Desires • Want some way to know where loss occurs when it happens (or delay) • Advanced service debugging • Multicast • QoS (QBone designing measurement in) • Service level specification conformance

  16. Desires • Application reflectors along with routers? (Is this measurement?)

  17. Summary • Consistent measurement of • Utilization • Performance • Traffic Characterization • That are made generally available • In support of applications and the networks themselves

  18. www.internet2.edu TM

More Related