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

From: PJ Aitken <[email-masked]>
Date: Tue, 16 May 2017 17:14:53 +0100

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: [email-masked]
> 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: [email-masked], [email-masked]
> Cc: [email-masked], [email-masked]
>
> 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:    [email-masked],
>                    [email-masked],
>                    [email-masked],
>                    [email-masked],
>                    [email-masked]
>        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 [email-masked].  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
>
> The RFC Editor Team
> Association Management Solutions, LLC