[IPFIX] How to interpret the scope/options in options template wisely

Min Wang <mwang@sevone.com> Wed, 07 January 2015 20:04 UTC

Return-Path: <mwang@sevone.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 9D0731A1ABF for <ipfix@ietfa.amsl.com>; Wed, 7 Jan 2015 12:04:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id bvueAsYol7oE for <ipfix@ietfa.amsl.com>; Wed, 7 Jan 2015 12:04:08 -0800 (PST)
Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9EA41A0275 for <ipfix@ietf.org>; Wed, 7 Jan 2015 12:04:07 -0800 (PST)
Received: by mail-qa0-f49.google.com with SMTP id dc16so4193490qab.8 for <ipfix@ietf.org>; Wed, 07 Jan 2015 12:04:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sevone.com; s=google; h=message-id:date:from:user-agent:mime-version:to:subject :content-type; bh=TBHU0NnWBpz8l8wlHQpV306AnQsSR16aagOPtFBaEHQ=; b=XmhB2xhXFdho7mZdpb+L4lI5EfhJACY8kD+uEFarZdFneXwuoJzvDD/Dg9ek6S9AJL nFoSjvxWYFhEYhZif9NaiAebzIOHKraQKF6Xt3OI49ZyCv0V1ip9ianwNL4THDEXhvRh 2L9/5ZbSiwEp5VUt3/eLWl5eeN1VLABdQE/Z0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:content-type; bh=TBHU0NnWBpz8l8wlHQpV306AnQsSR16aagOPtFBaEHQ=; b=ILk75EcJ6seYVXYu35JSbEnE4Ksewhp4PVP2sxPw+l0AUHKoyNGpqbs/PA7u/N/wMa O3g2Zf1bQuTWLasdX0BWJMZqKWRffLyass/7aYwAh7yBCEUeV/y8BpPj+pRAoJa2tT2H DDPnKVU++CfMsYluQiwbIUgVWNarwqpH15o5Zr9OMWuJ37pL+nc6a5fjKDy36deiHh4Z zxTwNzX7/QYuFqfWfoD4uGaqaC0ukgOXNKF7EV2Z9/pOoWj0pzsJ+/sntcwkH/+S8WAk i+iN0ab0avqbetI6/Ot9Wf5RInwBt+SA8fd7XUe+407/1okRRsb4K/ojarFCIdhPW0Wh 0oiw==
X-Gm-Message-State: ALoCoQlLasBQGafKwr25NLTjsX53E4S33rr07RJc/veneHBFQDBMCHoWBAw+lDm1yvjMnGXHtdWJhMh4NS8GBfg+sP3NvRtkXjzJXuE4LE1Ofd+khbbB0tg=
X-Received: by with SMTP id b7mr7928197qan.70.1420661046966; Wed, 07 Jan 2015 12:04:06 -0800 (PST)
Received: from mwang-pc.sevone.com (50-202-126-166-static.hfc.comcastbusiness.net. []) by mx.google.com with ESMTPSA id u49sm2069893qgd.26.2015. for <ipfix@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 07 Jan 2015 12:04:06 -0800 (PST)
Message-ID: <54AD9135.8000508@sevone.com>
Date: Wed, 07 Jan 2015 15:04:05 -0500
From: Min Wang <mwang@sevone.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7
MIME-Version: 1.0
To: ipfix@ietf.org
Content-Type: multipart/alternative; boundary="------------080105090004030502000507"
Archived-At: http://mailarchive.ietf.org/arch/msg/ipfix/WTQLYCXSSNrhScBn0UuPj7ELGvc
Subject: [IPFIX] How to interpret the scope/options in options template wisely
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: Wed, 07 Jan 2015 20:04:16 -0000


in RFC-7011, it said:

    4 <https://tools.ietf.org/html/rfc7011#section-4>. Specific
    Reporting Requirements

The Collecting Process MUST check the possible combinations of
    Information Elements within the Options Template Records to correctly
    interpret the following Options Templates.

Is there any guidance on how to interpret the scope/option fields IE in those options templates.

There are hundreds of IEs, in the real world, how can a reporting engine possibly know/interpret these combinations wisely  without check those IEs manually first?




SevOne, Inc. reserves the right to monitor the transmission of this message 
and to take corrective action against any misuse or abuse of its e-mail 
system or other components of its network.

The information contained in this e-mail may be confidential and/or legally 
privileged. It is intended solely for the addressee.  If the reader of this 
message is not an intended recipient, you are hereby notified that any 
unauthorized review, use, disclosure, dissemination, distribution, or 
copying of this communication, or any of its contents, is strictly 
prohibited and may be unlawful. If you have received this communication in 
error, please reply to the sender and destroy all copies of the message. 
 To contact us directly, send to postmaster@sevone.com.