[IPFIX] Fwd: New Version Notification for draft-ietf-ipfix-mediation-protocol-05.txt

Benoit Claise <bclaise@cisco.com> Fri, 28 June 2013 02:13 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A62A11E8145 for <ipfix@ietfa.amsl.com>; Thu, 27 Jun 2013 19:13:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.759
X-Spam-Level:
X-Spam-Status: No, score=-8.759 tagged_above=-999 required=5 tests=[AWL=1.839, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NA3AhxpAXAc0 for <ipfix@ietfa.amsl.com>; Thu, 27 Jun 2013 19:13:54 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (av-tac-rtp.cisco.com [64.102.19.209]) by ietfa.amsl.com (Postfix) with ESMTP id 1655A21F9A12 for <ipfix@ietf.org>; Thu, 27 Jun 2013 19:13:54 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r5S2DqbD022662 for <ipfix@ietf.org>; Thu, 27 Jun 2013 22:13:52 -0400 (EDT)
Received: from [10.82.210.131] (rtp-vpn4-643.cisco.com [10.82.210.131]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r5S2Dk3j007571 for <ipfix@ietf.org>; Thu, 27 Jun 2013 22:13:47 -0400 (EDT)
Message-ID: <51CCF159.50101@cisco.com>
Date: Thu, 27 Jun 2013 22:13:45 -0400
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "ipfix@ietf.org" <ipfix@ietf.org>
References: <20130628020930.31612.47124.idtracker@ietfa.amsl.com>
In-Reply-To: <20130628020930.31612.47124.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20130628020930.31612.47124.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------090305080309070202090706"
Subject: [IPFIX] Fwd: New Version Notification for draft-ietf-ipfix-mediation-protocol-05.txt
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jun 2013 02:13:58 -0000

Hi,

A new version has been posted. It takes into account many points from 
Paul's feedback.
However, the latest points discussed on the mailing list today are not 
yet incorporated.

Regards, B.


-------- Original Message --------
Subject: 	New Version Notification for 
draft-ietf-ipfix-mediation-protocol-05.txt
Date: 	Thu, 27 Jun 2013 19:09:30 -0700
From: 	internet-drafts@ietf.org
To: 	Benoit Claise <bclaise@cisco.com>, Atsushi Kobayashi 
<akoba@nttv6.net>, Brian Trammell <trammell@tik.ee.ethz.ch>



A new version of I-D, draft-ietf-ipfix-mediation-protocol-05.txt
has been successfully submitted by Benoit Claise and posted to the
IETF repository.

Filename:	 draft-ietf-ipfix-mediation-protocol
Revision:	 05
Title:		 Operation of the IP Flow Information Export (IPFIX) Protocol on IPFIX Mediators
Creation date:	 2013-06-27
Group:		 ipfix
Number of pages: 28
URL:             http://www.ietf.org/internet-drafts/draft-ietf-ipfix-mediation-protocol-05.txt
Status:          http://datatracker.ietf.org/doc/draft-ietf-ipfix-mediation-protocol
Htmlized:        http://tools.ietf.org/html/draft-ietf-ipfix-mediation-protocol-05
Diff:            http://www.ietf.org/rfcdiff?url2=draft-ietf-ipfix-mediation-protocol-05

Abstract:
    This document specifies the operation of the IP Flow Information
    Export (IPFIX) protocol specific to IPFIX Mediators, including
    Template and Observation Point management, timing considerations, and
    other Mediator-specific concerns.

                                                                                   


The IETF Secretariat