[IPFIX] Link-layer IEs draft submitted to IESG
Nevil Brownlee <n.brownlee@auckland.ac.nz> Wed, 09 October 2013 18:54 UTC
Return-Path: <n.brownlee@auckland.ac.nz>
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 5CDDB21E8181 for <ipfix@ietfa.amsl.com>; Wed, 9 Oct 2013 11:54:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 8nKyvzhynRhM for <ipfix@ietfa.amsl.com>; Wed, 9 Oct 2013 11:54:25 -0700 (PDT)
Received: from mx2.auckland.ac.nz (mx2.auckland.ac.nz [130.216.125.245]) by ietfa.amsl.com (Postfix) with ESMTP id D542721E818E for <ipfix@ietf.org>; Wed, 9 Oct 2013 11:54:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=uoa; t=1381344858; x=1412880858; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=RE4raDeppLk1ECsHwbGvxVT0mDIP3riuFpfhQt2InhE=; b=eT1iscxqYibnNc0CnPWPyB9mZaGmEUEDGhIljEeoDmpXnKOHn9t60hgD F7P6/JZM0VeD3lDV+zHVHaTHGzcy7hGvyj/RzXdZI5SlFBQMab2E90XA+ jPubbUSNG2Xw7ty8kxFFV4pq0NQheEk60pX21ZbicOtUgaABe/FX24emL s=;
X-IronPort-AV: E=Sophos;i="4.90,1065,1371038400"; d="scan'208";a="216738300"
X-Ironport-HAT: None - $RELAY-AUTH
X-Ironport-Source: 121.98.105.173 - Outgoing - Outgoing-SSL
Received: from 121-98-105-173.bng1.tvc.orcon.net.nz (HELO [192.168.0.4]) ([121.98.105.173]) by mx2-int.auckland.ac.nz with ESMTP; 10 Oct 2013 07:54:14 +1300
Message-ID: <5255A655.50605@auckland.ac.nz>
Date: Thu, 10 Oct 2013 07:54:13 +1300
From: Nevil Brownlee <n.brownlee@auckland.ac.nz>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: IPFIX list <ipfix@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [IPFIX] Link-layer IEs draft submitted to IESG
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: Wed, 09 Oct 2013 18:54:29 -0000
Hi all: Here's the write-up for our link-layer IEs draft, which I've just submitted. Cheers, Nevil Write-up for: draft-ietf-ipfix-data-link-layer-monitoring-06 Information Elements for Data Link Layer Traffic Measurement === 1. Summary === Document shepherd: Nevil Brownlee Responsible Area Director: Benoit Claise This document describes Information Elements (IEs) 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 document is intended to be a Proposed Standard. It describes, in detail, a set of Information Elements describing link-layer objects. These will be particularly to service providers who use Wide-Area Ethernet or Virtual Ethernet technologies. === 2. Review and Consensus === This draft's -00 version was published in July 2012. Two of its authors were from a large Japanese provider who needed to monitor and report on link-layer performance. Since then it has received ongoing low-activity-level discussion on the IPFIX list. It has also been discussed at each IETF meeting since then; alas, the WG has always considered this as low-priority work. Its WGLC was run in October 2012; we realised at that point that we needed someone from IEEE 802.1 to check that our Ethernet IEs were correct in their descriptions of the IEEE-defined technologies. Pat Thaler, IEEE liaison for IETF, has helped develop this document since then, she confirms that the IEEE-related IEs are correct in their descriptions. It has been carefully reviewed by Paul Aitken and Brian Trammell, both pointed out issues; these have been addressed in successive versions. Overall I believe that there is clear consensus within the WG for this draft. === 3. Intellectual Property === No IPR disclosures have been made directly on this draft, IPR on it has not been discussed in the WG. Two of the authors have stated that their direct, personal knowledge of any IPR related to this document has already been disclosed, in conformance with BCPs 78 and 79. The third author, Shingo Kashima, has not responded to my email requests for this confirmation. === 4. Other Points === This document has no downward references. Its IANA Considerations clearly state what IANA is being asked to do, i.e. add 25 new IPFIX Information Elements to the IPFIX Information Element Registry. These have been discussed at IETF meetings with all four of the IE-Doctors present. It also describes two existing IEs: 312, dataLinkFrameSize and 315, dataLinkFrameSection. These are already in the Information Element Registry - they're listed here so that all the link-layer IEs are described in a single RFC. The ID-nits checker has a few other complaints; the RFC Editor will fix those. Overall, I believe that this draft is ready for publication as an RFC. -- --------------------------------------------------------------------- Nevil Brownlee Computer Science Department | ITS Phone: +64 9 373 7599 x88941 The University of Auckland FAX: +64 9 373 7453 Private Bag 92019, Auckland 1142, New Zealand
- [IPFIX] Link-layer IEs draft submitted to IESG Nevil Brownlee
- Re: [IPFIX] Link-layer IEs draft submitted to IESG Benoit Claise