Re: [IPFIX] Initial review of draft-ietf-ipfix-mib-variable-export-03
Andrew Feren <[email protected]>
| Newsgroups | gmane.ietf.ipfix |
|---|---|
| Message-ID | <[email protected]> |
On 11/03/2013 11:05 AM, Juergen Schoenwaelder wrote: > On Fri, Nov 01, 2013 at 04:47:05AM +0100, Brian Trammell wrote: >> (3) Clarifying and SNMP-naif question on 11.2.2 mibObjectIdentifier: it >> seems from the examples that the intention is that the OID will be >> encoded in the document as a Unicode string of digits and "." >> characters? Is this the way OIDs are encoded in SNMP? The encoding of >> fundamentally binary data in strings is not very IPFIXish (7013 section >> 4.2 para 6), and I kind of expected these to be encoded as octetarrays >> of unsigned integers of a specified size, or something similar. However, >> if encoding-as-string is how things are done on the wire in SNMP, it's >> the right thing to do here too (7013 section 4.5). The same comment >> applies to 11.2.4. >> > SNMP uses ASN.1/BER and this gives you are much more compact encoding > of OIDs (but this is of course a much less human/programmer friendly > representation). So, would a simple octetArray like Brian asked about make sense? I'm still not sure. >> IpAddress -> ipv4Address (side question: how do you do V6 with SNMP?) > The IPv6 address types are an OCTET STRING on the wire (not a tagged > type anymore). I've occasionally wondered if an ipAddress type (varlen 4 or 16 octets) would be useful in IPFIX. -Andrew _______________________________________________ IPFIX mailing list [email protected] https://www.ietf.org/mailman/listinfo/ipfix