54th IETF Meeting - Packet Sampling BOF (psamp)
agenda@ietf.org Thu, 11 July 2002 21:10 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06413; Thu, 11 Jul 2002 17:10:12 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id RAA27307 for ietf-123-outbound.10@ietf.org; Thu, 11 Jul 2002 17:05:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id LAA23973 for <all-ietf@loki.ietf.org>; Thu, 11 Jul 2002 11:54:44 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22150; Thu, 11 Jul 2002 11:53:49 -0400 (EDT)
Message-Id: <200207111553.LAA22150@ietf.org>
To: IETF-Announce:;
From: agenda@ietf.org
cc: new-work@ietf.org
Subject: 54th IETF Meeting - Packet Sampling BOF (psamp)
Date: Thu, 11 Jul 2002 11:53:49 -0400
Sender: dinaras@cnri.reston.va.us
Packet Sampling BOF (psamp) Tuesday, July 16 at 0900-1130 ============================== CHAIR: Nick Duffield <duffield@research.att.com> Provisional Agenda: - Welcome and Agenda Review - Review of Draft Charter - Discussion of Draft Framework: draft-duffield-framework-papame Mailing Lists: General Discussion:psamp@ops.ietf.org To Subscribe: psamp-request@ops.ietf.org In Body: subscribe Archive: https://ops.ietf.org/lists/psamp/ Description of Working Group: The Packet Sampling working group is chartered to define a standard set of capabilities for network elements to sample packets. The capabilities should be simple enough that they can be implemented ubiquitously at maximal line rate. They should be rich enough to support a range of existing and emerging measurement-based applications, and other IETF working groups where appropriate. The focus of the WG will be to (i) specify a set of selection operations by which packets are sampled; (ii) specify the information that is to be made available for reporting on sampled packets; (iii) describe protocols by which information on sampled packets is reported to applications; (iv) describe protocols by which packet selection and reporting configured. Packet reports must be communicable in a timely manner, to applications either on-board of off-board the sampling network element. The streams of packet reports produced by a packet sampling must (i) allow consistent interpretation, independent of the particular network element that produced them; (ii) be self-defining, in that their interpretation does not require additional information to be supplied by the network element; (iii) allow robustness of interpretation with respect to missing reports or part of reports; Network elements shall support multiple parallel packet samplers, each with independently configurable packet selectors, reports, report streams, and export. Network elements must allow easy and secure reconfiguration of these packet samplers by on-board or external applications. Network elements and collectors must together be able to ensure that transmission of packet reports across a network path is aware of congestion, and take measures to avoid congestion, in compliance with RFC 2914. Selection of the content of packet reports will be cognizant of privacy and anonymity issues while being responsive to the needs of measurement applications. Re-use of existing protocols will be encouraged provided the protocol capabilities are compatible with PSAMP requirements. Specifically, the tasks of the PSAMP WG will be the following: 1. Selectors for packet sampling. Define the set of primitive packet selection operations for network elements, and the ways in which they can be combined. 2. Packet Information. Specify extent of packet that is to be made available for reporting. Target for inclusion the packet's IP header, some subsequent bytes of the packet, and encapsulating headers if present. Specify variants for IPv4 and IPv6, extent of IP packet available under encapsulation methods, and under packet encryption. 3. Sampled packet reports. Define the format of the report that is constructed by the network element for each sampled packet for communication to applications. The format shall be sufficiently rich as to allow inclusion in the packet report of (i) IP packet information as specified in paragraph 2 above; (ii) encapsulating packet headers as specified in paragraph 2 above; (iii) interface or channel identifiers associated with transit of the packet across the network element; (iv) quantities computable from packet content and router state, (v) quantities computed during the selection operation. All reported quantities must reflect the router state and configuration encountered by the packet in the network element. 4. Report Streams. Define a format for a stream of packet reports, to include: (i) the format of packet reports in the stream; (ii) the packet reports themselves; (iii) configuration parameters of the selectors of the packets reported on; (iv) configuration parameters and state information of the network element; (v) quantities that enable collectors and applications to infer of attained packet sampling rates, detect report loss in transmission, and correct for information missing from the packet report stream. 5. Multiple Report Streams. Define requirements for multiple parallel packet samplers in one network element, including the allowed degradation of packet reporting when packets are selected by multiple packet samplers. 6. Configuration and Management. Define a packet sampler MIB to reside at the network element, including parameters for packet selection, packet report and stream format, and export. Select or define a communication protocol to configure/read this MIB. 7. Presentation, Export, and Transport of Packet Reports. Define interface for presentation of reports to on-board applications. Select transport protocol for remote export that is compatible with PSAMP goals. Determine requirements on measurement device and collector for use of selected transport protocol, while being aware of and responsive to network congestion. Initial Internet-Draft: A Framework for Passive Packet Measurement <draft-duffield-framework-papame> Goals and Milestones: AUG 02 Submit Framework document NOV 02 Submit Packet selector and packet information document FEB 03 Submit Report format and report stream format document MAY 03 Submit Export and requirements for collectors document AUG 03 Submit MIB document