1 / 12

Observatory Requirements Strawman

Observatory Requirements Strawman. Matt Zekauskas, matt@internet2.edu Measurement SIG Fall 2006 Member Meeting Monday, 4-Dec-2006. June 2006. Small group traded email… and a concall Dan Magorian Joe Metzger Jeff Boote Eric Boyd Matt Zekauskas

audra
Download Presentation

Observatory Requirements Strawman

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. Observatory Requirements Strawman Matt Zekauskas, matt@internet2.edu Measurement SIG Fall 2006 Member Meeting Monday, 4-Dec-2006

  2. June 2006 • Small group traded email… and a concall • Dan Magorian • Joe Metzger • Jeff Boote • Eric Boyd • Matt Zekauskas • Result was a “v0.0” requirements document that needs iteration • Possibly as a WG under NTAC auspices

  3. Obligatory Pointer • http://measurement.internet2.edu/docs/ Observatory-2006-06-05-v0.0a.pdf

  4. Don’t Break Anything • Keep existing Observatory capabilities

  5. Potential (New) Focus Areas • Technology Issues • Is it working? How well? How debug problems? • Economy Issues – interdomain circuits • How are they used? Are they used effectively? Monitor violation of any rules (e.g. for short-term circuits) • Compare with “vanilla” IP services?

  6. Big Goals? • Extend research datasets to new equipment • Circuit “weathermap”; optical proxy • Auditing Circuits • Who requested (at suitable granularity) • What for? (ex: bulk data, streaming media, experiment control) • Why? (add’l bw, required characteristics, application isolation, security)

  7. Consumer Statistics • What might a consumer want to know? • Availability stats (per ckt, per segment, periodically, available seconds, unavailable seconds (planned, unplanned (equip? human?) • Error stats (pre/post FEC, if triggers maint) • Usage (creation, hold times, errors)

  8. Diagnostics • Auditing (ckt creation, teardown, errors, utilization if possible) • Ability to trace to find dysfunctional link (link setup packets, passive tap) • Ability to identify and track rate policing (or rate limiting, or rate mismatches)

  9. Quality Control • Circuit Statistics (setup times, call blocking times/rates, teardown time, in-service bit or packet error rates, in-service circuit failure rates) • Packet statistics for standard IP/Ethernet links (rates, loss, latency, jitter, utilization) • Periodic active tests (setup-test-teardown; tests ctl plane, ports (vary), attenuate to look for boundary conditions)

  10. Economy: Currency • How is it handed out? • Is it traded? If so, trade stats • Are credits stored? If so, how much • “Burn rate”

  11. Economy: Health (growing? Shrinking? Trends?) • Supply measurement • Demand measurement • Demand characterization (more granular than connector) • Which university or research group? • Purpose? (research/app/testing/offload other link) • Economy rules violations?

More Related