configuration: writable MIB modules versus NETCONF/YANG modules
David Meyer <[email protected]> Fri, 14 Feb 2014 07:12:41 -0800
| Newsgroups | gmane.ietf.ops |
|---|---|
| Message-ID | <CAHiKxWiHORkXy-zRz9Zhk3q7YOAcMYRpAj4gp7ojAJY+CfY_wA@mail.gmail.com> |
>> Dear all, >> >> We occasionally see read-write MIB module proposals within the IETF. >> However, the write capabilities of those MIB modules are rarely >> implemented. >> >> While discussing this issue with the MIB doctors, we arrive to the >> conclusion that it's now time to set the direction for future MIB >> developments within the IETF. Basically, let's not specify read-write >> MIB modules unless we have a good reason. Read-only MIB modules >> are still fine though, as SNMP is clearly used for monitoring purposes. >> >> Here is the statement we came up with: >> >> The OPS area recommends the use of NETCONF/YANG standards for >> configuration. IETF working groups are therefore encouraged to use the >> NETCONF/YANG standards for configuration, specifically in new >> charters. SNMP MIB modules modifying persistent configuration state >> should only be produced by working groups in cases of clear utility >> and consensus to use SNMP write operations for configuration. >> I>> deally, this should become an IESG statement. >> Your feedback is most welcome. >> >> Regards, the MIB doctors & Benoit Eminently reasonable and needed. +1 --dmm