You offer Harald's message as the definitive IETF response to the Job M=
IB
but, at the end of his note , Harald states
"I've scheduled the Job MIB on my list of things to look at; let's hope=
things get sorted out correctly!"
Harald cited several reasons why a charter may be denied, including
- The proposal is not going to be used in or around the Internet
- The proposal cannot be evaluated by IETF experts for lack of competen=
ce
- The proposal cannot be modified if the IETF community thinks that it
needs modification
- The proposal does not fit with IETF policy
These are not the only points Harald makes, there are others, such as
bandwidth of the IETF advisors.
If Harald doesn't have time to address the Job MIB, that's understandab=
le.
The IETF area directors certainly have as much reason to be "swamped"
as the rest of us. And, I admit, to an area director, "Print Job MIB"
may not seem as central an issue as "Web security". I can sympathize
with the dynamics of the priority stack, here. But... then what are we
to do?
All I am asking for is an explanation of the current status of the Job =
MIB
charter and, if rejected, WHY.
In helping the IETF make a determination, I think it must be pointed ou=
t how
the Job MIB relates to the Internet and other IETF standards activities=