Hello,
Not sure if this is the right list for this type of message ...
I am developing an IPFIX exporter. It exports IP flows, and I'd like now
to export some extra information (strings) about the machines on the LAN
(the hostname of the machine, and others information ...)
What is the right
Riccardo Bernardini framefri...@gmail.com wrote:
This came to my mind while reading: why not embedding the archive in
the text with some special line header that makes automatic
extraction possible?
Like RCF 6716.
Tony.
--
f.anthony.n.finch d...@dotat.at http://dotat.at/
Forties,
Hi, Thierry,
Have a look in the IANA information element registry
(http://www.iana.org/assignments/ipfix) to see if there are existing IEs for
the information you want to export.
Hostnames, I think, are not there -- in general, IPFIX exporters deal in
addresses taken from observed packets
That's 20 minutes per person of course.
--
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194 | Fax:
This messages provides the details for the random selection of
the ten voting members of the 2013-14 Nomcom.
We will once again be using the publicly verifiable random algorithm
specified in RFC 3797. This message contains both the timeline for
performing the publicly verifiable selection
Hi, everyone,
We are short of our goal of 200 volunteers for the upcoming nomcom.
Please do volunteer. Our publicly verifiable random algorithm has fully
adequate entropy for a flood of volunteers - more names, more names, more
names, more brains --- er, oops, not yet a zombie.
The more
Folks,
In keeping with the WG Charter, draft-ietf-lisp-deployment should be labeled
EXPERIMENTAL, not INFORMATIONAL. For supporting information, please see the
following milestone in the LISP Charter:
- Sep 2012 Submit a deployment model document to the IESG for publication
as an
The IESG has received a request from the Locator/ID Separation Protocol
WG (lisp) to consider the following document:
- 'LISP Network Element Deployment Considerations'
draft-ietf-lisp-deployment-08.txt as Informational RFC
The IESG plans to make a decision in the next few weeks, and solicits
The IESG has approved the following document:
- 'RTP Control Protocol (RTCP) Extended Report (XR) Block for De-Jitter
Buffer Metric Reporting'
(draft-ietf-xrblock-rtcp-xr-jb-14.txt) as Proposed Standard
This document is the product of the Metric Blocks for use with RTCP's
Extended Report
The IESG has approved the following document:
- 'RTP Control Protocol (RTCP) Extended Report (XR) Block for Discard
Count metric Reporting'
(draft-ietf-xrblock-rtcp-xr-discard-15.txt) as Proposed Standard
This document is the product of the Metric Blocks for use with RTCP's
Extended Report
The IESG has approved the following document:
- 'Session Description Protocol (SDP) Extension For Setting Audio and
Video Media Streams Over Circuit-Switched Bearers In The Public
Switched Telephone Network (PSTN)'
(draft-ietf-mmusic-sdp-cs-21.txt) as Proposed Standard
This document is
Hi all,
Based on discussions during IETF 86, we are trialing an IETF mentoring
program. During this trial period, we would like to pair newcomers (people who
have attended 3 or fewer meetings or have registered as students) with existing
IETF participants. The goal is to provide a
This messages provides the details for the random selection of
the ten voting members of the 2013-14 Nomcom.
We will once again be using the publicly verifiable random algorithm
specified in RFC 3797. This message contains both the timeline for
performing the publicly verifiable selection
Hi, everyone,
We are short of our goal of 200 volunteers for the upcoming nomcom.
Please do volunteer. Our publicly verifiable random algorithm has fully
adequate entropy for a flood of volunteers - more names, more names, more
names, more brains --- er, oops, not yet a zombie.
The more
14 matches
Mail list logo
