IETF Logo Mail Archive

[IPFIX] IPFIX length fields

Paul Aitken <paitken@cisco.com> Thu, 01 March 2012 23:07 UTC

Return-Path: <paitken@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 B40E621E82D8 for <ipfix@ietfa.amsl.com>; Thu, 1 Mar 2012 15:07:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.523
X-Spam-Level:
X-Spam-Status: No, score=-10.523 tagged_above=-999 required=5 tests=[AWL=0.075, 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 ZUvi7oBedpSK for <ipfix@ietfa.amsl.com>; Thu, 1 Mar 2012 15:07:14 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 99BC921E8292 for <ipfix@ietf.org>; Thu, 1 Mar 2012 15:07:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=paitken@cisco.com; l=2558; q=dns/txt; s=iport; t=1330643234; x=1331852834; h=message-id:date:from:mime-version:to:cc:subject; bh=RTgfGDnnBIgbInQu2I/i3LhZOSXq5OoG4TaTfqn0h20=; b=ZFO4RSiHvyxN/ihprNK/NSFrFUI4k6SofsMGtdg5dEVR1aOZSWQn/iwx 6Ql9XwgjV781S1rQnSeFfeUMoBkyH8GhqJMVeEEl8nOYoitwFPxKVIGoV ID1eFT2aRy0xP6EVtHtrb7KU0yP7AxKurwmbzw8zO5J9VSTWvIVn0uyyO g=;
X-IronPort-AV: E=Sophos; i="4.73,513,1325462400"; d="scan'208,217"; a="131112009"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 01 Mar 2012 23:07:08 +0000
Received: from [10.55.88.82] (dhcp-10-55-88-82.cisco.com [10.55.88.82]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q21N78r6022077; Thu, 1 Mar 2012 23:07:08 GMT
Message-ID: <4F50011C.1020508@cisco.com>
Date: Thu, 01 Mar 2012 23:07:08 +0000
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.27) Gecko/20120216 Lightning/1.0b2 Thunderbird/3.1.19
MIME-Version: 1.0
To: IETF IPFIX Working Group <ipfix@ietf.org>
Content-Type: multipart/alternative; boundary="------------060608070905070701090300"
Cc: Nicholas Brown <nicbrown@cisco.com>
Subject: [IPFIX] IPFIX length fields
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: Thu, 01 Mar 2012 23:07:15 -0000

Dear all,

Reviewing IANA's IPFIX field list, we noticed that most of the *length 
fields have no semantics.

However, mplsTopLabelPrefixLength has semantics of "identifier", while 
ethernetHeaderLength, ethernetPayloadLength, ethernetTotalLength have 
semantics of "identifier".

We propose that these all be changed to no semantics.

Or better, that all lengths be changed to semantics of "quantity", since 
RFC5102 says,

    3.2.1.  quantity

        A quantity value represents a discrete measured value pertaining to
        the record.  This is distinguished from counters that represent an
        ongoing measured value whose "odometer" reading is captured as part
        of a given record.If no semantic qualifier is given, the
        Information Elements that have an integral data type should behave as
        a quantity.


Feedback?

Thanks,
Paul and Nick

v2.23.0 | Report a Bug | By Email