It seems we should have the same capability for the ITEF Job Monitoring MIB,
so that any private IPP attribute that an IPP implementor invents, could be
supported by the same vendor in the IETF Job Monitoring MIB. My suggestion
would be to reserve a range of attribute enums for private experimental use
with clear warnings of interoperatbility problems for such use (and encourage
registration).
How about allocating a block of enum values for private JMP job attributes
in the range of 2**30 to 2**31-1 (same range as for IPP private operations)?
Comments?
Tom