Re: OPENBSD-PF-MIB, use DisplayString not OCTET STRING

2021-03-23 Thread Martijn van Duren
On Mon, 2021-03-22 at 09:00 +, Stuart Henderson wrote: > On 2021/03/22 00:20, Martijn van Duren wrote: > > There's two things I'd like to know before going further with this: > > > > 1) according to RFC2578 section 3.6: > > (1)  registration: the definition of a particular item is registered

Re: OPENBSD-PF-MIB, use DisplayString not OCTET STRING

2021-03-22 Thread Stuart Henderson
On 2021/03/22 00:20, Martijn van Duren wrote: > There's two things I'd like to know before going further with this: > > 1) according to RFC2578 section 3.6: > (1) registration: the definition of a particular item is registered as > a particular OBJECT IDENTIFIER value, and associated with a

Re: OPENBSD-PF-MIB, use DisplayString not OCTET STRING

2021-03-21 Thread Martijn van Duren
There's two things I'd like to know before going further with this: 1) according to RFC2578 section 3.6: (1) registration: the definition of a particular item is registered as a particular OBJECT IDENTIFIER value, and associated with a particular descriptor. After such a registration,

OPENBSD-PF-MIB, use DisplayString not OCTET STRING

2021-03-20 Thread Stuart Henderson
DisplayString seems a better type for pfIfDescr and some of the other objects; this improves the display format in Prometheus snmp_exporter which uses hex values for OCTET STRING. OK? Index: OPENBSD-PF-MIB.txt === RCS file: