IPFIX Vendor Specific Information Elements
draft-bryant-ipfix-vendor-ie-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Stewart Bryant , Ganesh Sadasivan | ||
| Last updated | 2003-10-03 | ||
| 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
Both IPFIX and PSAMP need methods whereby vendors can add proprietary information elements (IEs) to data flowsets. This draft proposes two possible methods of providing vendor specific IEs. The extension of these methods to provide vendor specific scope and options is also described.
Authors
Stewart Bryant
Ganesh Sadasivan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)