Observatory Requirements Strawman

Matt Zekauskas, matt@internet2.edu Measurement SIG

Fall 2006 Member MeetingMonday, 4-Dec-2006

2 Matt Zekauskas

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 Matt Zekauskas

Obligatory Pointer

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

4 Matt Zekauskas

Don’t Break Anything

• Keep existing Observatory capabilities

5 Matt Zekauskas

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 Matt Zekauskas

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 Matt Zekauskas

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 Matt Zekauskas

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 Matt Zekauskas

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 Matt Zekauskas

Economy: Currency

• How is it handed out?

• Is it traded? If so, trade stats

• Are credits stored? If so, how much

• “Burn rate”

11 Matt Zekauskas

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?

12 Matt Zekauskas