Re: [IPFIX] review of draft-ietf-ipfix-mib-variable-export-07
Paul Aitken <[email protected]> Wed, 17 Dec 2014 16:05:52 +0100
| Newsgroups | gmane.ietf.ipfix |
|---|---|
| Message-ID | <23B7BE54EACBED43957AB709C564F7B701853E2B2A@EMEA-EXCH01.corp.brocade.com> |
Thanks for this Juergen. I'll produce an updated version for the editorial issues. For the BITS issue, the largest IPFIX types are currently 64 bits (ie, signed64 / unsigned64). Although we could request a 128-bit type, we're simply moving the absolute limit along without solving the underlying issue. Do you know what size the largest BITS object is today? Would it be acceptable to limit the size that can be exported in IPFIX to the first 64 or 128 bits? Thanks, P. > here is my review of draft-ietf-ipfix-mib-variable-export-07. Most of the > comments are editorial or bug fixes. There is only one real technical concern > related to the encoding of BITS. The current I-D uses a 64-bit unsigned integer, > which limits things to 64 bit positions. The SMIv2 does not have this limit - it only > warns about bit positions in excess of 128. _______________________________________________ IPFIX mailing list [email protected] https://www.ietf.org/mailman/listinfo/ipfix