Subject: [IPFIX] Fwd: New Version Notification for draft-ietf-ipfix-protocol-rfc5101bis-09.txt

From: Brian Trammell <[email-masked]>
Date: Wed, 10 Jul 2013 16:01:40 +0200

Greetings, all,

We've submitted a new version of rfc5101bis, addressing IESG and ops-dir review comments. 

Best regards,

Brian

Begin forwarded message:

> From: [email-masked]
> Subject: New Version Notification for draft-ietf-ipfix-protocol-rfc5101bis-09.txt
> Date: 10 July 2013 15:55:51 GMT+02:00
> To: Benoit Claise <[email-masked]>, Brian Trammell <[email-masked]>
> 
> 
> A new version of I-D, draft-ietf-ipfix-protocol-rfc5101bis-09.txt
> has been successfully submitted by Benoit Claise and posted to the
> IETF repository.
> 
> Filename:	 draft-ietf-ipfix-protocol-rfc5101bis
> Revision:	 09
> Title:		 Specification of the IP Flow Information eXport (IPFIX) Protocol for the Exchange of Flow Information
> Creation date:	 2013-07-10
> Group:		 ipfix
> Number of pages: 72
> URL:             http://www.ietf.org/internet-drafts/draft-ietf-ipfix-protocol-rfc5101bis-09.txt
> Status:          http://datatracker.ietf.org/doc/draft-ietf-ipfix-protocol-rfc5101bis
> Htmlized:        http://tools.ietf.org/html/draft-ietf-ipfix-protocol-rfc5101bis-09
> Diff:            http://www.ietf.org/rfcdiff?url2=draft-ietf-ipfix-protocol-rfc5101bis-09
> 
> Abstract:
>   This document specifies the IP Flow Information Export (IPFIX)
>   protocol that serves for transmitting Traffic Flow information over
>   the network. In order to transmit Traffic Flow information from an
>   Exporting Process to a Collecting Process, a common representation of
>   flow data and a standard means of communicating them is required.
>   This document describes how the IPFIX Data and Template Records are
>   carried over a number of transport protocols from an IPFIX Exporting
>   Process to an IPFIX Collecting Process. This document obsoletes RFC
>   5101.
> 
> 
> 
> 
> The IETF Secretariat