search

netconf-wg / netconf-next

A repository to collection feature requests for NETCONF
0 stars 0 forks source link

Deprecate non-NMDA #27

Open jgcumming opened 10 months ago

jgcumming commented 10 months ago

We could deprecate anything that is not NMDA and ensure that all 'behaviours' intended by the original non-NMDA operations are retained and updated into NMDA(-style) operations.

abierman commented 9 months ago

Do not support. Not specific enough. NETCONF is widely used in non-NMDA deployment.

BalazsLengyel commented 9 months ago

OBJECT. NETCONF is widely used in non-NMDA deployment. In environments where Netconf is not the only management protocol used this would mean that the other protocol also needs to be updated. This is the situation with 3GPP OAM where both Netconf and a simple REST/OpenAPI protocol is also used (not Restconf). This would prevent 3GPP OAM from using Netconf-next.

abierman commented 9 months ago

There is an emerging standard called CORECONF that is intended for IoT devices, which are not likely to need NMDA.

Non-NMDA deployment must be supported. NMDA is not being widely used. It is not applicable to all use cases for YANG data modeling, so the effort to remove all non-NMDA operations and protocols is not helpful

jgcumming commented 9 months ago

Whilst I whole-heartedly agree that non-NMDA NETCONF is very widely deployed and actively in use. My question, and perhaps something for the interim, is whether this NETCONF-next activity is targeting a 2.0 implementation or a 1.x implementation.

If we are targeting a 2.0 then we have the opportunity to clean up the protocol to provide a smaller and cleaner set of functions without the requirement to be backwards compatible.

If the intention of NETCONF-next is a 1.x then this is not the case and we should support backwards compatibility.