Open Capture Format (OCF)
draft-bullen-ocf-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Robert Bullen | ||
Last updated | 2001-02-08 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Many protocol analyzer users and vendors have identified the need for an open, standards-based trace file format that allows free and easy exchange of captured data, whether it originates from a data network or otherwise. This document outlines the requirements of such a file format and a proposal that satisfies them--the Open Capture Format (OCF).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)