From nobody Wed Jul 1 04:03:13 2015 Return-Path: X-Original-To: ipfix@ietfa.amsl.com Delivered-To: ipfix@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D42981B2E12 for ; Wed, 1 Jul 2015 04:03:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.266 X-Spam-Level: X-Spam-Status: No, score=-2.266 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RpNX7i_75nGo for ; Wed, 1 Jul 2015 04:03:10 -0700 (PDT) Received: from mx0b-000f0801.pphosted.com (mx0b-000f0801.pphosted.com [67.231.152.113]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4B441B2E11 for ; Wed, 1 Jul 2015 04:03:08 -0700 (PDT) Received: from pps.filterd (m0000700.ppops.net [127.0.0.1]) by mx0b-000f0801.pphosted.com (8.15.0.59/8.15.0.59) with SMTP id t61AjnRA003890; Wed, 1 Jul 2015 04:03:06 -0700 Received: from brmwp-exchub02.corp.brocade.com ([208.47.132.227]) by mx0b-000f0801.pphosted.com with ESMTP id 1vbj1m3bfp-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 01 Jul 2015 04:03:06 -0700 Received: from EMEAWP-EXMB11.corp.brocade.com (172.29.11.85) by BRMWP-EXCHUB02.corp.brocade.com (172.16.187.99) with Microsoft SMTP Server (TLS) id 14.3.123.3; Wed, 1 Jul 2015 05:03:03 -0600 Received: from [192.168.1.73] (172.16.180.50) by EMEAWP-EXMB11.corp.brocade.com (172.29.11.85) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Wed, 1 Jul 2015 13:02:59 +0200 Message-ID: <5593C8DD.1050408@brocade.com> Date: Wed, 1 Jul 2015 12:02:53 +0100 From: Paul Aitken User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: IETF IPFIX Working Group References: <20150701105722.3454.64946.idtracker@ietfa.amsl.com> In-Reply-To: <20150701105722.3454.64946.idtracker@ietfa.amsl.com> X-Forwarded-Message-Id: <20150701105722.3454.64946.idtracker@ietfa.amsl.com> Content-Type: multipart/alternative; boundary="------------060200090507070005020801" X-Originating-IP: [172.16.180.50] X-ClientProxiedBy: hq1wp-excas12.corp.brocade.com (10.70.38.22) To EMEAWP-EXMB11.corp.brocade.com (172.29.11.85) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.14.151, 1.0.33, 0.0.0000 definitions=2015-07-01_08:2015-06-30,2015-07-01,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1506180000 definitions=main-1507010167 Archived-At: Cc: Joel jaeggli Subject: [IPFIX] Fwd: New Version Notification for draft-ietf-ipfix-mib-variable-export-09.txt X-BeenThere: ipfix@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IPFIX WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jul 2015 11:03:13 -0000 --------------060200090507070005020801 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Dear All, here is an updated version of the draft which addresses the only feedback we received since the previous version. (See http://www.ietf.org/mail-archive/web/ipfix/current/msg07285.html) Changes: * Changed mibObjectValueOctetString in Template 601 in Figure 29 to variable length * Encoded Figure 31 with variable length elements and adjusted the overall Set length * Minor modification to the interface names in Table 6 to simplify redrawing Figure 31 * Updated Colin's affiliation and contact details Per Joel's email (*), this draft needs AD sponsored. Thanks, Paul * http://www.ietf.org/mail-archive/web/ipfix/current/msg07296.html -------- Forwarded Message -------- Subject: New Version Notification for draft-ietf-ipfix-mib-variable-export-09.txt Date: Wed, 1 Jul 2015 03:57:22 -0700 From: internet-drafts@ietf.org To: Colin McDowall , Juergen Schoenwaelder , Juergen Schoenwaelder , Benoit Claise , Paul Aitken , Paul Aitken , Benoit Claise , Colin McDowall A new version of I-D, draft-ietf-ipfix-mib-variable-export-09.txt has been successfully submitted by Paul Aitken and posted to the IETF repository. Name: draft-ietf-ipfix-mib-variable-export Revision: 09 Title: Exporting MIB Variables using the IPFIX Protocol Document date: 2015-07-01 Group: Individual Submission Pages: 76 URL: https://www.ietf.org/internet-drafts/draft-ietf-ipfix-mib-variable-export-09.txt Status: https://datatracker.ietf.org/doc/draft-ietf-ipfix-mib-variable-export/ Htmlized: https://tools.ietf.org/html/draft-ietf-ipfix-mib-variable-export-09 Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-ipfix-mib-variable-export-09 Abstract: This document specifies a way to complement IPFIX Data Records with Management Information Base (MIB) objects, avoiding the need to define new IPFIX Information Elements for existing Management Information Base objects that are already fully specified. An IPFIX Options Template and method are specified, which are used to export the extra information required to fully describe Simple Network Management Protocol (SNMP) MIB objects in IPFIX. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat --------------060200090507070005020801 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 7bit Dear All, here is an updated version of the draft which addresses the only feedback we received since the previous version.
(See http://www.ietf.org/mail-archive/web/ipfix/current/msg07285.html)

Changes:
  • Changed mibObjectValueOctetString in Template 601 in Figure 29 to variable length
  • Encoded Figure 31 with variable length elements and adjusted the overall Set length
  • Minor modification to the interface names in Table 6 to simplify redrawing Figure 31
  • Updated Colin's affiliation and contact details

Per Joel's email (*), this draft needs AD sponsored.

Thanks,
Paul


* http://www.ietf.org/mail-archive/web/ipfix/current/msg07296.html



-------- Forwarded Message --------
Subject: New Version Notification for draft-ietf-ipfix-mib-variable-export-09.txt
Date: Wed, 1 Jul 2015 03:57:22 -0700
From: internet-drafts@ietf.org
To: Colin McDowall <cmcdowal@brocade.com>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Benoit Claise <bclaise@cisco.com>, Paul Aitken <paitken@brocade.com>, Paul Aitken <paitken@brocade.com>, Benoit Claise <bclaise@cisco.com>, Colin McDowall <cmcdowal@brocade.com> 


A new version of I-D, draft-ietf-ipfix-mib-variable-export-09.txt
has been successfully submitted by Paul Aitken and posted to the
IETF repository.

Name:		draft-ietf-ipfix-mib-variable-export
Revision:	09
Title:		Exporting MIB Variables using the IPFIX Protocol
Document date:	2015-07-01
Group:		Individual Submission
Pages:		76
URL:            https://www.ietf.org/internet-drafts/draft-ietf-ipfix-mib-variable-export-09.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-ipfix-mib-variable-export/
Htmlized:       https://tools.ietf.org/html/draft-ietf-ipfix-mib-variable-export-09
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-ipfix-mib-variable-export-09

Abstract:
   This document specifies a way to complement IPFIX Data Records with
   Management Information Base (MIB) objects, avoiding the need to
   define new IPFIX Information Elements for existing Management
   Information Base objects that are already fully specified.

   An IPFIX Options Template and method are specified, which are used to
   export the extra information required to fully describe Simple
   Network Management Protocol (SNMP) MIB objects in IPFIX.

                                                                                  


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat


--------------060200090507070005020801-- From nobody Fri Jul 17 08:50:56 2015 Return-Path: X-Original-To: ipfix@ietfa.amsl.com Delivered-To: ipfix@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A43271A1BB0; Fri, 17 Jul 2015 08:50:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.912 X-Spam-Level: X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RGC3pLYORL20; Fri, 17 Jul 2015 08:50:54 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 645961A1B11; Fri, 17 Jul 2015 08:50:29 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 89052180204; Fri, 17 Jul 2015 08:46:49 -0700 (PDT) To: rick.hofstede@redsocks.nl, bclaise@cisco.com, trammell@tik.ee.ethz.ch, paitken@cisco.com X-PHP-Originating-Script: 1005:errata_mail_lib.php From: RFC Errata System Message-Id: <20150717154649.89052180204@rfc-editor.org> Date: Fri, 17 Jul 2015 08:46:49 -0700 (PDT) Archived-At: Cc: iesg@ietf.org, ipfix@ietf.org, rfc-editor@rfc-editor.org Subject: [IPFIX] [Errata Verified] RFC7011 (4396) X-BeenThere: ipfix@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IPFIX WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jul 2015 15:50:55 -0000 The following errata report has been verified for RFC7011, "Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow Information". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=7011&eid=4396 -------------------------------------- Status: Verified Type: Editorial Reported by: Rick Hofstede Date Reported: 2015-06-19 Verified by: Benoit Claise (IESG) Section: 3.1 Original Text ------------- Incremental sequence counter modulo 2^32 of all IPFIX Data Records sent in the current stream from the current Observation Domain by the Exporting Process. Corrected Text -------------- Incremental sequence counter modulo 2^32 of all IPFIX Data Records sent in the current stream from the current Observation Domain by the Exporting Process, prior to the receipt of this IPFIX Message. Notes ----- The original specification can be interpreted in two ways: (1) Incremental sequence counter modulo 2^32 of all IPFIX Data Records sent in the current stream from the current Observation Domain by the Exporting Process *up to* this Message. (2) Incremental sequence counter modulo 2^32 of all IPFIX Data Records sent in the current stream from the current Observation Domain by the Exporting Process *up to and including* this Message. It seems that only Section 10.3.2 — Reliability explains which of the two interpretations is right: In the case of UDP, the IPFIX Sequence Number contains the total number of IPFIX Data Records sent for the Transport Session *prior* to the receipt of this IPFIX Message, modulo 2^32. In my opinion, it would be good to clarify the use of sequence numbers in Message headers already in the definition of sequence numbers in RFC 7011, namely in Section 3.1. Discussed here: https://mailarchive.ietf.org/arch/msg/ipfix/AQKObQ2WA_zIXgRzdxRsDrIWjx0 -------------------------------------- RFC7011 (draft-ietf-ipfix-protocol-rfc5101bis-10) -------------------------------------- Title : Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow Information Publication Date : September 2013 Author(s) : B. Claise, Ed., B. Trammell, Ed., P. Aitken Category : INTERNET STANDARD Source : IP Flow Information Export Area : Operations and Management Stream : IETF Verifying Party : IESG