[IPFIX] RFC 8038 <draft-ietf-ipfix-mib-variable-export-10.txt> NOW AVAILABLE

PJ Aitken <pjaitken@brocade.com> Tue, 16 May 2017 16:19 UTC

Return-Path: <paitken@Brocade.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 D27D812EB78 for <ipfix@ietfa.amsl.com>; Tue, 16 May 2017 09:19:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FX-DPundQKEz for <ipfix@ietfa.amsl.com>; Tue, 16 May 2017 09:19:36 -0700 (PDT)
Received: from mx0a-000f0801.pphosted.com (mx0b-000f0801.pphosted.com [IPv6:2620:100:9005:71::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADB0A12E055 for <ipfix@ietf.org>; Tue, 16 May 2017 09:15:08 -0700 (PDT)
Received: from pps.filterd (m0000700.ppops.net [127.0.0.1]) by mx0b-000f0801.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v4GGEkk2005723; Tue, 16 May 2017 09:15:04 -0700
Received: from brmwp-exmb11.corp.brocade.com ([208.47.132.227]) by mx0b-000f0801.pphosted.com with ESMTP id 2adys1u09p-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 16 May 2017 09:15:04 -0700
Received: from EMEAWP-EXMB12.corp.brocade.com (172.29.11.86) by BRMWP-EXMB11.corp.brocade.com (172.16.59.77) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 16 May 2017 10:15:02 -0600
Received: from [172.27.212.154] (172.27.212.154) by EMEAWP-EXMB12.corp.brocade.com (172.29.11.86) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 16 May 2017 18:14:58 +0200
References: <B46C4319-32EE-480B-85DB-1A2F6081225D@amsl.com>
To: "ipfix@ietf.org" <ipfix@ietf.org>, "bclaise@cisco.com" <bclaise@cisco.com>, Srikar B S <srikarbs@gmail.com>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Colin McDowall <cmcdowal@Brocade.com>
From: PJ Aitken <pjaitken@brocade.com>
X-Forwarded-Message-Id: <B46C4319-32EE-480B-85DB-1A2F6081225D@amsl.com>
Message-ID: <bc529be8-56bf-ae3b-e2a6-02cfc23fd76e@brocade.com>
Date: Tue, 16 May 2017 17:14:53 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <B46C4319-32EE-480B-85DB-1A2F6081225D@amsl.com>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.27.212.154]
X-ClientProxiedBy: hq1wp-excas12.corp.brocade.com (10.70.38.22) To EMEAWP-EXMB12.corp.brocade.com (172.29.11.86)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-05-16_05:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=2 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1705160126
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/BrvdzEQSgldCQlQUvdK7N7WrDh8>
Subject: [IPFIX] RFC 8038 <draft-ietf-ipfix-mib-variable-export-10.txt> NOW AVAILABLE
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 16 May 2017 16:19:39 -0000

FYI, the MIB variable export RFC has finally been published.

Congratulations to the authors, and thanks to everyone who contributed 
and helped with this draft.

P.

> From: rfc-editor@rfc-editor.org
> Subject: RFC 8038 on Exporting MIB Variables Using the IP Flow Information Export (IPFIX) Protocol
> Date: May 2, 2017 at 6:33:09 PM PDT
> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
> Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
>
> A new Request for Comments is now available in online RFC libraries.
>
>
>        RFC 8038
>
>        Title:      Exporting MIB Variables Using the
>                    IP Flow Information Export (IPFIX) Protocol
>        Author:     P. Aitken, Ed.,
>                    B. Claise,
>                    S. B S,
>                    C. McDowall,
>                    J. Schoenwaelder
>        Status:     Standards Track
>        Stream:     IETF
>        Date:       May 2017
>        Mailbox:    paitken@brocade.com,
>                    bclaise@cisco.com,
>                    srikarbs@gmail.com,
>                    cmcdowal@brocade.com,
>                    j.schoenwaelder@jacobs-university.de
>        Pages:      85
>        Characters: 188626
>        Updates/Obsoletes/SeeAlso:   None
>
>        I-D Tag:    draft-ietf-ipfix-mib-variable-export-10.txt
>
>        URL:        https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_info_rfc8038&d=DwIF-g&c=IL_XqQWOjubgfqINi2jTzg&r=l3qN-NVkUTPhhRxKVpFXRDjrG3WNcj_6aGqXB9E7JYU&m=n1SIVEfTEWaWTVidhCiOeti5waf1KKQfkKY-3lKlJcs&s=-WBZuOvcfoy_AZnj8Cq0s2bymqNqZTzuYJe2BDuKDfY&e=
>
>        DOI:        10.17487/RFC8038
>
> This document specifies a way to complement IP Flow Information
> Export (IPFIX) Data Records with Management Information Base (MIB)
> objects, avoiding the need to define new IPFIX Information Elements
> for existing MIB objects that are already fully specified.
>
> Two IPFIX Options Templates, as well as a method for creating IPFIX
> Options Templates that are used to export the extra data required to
> fully describe Simple Network Management Protocol (SNMP) MIB objects
> in IPFIX, are specified herein.
>
> This is now a Proposed Standard.
>
> STANDARDS TRACK: This document specifies an Internet Standards Track
> protocol for the Internet community, and requests discussion and suggestions
> for improvements.  Please refer to the current edition of the Official
> Internet Protocol Standards (https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_standards&d=DwIF-g&c=IL_XqQWOjubgfqINi2jTzg&r=l3qN-NVkUTPhhRxKVpFXRDjrG3WNcj_6aGqXB9E7JYU&m=n1SIVEfTEWaWTVidhCiOeti5waf1KKQfkKY-3lKlJcs&s=RFZU2K77IXlsgiUBwYsQt6DyuZWSf6G3Oq1xmNuY-gE&e= ) for the
> standardization state and status of this protocol.  Distribution of this
> memo is unlimited.
>
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>  https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_ietf-2Dannounce&d=DwIF-g&c=IL_XqQWOjubgfqINi2jTzg&r=l3qN-NVkUTPhhRxKVpFXRDjrG3WNcj_6aGqXB9E7JYU&m=n1SIVEfTEWaWTVidhCiOeti5waf1KKQfkKY-3lKlJcs&s=c9I8mLNQzFZnrkJek-ohvY78DJGhXjruOkphPi1LXv0&e=
>  https://urldefense.proofpoint.com/v2/url?u=https-3A__mailman.rfc-2Deditor.org_mailman_listinfo_rfc-2Ddist&d=DwIF-g&c=IL_XqQWOjubgfqINi2jTzg&r=l3qN-NVkUTPhhRxKVpFXRDjrG3WNcj_6aGqXB9E7JYU&m=n1SIVEfTEWaWTVidhCiOeti5waf1KKQfkKY-3lKlJcs&s=gu9G1wCk1wdVKl_Y3Vigb7E4gTQKdwQoNI1C6aOGI28&e=
>
> For searching the RFC series, see https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_search&d=DwIF-g&c=IL_XqQWOjubgfqINi2jTzg&r=l3qN-NVkUTPhhRxKVpFXRDjrG3WNcj_6aGqXB9E7JYU&m=n1SIVEfTEWaWTVidhCiOeti5waf1KKQfkKY-3lKlJcs&s=4Jrdjy13IBOB7VotVGOMRfb4t9JO2r2Rdbc-UBGsEvQ&e=
> For downloading RFCs, see https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_retrieve_bulk&d=DwIF-g&c=IL_XqQWOjubgfqINi2jTzg&r=l3qN-NVkUTPhhRxKVpFXRDjrG3WNcj_6aGqXB9E7JYU&m=n1SIVEfTEWaWTVidhCiOeti5waf1KKQfkKY-3lKlJcs&s=gI75yvTOd9NqiSRJtCPg0azWi9bZ1rQqBiiCRxx11Go&e=
>
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
>
> The RFC Editor Team
> Association Management Solutions, LLC