Re: [IPFIX] Fw: New Version Notification fordraft-kashima-ipfix-data-link-layer-monitoring-07.txt
"Aamer Akhter (aakhter)" <aakhter@cisco.com> Mon, 26 March 2012 09:04 UTC
Return-Path: <aakhter@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 DDDFF21F854D for <ipfix@ietfa.amsl.com>; Mon, 26 Mar 2012 02:04:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.599
X-Spam-Level:
X-Spam-Status: No, score=-109.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 jS2ZElotJL7z for <ipfix@ietfa.amsl.com>; Mon, 26 Mar 2012 02:04:13 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 1BDFD21F8516 for <ipfix@ietf.org>; Mon, 26 Mar 2012 02:04:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3478; q=dns/txt; s=iport; t=1332752653; x=1333962253; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=Xj71T27lgqOy3gDWiJ92MF+L0ZU0n+NxS3Xcro+kXi0=; b=AjPmlBhbTWkAReVZ4PRVNI2F0YUXIQe4P5S9/Tg5/ot6DP+9apGMx6uP YvAXs9DX4NXGbdzaJvzomE4Ed/vYvgLkI0nJXlmuXk0jV5Mia3v4Y+iSH BSoUHuJGzHXy7VwdGH7pN/vq21l3Ialr0SnMfnPTcoSXpJo/dWrLOtrcg c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAEwwcE+tJV2d/2dsb2JhbABEuDCBB4IJAQEBBAEBAQ8BHQotBwQFDgQCAQgRAwEBAQsGFwEGASYfCQgBAQQBEggah2gLmgueO5BFYwSIV44ajTSBaIMF
X-IronPort-AV: E=Sophos;i="4.73,649,1325462400"; d="scan'208";a="66330693"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-9.cisco.com with ESMTP; 26 Mar 2012 09:04:12 +0000
Received: from xbh-rcd-201.cisco.com (xbh-rcd-201.cisco.com [72.163.62.200]) by rcdn-core-6.cisco.com (8.14.3/8.14.3) with ESMTP id q2Q94Cb8029247; Mon, 26 Mar 2012 09:04:12 GMT
Received: from xmb-rcd-101.cisco.com ([72.163.62.143]) by xbh-rcd-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 26 Mar 2012 04:04:12 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 26 Mar 2012 04:04:09 -0500
Message-ID: <7F298ACC76CC154F832B6D02852D169F078D56C7@XMB-RCD-101.cisco.com>
In-Reply-To: <20120326031139.8285.1AB7FA03@nttv6.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [IPFIX] Fw: New Version Notification fordraft-kashima-ipfix-data-link-layer-monitoring-07.txt
thread-index: Ac0KsvHvkl9Req3EQSW6kiOL3bEjVgAdTWPQ
References: <20120326031139.8285.1AB7FA03@nttv6.net>
From: "Aamer Akhter (aakhter)" <aakhter@cisco.com>
To: Shingo KASHIMA <kashima@nttv6.net>, ipfix@ietf.org
X-OriginalArrivalTime: 26 Mar 2012 09:04:12.0384 (UTC) FILETIME=[696EA600:01CD0B2F]
Subject: Re: [IPFIX] Fw: New Version Notification fordraft-kashima-ipfix-data-link-layer-monitoring-07.txt
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: Mon, 26 Mar 2012 09:04:14 -0000
Hi Shingo, Please find my comments regarding draft-kashima-ipfix-data-link-layer-monitoring-07 below: Sec 2.3 - given the section context it might be worthwhile to mention LAG connections and how these can be tracked using the ingressPhysicalInterface and egressPhysicalInterface. - it is unclear what this section means for IPFIX information elements. (perhaps none?) Sec 3.1 - would it be possible to add a 'units' field? I think dataLinkFrameSize is to be expressed in bytes, but let's be explicit. Sec 3.2 - given the provider and customer l2 spans, does it make sense to further refine what is meant by ' carries n octets from the data link frame of a selected frame' Sec 3.5 - It's not clear to me what sectionObservedOctets is actually reporting on. 3.12. postMCastL2OctetDeltaCount - Is the L2 mcast behavior any different (in this area for reporting) for 802.1Qbh rather than traditional L2 bridges? (I don't know the answer for sure.) I think we just need to make sure that both cases (802.1Qbh and regular bridges can use this field. 3.17. droppedL2OctetDeltaCount - I think this is also referring to policy drops (for example done by relay in 802.1Qbh), not just regular drops (QoS, broadcast suppression etc.) Is the 802.1Qbh case to be handled in any special way? 3.19 and 3.20 description is exactly the same (copy and paste error?) -----Original Message----- From: ipfix-bounces@ietf.org [mailto:ipfix-bounces@ietf.org] On Behalf Of Shingo KASHIMA Sent: Sunday, March 25, 2012 2:12 PM To: ipfix@ietf.org Subject: [IPFIX] Fw: New Version Notification fordraft-kashima-ipfix-data-link-layer-monitoring-07.txt Hi IPFIXer, I posted draft-kashima-ipfix-data-link-layer-monitoring-07. http://tools.ietf.org/html/draft-kashima-ipfix-data-link-layer-monitorin g-07 Soon this draft will be draft-ietf-ipfix-data-link-layer-monitoring-00. The differences from -06 are as follows: - adding "the relationship between Ethernet header filelds and Information Elements " in section 6, according to the comment raised by Laxmi Mukund. - adding new Information Elements related to octet counter and packet length for layer 2 in section 3.11 - 3.24 Best Regards, Shingo. Forwarded by Shingo KASHIMA <kashima.shingo@lab.ntt.co.jp> ----------------------- Original Message ----------------------- From: internet-drafts@ietf.org To: kashima@nttv6.net Date: Mon, 12 Mar 2012 13:02:52 -0700 Subject: New Version Notification for draft-kashima-ipfix-data-link-layer-monitoring-07.txt ---- A new version of I-D, draft-kashima-ipfix-data-link-layer-monitoring-07.txt has been successfully submitted by Shingo Kashima and posted to the IETF repository. Filename: draft-kashima-ipfix-data-link-layer-monitoring Revision: 07 Title: Information Elements for Data Link Layer Traffic Measurement Creation date: 2012-03-12 WG ID: Individual Submission Number of pages: 34 Abstract: This document describes Information Elements related to data link layer. They are used by the IP Flow Information Export (IPFIX) protocol for encoding measured data link layer traffic information. The IETF Secretariat --------------------- Original Message Ends -------------------- _______________________________________________ IPFIX mailing list IPFIX@ietf.org https://www.ietf.org/mailman/listinfo/ipfix
- [IPFIX] Fw: New Version Notification for draft-ka… Shingo KASHIMA
- Re: [IPFIX] Fw: New Version Notification fordraft… Aamer Akhter (aakhter)