Re: [IPFIX] Initial review of draft-ietf-ipfix-mib-variable-export-03

On Thu, Nov 07, 2013 at 09:15:47PM +0000, Colin McDowall wrote:
> 
> A string encoding may be easier for some implementors but might
> require translation into a string if any OIDs being exported are
> already stored internally with a BER encoding. I'm thinking more of
> the case where the value of a mibObject is itself an OID.
> 

OIDs as values are rare and even then it is an implementation choice
whether they are stored internally BER encoded.

> The encoding is already a standard and there are library
> implementations of the BER encoding.  Also anything extracting
> values out of an existing MIB implementation will probably already
> have support.

Yes, for the exporter this should not be an issue at all. For
something processing collected IPFIX records, BER encoded OIDs may be
a bit more fun. That said, it should be possible to write a fairly
simple piece of C code to go into an appendix in case people think it
is hard to figure out how this works.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
_______________________________________________
IPFIX mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipfix