@techreport{li-opsawg-ipfix-extended-message-00,
    number =    {draft-li-opsawg-ipfix-extended-message-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-li-opsawg-ipfix-extended-message/00/},
    author =    {Zhenqiang Li and Paul Aitken},
    title =     {{Extended Length Message Support for IP Flow Information Export (IPFIX)}},
    pagetotal = 6,
    year =      2017,
    month =     jun,
    day =       30,
    abstract =  {The specification of the IP Flow Information Export (IPFIX) Protocol {[}RFC7011{]} defines an IPFIX Message length of 16 bits. As new Information Elements (IEs) are introduced in IPFIX to export long information, such as the BGP community information {[}I-D.ietf-opsawg-ipfix-bgp-community{]}, an IPFIX Message no longer has sufficient space to fit all the information of a specific flow. This document updates the IPFIX specification by extending the IPFIX Message length from 16 bits to 32 bits. For backwards compatibility, a new version of IPFIX (i.e., 11) is introduced to support the 32-bit Message length.},
}