[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: ispmon BOF
[Non-member submission from Simon Leinen <simon@limmat.switch.ch>]
Here is the initial agenda for the ispmon BOF.
As you see, only 60 minutes of the 120 minute slot have been allocated
so far. Maybe the rest is for open discussion. But it could also be
a possibility for others to provide their input, so we might want to
consider presenting something (I don't know what).
--
Simon.
--=-=-=
Content-Type: message/rfc822
Content-Disposition: inline
X-From-Line: procmail Thu Jul 3 07:50:47 2003
Received: from psg.com ([147.28.0.62])
by central.switch.ch with esmtp (Exim 3.20 #1)
id 19XwzW-0000i7-00
for simon@limmat.switch.ch; Thu, 03 Jul 2003 07:50:46 +0200
Received: from lserv by psg.com with local (Exim 4.14)
id 19XwyF-0005a0-8E
for psamp-data@psg.com; Thu, 03 Jul 2003 05:49:27 +0000
Received: from [208.30.172.76] (helo=smtp-out.sprintlabs.com)
by psg.com with esmtp (Exim 4.14)
id 19XwyB-0005Yw-Qo; Thu, 03 Jul 2003 05:49:23 +0000
Received: from mailman.sprintlabs.com (mx.sprintlabs.com [199.2.53.192])
by smtp-out.sprintlabs.com (Postfix) with ESMTP
id 46112B8102; Wed, 2 Jul 2003 22:49:36 -0700 (PDT)
Received: by mailman.sprintlabs.com with Internet Mail Service (5.5.2656.59)
id <MY197DBV>; Wed, 2 Jul 2003 22:48:53 -0700
Message-ID: <49D9473417F1234C9C86886EE8353FAAEFF693@mailman.sprintlabs.com>
Subject: ispmon BOF
Date: Wed, 2 Jul 2003 22:48:52 -0700
X-Mailer: Internet Mail Service (5.5.2656.59)
Sender: owner-psamp@ops.ietf.org
Precedence: bulk
X-Spam-Status: No, hits=-2.6 required=5.0
tests=BAYES_20
version=2.54
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.54 (1.174.2.17-2003-05-11-exp)
Lines: 117
Xref: babar lists.ietf.wg.psamp:219
MIME-Version: 1.0
[apologies if you receive multiple copies of this email]
please find attached the agenda and description of the
new BOF on Monitoring Infrastructure Deployment.
thanks,
gianluca
----------------------------------------------------------
Monitoring Infrastructure Deployment BOF (ispmon)
Thursday, July 17 at 1530-1730
===============================
CHAIR: Gianluca Iannaccone <gianluca@sprintlabs.com>
AGENDA
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
MAILING LIST
General Discussion: ispmon@ops.ietf.org
To Subscribe: ispmon-request@ops.ietf.org, "subscribe" in body
Archive: http://opt.ietf.org/lists/ispmon
DESCRIPTION
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
not been.
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
plane functionality).
. 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.,
READING LIST
. draft-bhattacharyya-monitoring-deployment-00.txt
. draft-bhattacharyya-monitoring-sprint-01.txt
. draft-ietf-ipfix-reqs-10.txt
. draft-ietf-psamp-framework-03.txt
. draft-ietf-idwg-requirements-10.txt
. draft-ietf-inch-iodef-01.txt
. RFC2330: Framework for IP Performance Metrics
RELATED WGs
IP Flow Information Export (ipfix)
http://www.ietf.org/html.charters/ipfix-charter.html
Packet Sampling (psamp)
http://www.ietf.org/html.charters/psamp-charter.html
IP Performance Metrics (ippm)
http://www.ietf.org/html.charters/ippm-charter.html
Intrusion Detection Exchange Format (idwg)
http://www.ietf.org/html.charters/idwg-charter.html
Extended Incident Handling (inch)
http://www.ietf.org/html.charters/inch-charter.html
----------------------------------------------------------
Gianluca Iannaccone ' gianluca@sprintlabs.com
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 psamp-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/psamp/>
--=-=-=--
--
to unsubscribe send a message to ispmon-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/ispmon/>