50 likes | 201 Views
65th IETF Meeting – March 2006 IPPM Working Group. IPPM Framework & ISP measurement … exchange. Emile Stephan. Presentation Overview. History & Methodology ISP measurement result exchange. History & Methodology. 1995 IPPM Bof, "IP Provider Metrics" RFC2330 framework covers
E N D
65th IETF Meeting – March 2006 IPPM Working Group IPPM Framework & ISP measurement … exchange Emile Stephan
Presentation Overview • History & Methodology • ISP measurement result exchange
History & Methodology • 1995 • IPPM Bof, "IP Provider Metrics" • RFC2330 framework covers • Active method • Passive is not excluded (see sections 5,10.2 & 17) • Spatial composition (sect 9.1) • How to measure, what to report • IPPM WG effort covers • E2E metrics including p2mp (multimetrics draft) • Composition of e2e metrics only • Point to address to satisfy IP Provider Measurement needs • How to report ? • spatial decomposition to integrate passive metrics in composition
Framework for composition • Segments one-way delay + context (segment, accuracy, sync ok…) • Results acceptable /error uncertainty… • Temporal aggregation • One way delay Composition • Segment one-way delay computed • Type-P-One-way-Delay-* from [RFC2679] or [RFC3432]; • Or Type-P-One-way-Delay-Composition-* [composition draft]; • Type-P-subpath-One-way-Delay-* [multimetric draft] ; • Same apply for packet loss and jitter whenever applicable
Framework for ISP measure result exchange ISP1 ISP2 ISP3 Segment: A B C D E F <-----------------------> <------------------------> <-------------><----------------> Owd MetricID: subpath(34) e2e(6) composition(35) Results: dAB, dCD, dEF Exchange: records (results, metric ID, segment, begin, end, sync status…) Composition: Allowed combination of metricID defined in composition draft : DelayAF for the period t0tf ~ Compagg( (34, dAB, ~t0, ~tf, ok), (6, dCD, ~t0, ~tf, ok), (35, dEF, ~t0, ~tf, ok)) Data model: Metric ID from IPPM Metric Registry (see RFC4148) Result, Begin, end, segment...: FieldID from IPFIX, PSAMP data model