Hi Sheppy,
Updating a standard is a fairly difficult task. This is deliberate; If standards were constantly changing, it would be hard to get consistent implementations across products. The IETF would need to publish a new RFC to obsolete the existing RFC. Before they would do this, the IESG (standards approval committee) would need to verify that the change to the standard represented IETF consensus. So any proposed change would need to be discussed by the IETF community before being accepted. There are likely other changes people would like, so changing the standard would likely include a number of changes, all of which would need IETF community consensus. Updating a standard MIB is a slightly more difficult task than normal. MIB modules contain compliance statements to ensure/encourage interoperability across implementations. There are specific rules about how to update a MIB so that existing compliant implementations do not become non-compliant. That's why writing up a proposal is important - so the IETF can read/study your proposal in detail. A simpler approach would be to write a new MIB module that could be implemented in addition to the standard, without updating the standard MIB module. David Harrington <mailto:[email protected]> [email protected] +1-603-828-1401 From: [email protected] [mailto:[email protected]] On Behalf Of Sheppy Reno Sent: Tuesday, September 11, 2012 12:15 PM To: Melinda Shore Cc: [email protected] 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
