Re: [IPFIX] draft-kashima-ipfix-data-link-layer-monitoring

Hadriel Kaplan <HKaplan@acmepacket.com> Tue, 09 November 2010 06:02 UTC

Return-Path: <HKaplan@acmepacket.com>
X-Original-To: ipfix@core3.amsl.com
Delivered-To: ipfix@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AB0A63A69AE for <ipfix@core3.amsl.com>; Mon, 8 Nov 2010 22:02:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.154
X-Spam-Level:
X-Spam-Status: No, score=-2.154 tagged_above=-999 required=5 tests=[AWL=0.445, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GknvaeDfnCO5 for <ipfix@core3.amsl.com>; Mon, 8 Nov 2010 22:02:38 -0800 (PST)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id BD2663A69EE for <ipfix@ietf.org>; Mon, 8 Nov 2010 22:02:36 -0800 (PST)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Tue, 9 Nov 2010 01:02:55 -0500
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Tue, 9 Nov 2010 01:02:55 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Shingo KASHIMA <kashima@nttv6.net>
Date: Tue, 09 Nov 2010 01:02:53 -0500
Thread-Topic: [IPFIX] draft-kashima-ipfix-data-link-layer-monitoring
Thread-Index: Act/08AhzRbIGQTjQxKYpa8TgIRxGw==
Message-ID: <DA9BBB04-D03D-439F-8064-B46EA5D97B20@acmepacket.com>
References: <20101109014328.D0A1.1AB7FA03@nttv6.net> <4CD875D2.5030907@cisco.com> <20101109104639.C689.1AB7FA03@nttv6.net>
In-Reply-To: <20101109104639.C689.1AB7FA03@nttv6.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF IPFIX Working Group <ipfix@ietf.org>, "ipfix-chairs@tools.ietf.org" <ipfix-chairs@tools.ietf.org>
Subject: Re: [IPFIX] draft-kashima-ipfix-data-link-layer-monitoring
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 09 Nov 2010 06:02:40 -0000

On Nov 8, 2010, at 10:08 PM, Shingo KASHIMA wrote:

> Then let's see existing IEs.
> - flowEndReason includes a value list in its description.
> - biflowDirection includes a value list in its description.
> Are there IEs which do not include a value list in their description ?
> 
> Which is IPFIX IEs registries policy, to be defined in the IE
> description or in separate registries ?
> We should follow our policy.
> Or, dataLinkFrameType is a different kind of IE from existing IEs
> such as flowEndReason and biflowDirection ?

I think he means more like mplsTopLabelType, which has an actual registry for its enumeration values. (See http://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-mpls-label-type)

-hadriel