Re: configuration: writable MIB modules versus NETCONF/YANG modules

Balazs Lengyel <[email protected]> Fri, 14 Feb 2014 15:34:09 +0100
Newsgroups gmane.ietf.ops
Message-ID <[email protected]>
Hello Benoit,

We have a use case that might end up in an IETF RFC, which involves
updating a small set of data very frequently (2 times/sec).

It is kind of on the border of configuration and SDN/routing.

What would be a good protocol for this purpose? Is it still Netconf,
or a custom protocol?

regards Balazs

On 2014-02-14 01:39, Benoit Claise
wrote:

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.

Ideally, this should become an IESG statement.

Your feedback is most welcome.

Regards, the MIB doctors & Benoit

_______________________________________________
OPS-AREA mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ops-area

--
Balazs Lengyel Ericsson Hungary Ltd.
System Manager
ECN: 831 7320 Tel: +36-1-437-7320
Mobile: +36-70-330-7909 email: [email protected]

_______________________________________________
OPS-AREA mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ops-area