Sheppy You should look too at RFC4181 which gives the current guidelines for writing a MIB module, which is what you would, de facto, be doing. The practice has moved on and this RFC will give you some idea of what would be involved in making even a one word change to a MIB module from an earlier time:-(
Tom Petch ----- Original Message ----- From: "Sheppy Reno" <[email protected]> To: "Melinda Shore" <[email protected]> Cc: <[email protected]> Sent: Tuesday, September 11, 2012 5:15 PM Subject: Re: [OPSAWG] Addition of Available Space to Host-Resources-MIB On Tue, Sep 11, 2012 at 11:57 AM, Melinda Shore <[email protected]>wrote: > On 9/11/12 7:48 AM, Sheppy Reno wrote: > > I’ve been reading through the IETF site a bit, but I’m still not sure as > > to the best process to get this implemented. I was hoping someone on > > here could give me some tips on proceeding with this. From what I can > > see, I just need to update RFC2790 with the below information and > > resubmit. > > Probably the best approach would be to write up your proposal in the > form of an internet draft describing the problem you're encountering, > your proposal, and the rationale for your proposal. > Melinda > Melinda, Thanks for the prompt response. My issues arise from not knowing how to properly submit this as an internet draft. http://www.ietf.org/ietf-ftp/1id-guidelines.html seems to be more geared towards new drafts than to updates for current RFCs. From the information on that page I would assume that the proper way to proceed would be to modify RFC2790, add in the Internet Draft comments in the header, remove anything mentioning RFC, etc. I'm just worried because this seems like a counterintuitive approach to submitting a modification. Is there a process by which I just submit the changes instead of rebuilding the entire RFC this is based on? I don't mind doing the extra work if a complete rewrite of the original RFC is required, but I want to make sure I'm making the submission properly. Thanks, Sheppy ------------------------------------------------------------------------ -------- > _______________________________________________ > OPSAWG mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/opsawg > _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
