[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[apologies if you receive multiple copies of this email]
please find attached the agenda and description of the
new BOF on Monitoring Infrastructure Deployment.
Monitoring Infrastructure Deployment BOF (ispmon)
Thursday, July 17 at 1530-1730
CHAIR: Gianluca Iannaccone <email@example.com>
5 min - Agenda Bashing
15 min - Presentation: draft-bhattacharyya-monitoring-deployment-00
10 min - Presentation: Sprint's Continuous Monitoring (CMON) project
15 min - Scope and candidate charter for Working group
15 min - Next steps
General Discussion: firstname.lastname@example.org
To Subscribe: email@example.com, "subscribe" in body
Various types of measurement data need to be collected to support
monitoring applications. We classified them in two broad categories:
(i) aggregate information that need to be collected at coarse time-scales
and reported on a regular basis (e.g. SNMP, flows, routing tables) ;
(ii) packet-level traces to analyze and understand a specific phenomenon.
There are a number of implementation challenges in order to capture,
process, summarize and export data at the required level of granularity
at the time that it is needed. Some of these problems are being
addressed in different IETF working groups whereas some others have
The goal of this BOF is to discuss whether a new working group is needed
to undertake the following activities: (i) define a framework for
monitoring needed to support day-to-day operations in IP networks, (ii)
identify existing and on-going efforts in the IETF on various aspects of
the framework and ensure that this work guarantees inter-operability
among ISPs, and (iii) provide clear guidelines to equipment vendors on
what infrastructure is needed to support monitoring in ISP networks.
A charter for the new working group could address (but not be limited to)
the following aspects:
. provide BCP documents on how to instrument monitoring systems in
large-scale provider networks.
. describe known-to-work implementations and identify open issues.
. specify components of an operational monitoring infrastructure
in particular regarding aspects not addressed in other IETF WGs
(e.g., storage, aging and analysis of collected data, control
. specify ways for ISPs to share monitoring data.
. make recommendations to other working groups standardizing different
elements of monitoring, e.g., IPPM, IPFIX and PSAMP, INCH, IDWG, etc.,
. RFC2330: Framework for IP Performance Metrics
IP Flow Information Export (ipfix)
Packet Sampling (psamp)
IP Performance Metrics (ippm)
Intrusion Detection Exchange Format (idwg)
Extended Incident Handling (inch)
Gianluca Iannaccone ' firstname.lastname@example.org
Sprint ATL ' tel +1 (650) 375-4198
1 Adrian Court ' fax +1 (650) 375-4079
Burlingame, CA 94010 ' www.sprintlabs.com/~gianluca
to unsubscribe send a message to email@example.com with
the word 'unsubscribe' in a single line as the message text body.