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

"Laxmi Mukund (lmukund)" <lmukund@cisco.com> Thu, 07 April 2011 04:19 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 B4A913A685D for <ipfix@core3.amsl.com>; Wed, 6 Apr 2011 21:19:15 -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 ofBJnq6aSZOs for <ipfix@core3.amsl.com>; Wed, 6 Apr 2011 21:19:14 -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 00C8528C0CF for <ipfix@ietf.org>; Wed, 6 Apr 2011 21:19:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lmukund@cisco.com; l=5545; q=dns/txt; s=iport; t=1302150058; x=1303359658; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=xS6aiNewJmHvydmITte6r0VN8uPNqDj+6Vf7ncuZGAU=; b=EHMc7PasJfTza0Ustl/4iLR9SDZEbiH+V+n50aw2MIeLXj2guaPIqOgJ /2Ar+SW1+z7UVWvoHNeuEsvTvj55pUmMFBOKpRnsTIdu7hBcwEs7X21pd +F1U/3jpeBdEG6qoeiHzEofOl6FHiF0Cldt9Q38aqOLLwTsA1HpwHCwcb Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AroAAEc7nU2Q/khLgWdsb2JhbACYNI1MFAEBCwsmJYh5nX+cb4VsBIVMi10
X-IronPort-AV: E=Sophos;i="4.63,314,1299456000"; d="scan'208";a="82527106"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 07 Apr 2011 04:20:57 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p374Knbb019239; Thu, 7 Apr 2011 04:20:57 GMT
Received: from xmb-bgl-41a.cisco.com ([72.163.129.216]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 7 Apr 2011 09:50:56 +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: Thu, 07 Apr 2011 09:50:55 +0530
Message-ID: <061BB2F7C70CFF42BB3E8DF41D130EB903D8A0A3@XMB-BGL-41A.cisco.com>
In-Reply-To: <20110406002315.B2A1.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: AcvzpXURzw0XLVFWTPCIlJ2kIxsRaABNDz+A
References: <20110324113405.DF09.1AB7FA03@nttv6.net> <061BB2F7C70CFF42BB3E8DF41D130EB903BE8531@XMB-BGL-41A.cisco.com> <20110406002315.B2A1.1AB7FA03@nttv6.net>
From: "Laxmi Mukund (lmukund)" <lmukund@cisco.com>
To: Shingo KASHIMA <kashima@nttv6.net>
X-OriginalArrivalTime: 07 Apr 2011 04:20:56.0286 (UTC) FILETIME=[30BC67E0:01CBF4DB]
Cc: ipfix@ietf.org
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: Thu, 07 Apr 2011 04:19:15 -0000

Hi Shingo San,
Thank you for the reply. Yes we can combine 4.5.6 in the list.
Thanks,
Laxmi.

-----Original Message-----
From: Shingo KASHIMA [mailto:kashima@nttv6.net] 
Sent: Tuesday, April 05, 2011 8:53 PM
To: Laxmi Mukund (lmukund)
Cc: ipfix@ietf.org
Subject: Re: [IPFIX] Fwd: New Version Notification
fordraft-kashima-ipfix-data-link-layer-monitoring-05


Hi Laxmi,

Thank you for your comments.

Please see in-line.

On Mon, 28 Mar 2011 16:28:17 +0530
"Laxmi Mukund (lmukund)" <lmukund@cisco.com> san wrote:

> 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.  

Yes.
I will modify in a next revision.


> 2) It looks like Section 3.7 and 3.8 have got interchanged. The
> description and the information elements have been switched.

Oh.. This is my mistake.
I will modify in a next revision.


> 
> 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
> 

Nice comments.
But as you know, I-TAG includes C-DA and C-SA
How about the following ?

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

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, 3.9 and 3.10 of this
draft
5.(Existing Element) dot1qCustomerVlanId 245, dot1qCustomerPriority 246


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

Thank you.


> 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

-- 
Shingo KASHIMA <kashima@nttv6.net>