[IPFIX] Fwd: New Version Notification for draft-claise-ipfix-protocol-rfc5101bis-01.txt
Benoit Claise <bclaise@cisco.com> Mon, 26 September 2011 13: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 9494021F8A69 for <ipfix@ietfa.amsl.com>; Mon, 26 Sep 2011 06:13:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.481
X-Spam-Level:
X-Spam-Status: No, score=-2.481 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 01inrMfxyenq for <ipfix@ietfa.amsl.com>; Mon, 26 Sep 2011 06:13:09 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 1D4A321F8A35 for <ipfix@ietf.org>; Mon, 26 Sep 2011 06:13:07 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p8QDFltq013320; Mon, 26 Sep 2011 15:15:47 +0200 (CEST)
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p8QDFgrT006556; Mon, 26 Sep 2011 15:15:42 +0200 (CEST)
Message-ID: <4E807AFE.8010604@cisco.com>
Date: Mon, 26 Sep 2011 15:15:42 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2
MIME-Version: 1.0
To: "ipfix@ietf.org" <ipfix@ietf.org>
References: <20110926130703.4979.26742.idtracker@ietfa.amsl.com>
In-Reply-To: <20110926130703.4979.26742.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20110926130703.4979.26742.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------030208010200020905050902"
Cc: Thomas Dietz <Thomas.Dietz@nw.neclab.eu>
Subject: [IPFIX] Fwd: New Version Notification for draft-claise-ipfix-protocol-rfc5101bis-01.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: Mon, 26 Sep 2011 13:13:09 -0000
Dear all, Trying to close on the recent discussion on the mailing list, I posted a new draft, including the feedback from everybody. Please review and comment. The diffs are at: http://tools.ietf.org/rfcdiff?difftype=--hwdiff&url2=draft-claise-ipfix-protocol-rfc5101bis-01.txt Note that there is this pending AUTH48 changes for [IPFIX-CONF]: the addition of selectorId, exportingProcessId, and meteringProcessId in the configuration data model, as state parameters, i.e. read-only. Only 2 to-do items, as far as I can tell: - NTP RFC 1305 is obsoleted by RFC5905. Check if the format is the similar before updating the reference. - Resolution to the template lifetime mechanism for UDP Regards, Benoit -------- Original Message -------- Subject: New Version Notification for draft-claise-ipfix-protocol-rfc5101bis-01.txt Date: Mon, 26 Sep 2011 06:07:03 -0700 From: internet-drafts@ietf.org To: bclaise@cisco.com CC: bclaise@cisco.com A new version of I-D, draft-claise-ipfix-protocol-rfc5101bis-01.txt has been successfully submitted by Benoit Claise and posted to the IETF repository. Filename: draft-claise-ipfix-protocol-rfc5101bis Revision: 01 Title: Specification of the IP Flow Information eXport (IPFIX) Protocol for the Exchange of IP Traffic Flow Information Creation date: 2011-09-26 WG ID: Individual Submission Number of pages: 69 Abstract: This document specifies the IP Flow Information Export (IPFIX) protocol that serves for transmitting IP Traffic Flow information over the network. In order to transmit IP Traffic Flow information from an Exporting Process to an information 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
- [IPFIX] Fwd: New Version Notification for draft-c… Benoit Claise