Re: [IPFIX] Fwd: New Version Notification fordraft-kashima-ipfix-data-link-layer-monitoring-05

"Laxmi Mukund (lmukund)" <lmukund@cisco.com> Mon, 28 March 2011 10:57 UTC

Return-Path: <lmukund@cisco.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 62A633A63CB for <ipfix@core3.amsl.com>; Mon, 28 Mar 2011 03:57:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.399
X-Spam-Level:
X-Spam-Status: No, score=-9.399 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_37=0.6, J_CHICKENPOX_39=0.6, RCVD_IN_DNSWL_HI=-8]
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 sv5rJOYLfzhi for <ipfix@core3.amsl.com>; Mon, 28 Mar 2011 03:57:23 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id BD6CC3A63C9 for <ipfix@ietf.org>; Mon, 28 Mar 2011 03:57:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lmukund@cisco.com; l=3787; q=dns/txt; s=iport; t=1301309940; x=1302519540; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=Ltg/8bT2/50ykBKHvXfga3hbzJC5AnLSmSFejXc/O1s=; b=mQpaQ0+0y7RvYVGloxQhzWmHlWk7iiuRnweDfx3sVmxdUME8dOPsg5/P YeWGBS4tta2Uu8wAQRvZHw0X704EBJivSVpDAwasAEjEBGJsVvZDza4+n HWytn1Ub6DSVNJlMDpATLrYgIq20uUGVGvUJfWvsw5eUo9ngVStnGxFsm g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AucAALRokE2Q/khNgWdsb2JhbACYDI0/FAEBFiYlpxSbUYVpBIU4ixk
X-IronPort-AV: E=Sophos;i="4.63,253,1299456000"; d="scan'208";a="81080388"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 28 Mar 2011 10:58:24 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2SAvxnf003009; Mon, 28 Mar 2011 10:58:23 GMT
Received: from xmb-bgl-41a.cisco.com ([72.163.129.216]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 28 Mar 2011 16:28:19 +0530
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, 28 Mar 2011 16:28:17 +0530
Message-ID: <061BB2F7C70CFF42BB3E8DF41D130EB903BE8531@XMB-BGL-41A.cisco.com>
In-Reply-To: <20110324113405.DF09.1AB7FA03@nttv6.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [IPFIX] Fwd: New Version Notification fordraft-kashima-ipfix-data-link-layer-monitoring-05
Thread-Index: AcvpzC8ie7evXsyhRbmHQ1nXKBu7QADaWhLQ
References: <20110324113405.DF09.1AB7FA03@nttv6.net>
From: "Laxmi Mukund (lmukund)" <lmukund@cisco.com>
To: Shingo KASHIMA <kashima@nttv6.net>, ipfix@ietf.org
X-OriginalArrivalTime: 28 Mar 2011 10:58:19.0093 (UTC) FILETIME=[0C068850:01CBED37]
Subject: Re: [IPFIX] Fwd: New Version Notification fordraft-kashima-ipfix-data-link-layer-monitoring-05
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: Mon, 28 Mar 2011 10:57:24 -0000

Hi Shingo San,
I think this would be very useful to include in the draft. We have been
working on this but didn't get to put it in a draft. Glad you could put
them in here.
I have some comments about the draft.
1) 
3.6.  dot1qServiceInstanceTag
Maybe this could be reworded to:
      This Information Element, which may have 16 octets length,
represents 
      the Backbone Service Instance Tag (I-TAG) Tag Control Information
      (TCI) field of an Ethernet frame as described in
      [IEEE802.1ah-2008]. It encodes the priority, drop_eligible,
destination
      and source address.  
2) It looks like Section 3.7 and 3.8 have got interchanged. The
description and the information elements have been switched.

3) Could we include a section that would say the current and new
information elements needed to export all the 802.1ah header fields like
so:

This is a summary of the 802.1ah fields and the new and current
informational elements that would be used to represent each of the
fields.

<-----6---------><------6-------><--4-----><-----6--------><-----6------
--><-----6-------><---4--->
+---------------+---------------+---------+---------------+-------------
--+--------------+--------+
+               +               +         +               +
+              +        +
+     B-DA      +       B-A     + B TAG   +     I-TAG     +      C-DA
+     C-SA     +  C-TAG +
+       1       +        2      +    3    +       4       +        5
+      6       +    7   +
+---------------+---------------+---------+---------------+-------------
--+--------------+--------+

1.(Existing Element) destinationMacAddress 80
2.(Existing Element) sourceMacAddress 56
3.(Existing Element) dot1qVlanId 243, dot1qPriority 244
4.(New Element) defined in section 3.6, 3.7, 3.8 of this draft
5.(New Element) defined in section 3.9 of this draft
6.(New Element) defined in section 3.10 of this draft
7.(Existing Element) dot1qCustomerVlanId 245, dot1qCustomerPriority 246


Very sorry about what happened in Japan, it is very unfortunate.
My best wishes, please take care,
Thanks,
Laxmi.

-----Original Message-----
From: ipfix-bounces@ietf.org [mailto:ipfix-bounces@ietf.org] On Behalf
Of Shingo KASHIMA
Sent: Thursday, March 24, 2011 8:04 AM
To: ipfix@ietf.org
Subject: [IPFIX] Fwd: New Version Notification
fordraft-kashima-ipfix-data-link-layer-monitoring-05


Dear all,

Here is a new version of the draft, which includes:
- new information elements related to 802.1ah (MAC-in-MAC)
- generic offset and observed octets

Is this valuable for WG item ?

I wanted to make a presentaion in Prague.
But I cannot go to Prague due to huge earthquak in Japan.
Sorry.

Best Regards,
Shingo.

----- Original Message -----
Date: Tue, 15 Mar 2011 09:59:12 +0900
From: "IETF I-D Submission Tool" <idsubmission@ietf.org>
Subject: New Version Notification for
draft-kashima-ipfix-data-link-layer-monitoring-05

A new version of I-D,
draft-kashima-ipfix-data-link-layer-monitoring-05.txt 
has been successfully submitted by Kensuke Nakata and posted to the IETF
repository.

Filename: draft-kashima-ipfix-data-link-layer-monitoring
Revision: 05
Title: Information Elements for Data Link Layer Traffic Measurement
Creation_date: 2011-03-15
WG ID: Independent Submission
Number_of_pages: 26

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.

-- 
Shingo KASHIMA <kashima@nttv6.net>

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www.ietf.org/mailman/listinfo/ipfix