1. NSLP for Metering Configuration Signaling (Metering NSLP)
draft-dressler-nsis-metering-nslp-00 (update of …accounting-nslp-00)
Falko Dressler, Georg Carle, Changpeng Fan, Cornelia Kappler, Hannes Tschofenig

2. Outline What does a Metering NSLP do? What is in the Draft?
What do we learn from it for current NSIS work?
Next Steps

3. What does a Metering NSLP do?
Dynamic configuration of Metering Entities (ME)
Application scenarios
Monitoring
Charging
Intrusion Detection
Configuration Data includes
What Metering Entities should participate in the metering
What to meter
Where to send metered data
Use e.g. ipfix to send metered data
Correlation identifier for metered data
ME not participating
Initial GIMPS signaling ME ME ME ME ME
Participating ME
GIMPS Messaging Associations

4. What is in the Draft Scenarios Requirements
Why solve the problem with NSIS
Basic protocol design
Comparison with other NSLPs
Impact on GIMPS API

5. What do we learn from it for current NSIS work? (I)
Structurally, M-NSLP similar to QoS-NSLP
CONFIGURE, QUERY, RESPONSE, NOTIFY
Differences
Must be possible for Metering Entities to pull out of a signaling session
And, upon a configuration update, to re-enter later
Similar to NATFW NSLP, when only NATs should be included
Interaction of Metering Entities
E.g. want exactly two entities measuring delay; Signaling message needs to carry information on how many entities have already been found

6. What do we learn from it for current NSIS work? (II)
Impact on GIMPS API
M-NSLP processing must be able to tell GIMPS not to install a messaging association, but to pull out of the signaling chain for this session
Also needed by NAT-FW, supported by Source-SII-Handle
When configuration of ongoing session is changed, other / more Metering Entities may need to be included in the signaling chain.
NI tells GIMPS that a rerouting event occurred
GIMPS should however not use this information to warn other M-NSLP sessions or other NSLPs!

7. Next Steps More details on configuration information
Use it to validate basic protocol design