Re: [IPFIX] [Technical Errata Reported] RFC5655 (4306)

Benoit Claise <bclaise@cisco.com> Thu, 19 March 2015 21:23 UTC

Return-Path: <bclaise@cisco.com>
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 32DE41ACF59 for <ipfix@ietfa.amsl.com>; Thu, 19 Mar 2015 14:23:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 7W2juizH8mZv for <ipfix@ietfa.amsl.com>; Thu, 19 Mar 2015 14:23:37 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A2481ACF56 for <ipfix@ietf.org>; Thu, 19 Mar 2015 14:23:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3080; q=dns/txt; s=iport; t=1426800217; x=1428009817; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=C99vDpFw+s9XCeamPR9OJeW/rF81bT5I/r3zZOeMruw=; b=IxwsRYLiTeDqAQMO4GxDmJK3D9RzKOT2keCa6AvMG9i+sgMSKk/J7Y9P 2uDVxtYRuLFbc3zYhxNB1n7XN4ZqdM1/jrFrd9PafnL2JpFGCPuecEJ/6 IyO94dJGiX923dPph77+XkL7fAZNs4SK49E3rbbLfXTQARUDqGUc+B0Ll E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BQBABOPQtV/xbLJq1CGg6DSlrEYYFFCoV1AoIBFAEBAQEBAQF8hBABAQQBAQEkETYKARALDgoJFg8JAwIBAgEVMAYBDAEFAgEBiCsNN81tAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4sXgT2DNAeELQEEhhaUI4EbgzCCOI0lIoF/Aw0PgRM+PTEBEYIxAQEB
X-IronPort-AV: E=Sophos;i="5.11,432,1422921600"; d="scan'208";a="388706097"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 19 Mar 2015 21:23:35 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t2JLNYtK012980; Thu, 19 Mar 2015 21:23:35 GMT
Message-ID: <550B3E56.4040303@cisco.com>
Date: Thu, 19 Mar 2015 22:23:34 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Paul Aitken <paitken@brocade.com>, "brian.trammell@hitachi-eu.com" <brian.trammell@hitachi-eu.com>, "elisa.boschi@hitachi-eu.com" <elisa.boschi@hitachi-eu.com>, "lutz.mark@ifam.fraunhofer.de" <lutz.mark@ifam.fraunhofer.de>, "tanja.zseby@fokus.fraunhofer.de" <tanja.zseby@fokus.fraunhofer.de>, "arno@wagner.name" <arno@wagner.name>, "joelja@bogus.com" <joelja@bogus.com>, "n.brownlee@auckland.ac.nz" <n.brownlee@auckland.ac.nz>, "quittek@neclab.eu" <quittek@neclab.eu>
References: <20150319180856.28BEC180205@rfc-editor.org> <550B390C.8080809@brocade.com>
In-Reply-To: <550B390C.8080809@brocade.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipfix/HSA7m_wWszd0R5syJ4uv1hFxwG0>
Cc: "ipfix@ietf.org" <ipfix@ietf.org>
Subject: Re: [IPFIX] [Technical Errata Reported] RFC5655 (4306)
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 19 Mar 2015 21:23:39 -0000

Thanks Paul,

I'll accept it.

Regards, Benoit
> [-RFC Editor]
>
> I checked the figure and agree with Wayne: the byte should be 0x16 
> because there's only one padding octet, not three.
>
> P.
>
>
> On 19/03/15 18:08, RFC Errata System wrote:
>> The following errata report has been submitted for RFC5655,
>> "Specification of the IP Flow Information Export (IPFIX) File Format".
>>
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=5655&eid=4306
>>
>> --------------------------------------
>> Type: Technical
>> Reported by: Wayne Tackabury <wtackabury@us.ibm.com>
>>
>> Section: A.5
>>
>> Original Text
>> -------------
>>     224: 0A 47 0A B6 E5 47 0C 07 48 00|01 03 00 18 00 3E
>>             [ message checksum record ^ -->
>>     240: 2B 37 08 CE B2 0E 30 11 32 12 4A 5F E3 AD DB 00
>>
>>     256:|00 0A 05 10 47 0A B6 E5 00 00 00 06 00 00 00 01
>>
>>
>>
>> Corrected Text
>> --------------
>>     224: 0A 47 0A B6 E5 47 0C 07 48 00|01 03 00 16 00 3E
>>             [ message checksum record ^ -->
>>     240: 2B 37 08 CE B2 0E 30 11 32 12 4A 5F E3 AD DB 00
>>
>>     256:|00 0A 05 10 47 0A B6 E5 00 00 00 06 00 00 00 01
>>
>>
>>
>> Notes
>> -----
>> First of all, note that per erratum #2030, the offsets in this whole 
>> section are wrong, it should begin (I think) at 192.  I shall use the 
>> published (incorrect) offset for illuminating this point:
>>
>> I believe the byte at #237 should be 0x16 and not 0x18.  I suspect 
>> this checksum was copy-pasted from a prior instance in the example, 
>> where there were three pad bytes added to the data record for #259 
>> (0x103).    In this instance, there is only one pad byte at #255, 
>> hence the offset here should be two less (22 or 0x16 and not 24 or 
>> 0x18):
>>
>>    2 bytes set ID
>>    2 bytes length
>>    1 byte option data
>>   16 bytes checksum data
>>    1 byte pad (at #255)
>>
>>   ...totalling 22. Thanks!
>>
>> Instructions:
>> -------------
>> This erratum is currently posted as "Reported". If necessary, please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party (IESG)
>> can log in to change the status and edit the report, if necessary.
>>
>> --------------------------------------
>> RFC5655 (draft-ietf-ipfix-file-05)
>> --------------------------------------
>> Title               : Specification of the IP Flow Information Export 
>> (IPFIX) File Format
>> Publication Date    : October 2009
>> Author(s)           : B. Trammell, E. Boschi, L. Mark, T. Zseby, A. 
>> Wagner
>> Category            : PROPOSED STANDARD
>> Source              : IP Flow Information Export
>> Area                : Operations and Management
>> Stream              : IETF
>> Verifying Party     : IESG
>>
>> _______________________________________________
>> IPFIX mailing list
>> IPFIX@ietf.org
>> https://www.ietf.org/mailman/listinfo/ipfix
>
> .
>