Re: Updating a published MIB
t.petch <[email protected]> Tue, 30 Jul 2013 09:53:55 +0100
| Newsgroups | gmane.ietf.ops |
|---|---|
| Message-ID | <[email protected]> |
You will find a three page description of what you can and cannot do in RFC4181 pp.28-31. This refers back to RFC2578 which is the authoritative statement of what can and cannot be done. And then there is the [email protected] mailing list which is where most of those with expertise in MIB modules lurk. No, it is not obvious:-( Tom Petch ----- Original Message ----- From: "Olle E. Johansson" <[email protected]> To: <[email protected]> Sent: Monday, July 29, 2013 8:52 PM Hi! The SIP MIB in RFC 4780 contains a SipTCTransportProtocol entry. The SIPcore group is about to add another transport (websockets), which means that we will have to update RFC 4780 with a new bit for websocket transports. I've asked around and it seems to be a lack of information about the process of updating a published MIB. The IANA is not involved. And reading the wiki entry on OPS and MIB doctors seems to contain a lot of information about *new* MIBs but nothing on updates. So my question is what the process is for changing parameters or adding new OIDs. Thanks for your response! Apologies if I did miss something obvious. /Olle