IETF 62 NSIS WG1 Porgress Report: Metering NSLP (M-NSLP) Georg Carle, Falko Dressler, Changpeng Fan, Ali Fessi, Cornelia Kappler, Andreas Klenk, Juergen Quittek, Hannes Tschofenig 62th IETF meeting, NSIS WG

IETF 62 NSIS WG2 Motivation Problem: Measuring properties of a specific IP traffic flow along its path through the Internet  identifying sources of delay, jitter and loss n delay and jitter per hop n number of dropped packets per hop  at several routers  in several domains Domain 1Domain 2Domain 3 Domain 4

IETF 62 NSIS WG3 Already Known Solutions (1) Active measurements: traceroute and ping  does not measure the flow of interest but another artificial flow Massive passive measurement: measure all flows in the network at all routers in all domains  very high overhead n overloading core routers n huge amount of data to be transported, stored and searched Domain 1Domain 2Domain 3 Domain 4

IETF 62 NSIS WG4 Already Known Solutions (2) Selective passive measurement: configure measurement for the flow individually by a management tool  much leaner, much less data  central coordination of individual measurements  full topology and routing information required for coordination  still a high management and coordination overhead Domain 1Domain 2Domain 3 Domain 4

IETF 62 NSIS WG5 Path-coupled signaling Sending signaling message along the data path  same basic idea as RSVP uses for QoS signaling  each router on the path receives a request for measuring a specified data flow  non-supportive routers just ignore the message Data collection to  (a) per-domain databases  (b) case-by-case-specified database  (c) along data path back to requesting party Domain 1Domain 2Domain 3 Domain 4 (c) (a) (b)

IETF 62 NSIS WG6 (pID,t k ) i NiNi NeNe NcNc (pID,t k ) e collector signaling traffic of interest (pID,t k ) c Web access Example: Intra-domain Measurement

IETF 62 NSIS WG7 Advantages Topology and routing information not required  automatically only routers on the data path are configured  reduced measurements overhead Relatively low signaling overhead Filter specification allows exact measurement of specific traffic flow  even at high speed link, measurement without sampling possible n also precise loss and jitter measurement possible  lower probability of packet ID collisions n further increases by also reporting packet length Low amount of data to be stored in database Measuring byte loss and packet loss MP i MP e MP k collector (pID,t k,M j ) i (pID,t k,M j ) e Wasteful reporting traffic Traffic being correctly measured Traffic being observed but not measured

IETF 62 NSIS WG8 Current Activities  2 Internet Drafts:  “Framework for Metering NSLP” (New I-D) n Presents shortly the whole context of Metering and Measurement n Presents different scenarios for path-coupled configuration of MEs n Collects requirements for a path-coupled configuration protocol of MEs Discusses the applicability of NSIS for this purpose  “NSLP for Metering Configuration Signaling” n Protocol Design n M-Spec  Prototype already implemented.  Team increased to 8 people from 4 organizations

IETF 62 NSIS WG9 Considered Scenarios  Accounting  Configure the MNEs dynamically and distribute Correlation-ID  QoS Monitoring  Loss, delay, jitter along the path  Monitoring for Security

IETF 62 NSIS WG10 Metering Compoments ME: Metering Entity MP: Monitoring Probe ME MP exported monitoring data ME MP ME MP Collector Metering Records data flows

IETF 62 NSIS WG11 Metering Components  Monitoring Probe (MP)  an entity that examines the data flow in order to gather Metering Data.  This Metering Data is exported to an Metering Entity (ME)  Metering Entity (ME)  An ME produces Metering Data describing the resource utilization of a particular flow or service.  Typically, this information is collected from associated monitoring probes.  Collector  A collector receives Metering Data from one or multiple Metering Entities.  This Metering Data is aggregated, correlated, and stored in form of Metering Records.

IETF 62 NSIS WG12 Metering Framework  Exported data  Statistics about the data flows n e.g. number of observed packets per flow, timestamps  Sampled packets or packet digests (hash value)  Export protocols  Netflow, IPFIX/PSAMP, …  Parameters to be configured  Data flows to be measured (can be identified, e.g. using IP 5-tuples)  What to meter/measure: n Number of packets/octets n Duration of data flows n Samples of packets n Collector-ID (to which Collector the data should be sent to) n etc.

IETF 62 NSIS WG13 Protocol Design  Message Types: n CONFIGURE n RESPONSE n QUERY n NOTIFY  Example of Operation  M-Spec is derived from the NAT/Firewall NSLP  Flexible information model MNI MNF CONFIGURE MNF CONFIGURE MNR CONFIGURE RESPONSE

IETF 62 NSIS WG14 Shall this become a NSIS WG work item?