RFC support
This section lists what RFCs @node-net/netconf implements, where, and how it's been tested. Testing is against netopeer2 unless stated otherwise.
Protocol and transport
| RFC | Title | Support |
|---|---|---|
| 6241 | NETCONF | ✅ Built in: hello and capabilities, all base operations, confirmed commit with persist, typed <rpc-error>, pipelining |
| 6242 | NETCONF over SSH | ✅ Built in: end-of-message and chunked framing, switching to chunked framing on base:1.1, chunk-size limits |
| 4741, 4742 | NETCONF 1.0 | ✅ base:1.0 devices work, with end-of-message framing. Tested against netopeer2 through a profile that sets forceBaseVersion, since netopeer2 advertises 1.1: get-config, edit-config, validate, commit and configure() |
| 7589 | NETCONF over TLS | ✅ tls(): mutual X.509, TLS 1.2 minimum, server verified by CA or pinned fingerprint |
| 8071 | Call home | ✅ listenCallHome(), over SSH and TLS |
Data and datastores
| RFC | Title | Support |
|---|---|---|
| 6243 | With-defaults | ✅ with-defaults extension |
| 6022 | NETCONF monitoring | ✅ monitoring: <get-schema>, sessions, locks, statistics |
| 8342, 8526 | NMDA | ✅ nmda: <get-data>, <edit-data>, origins. Not yet: lock, unlock and validate on NMDA-only datastores |
| 8525, 7895 | YANG library | ✅ yang-library, also used to find namespaces for YANG paths |
| 5717 | Partial lock | ✅ partial-lock. Tested against the fake server only: no open-source server implements it |
| 9144 | Comparing NMDA datastores | ✅ compare. Tested against Clixon 7.9; netopeer2 doesn't implement it |
| 7950 §7.14, §7.15 | YANG 1.1 RPCs and actions | ✅ content.invoke() by path, with JSON input and output, and ops.action(). Tested against the fake server and the in-repo nncd server; netopeer2 needs a sysrepo subscriber in the container to answer an action, so it isn't used |
| 7950 §9.13 | YANG instance identifiers | ✅ The path API, with module names as in RFC 7951 |
| 7951, 7952 | JSON encoding of YANG data, and metadata | ✅ Typed by the server's schema: reads as JSON, and JSON config and filters, with RFC 7952 metadata for annotations and edit attributes |
Notifications
| RFC | Title | Support |
|---|---|---|
| 5277 | Event notifications | ✅ Built-in routing of <notification>, plus the notifications extension for <create-subscription> |
| 6470 | Base notifications | ✅ base-notifications: typed decoders |
| 8639, 8640 | Subscribed notifications | ✅ subscriptions |
| 8641 | YANG-Push | ✅ Periodic and on-change datastore subscriptions, in the same extension |
| 9196 | System and notification capabilities | ✅ capabilities() in the same extension. Tested against the fake server only: netopeer2 doesn't implement it |
Security
| RFC | Title | Support |
|---|---|---|
| 8341 | NACM | ✅ Enforced by the server. access-denied is a typed error tag, tested against netopeer2 as a user in no NACM group (over TLS, where the certificate names the user) |
| 4251–4254, 4256, 8332, 8709, 9142 | SSH | ✅ Via ssh2. The defaults leave out SHA-1 (ssh-rsa, hmac-sha1), SHA-1 key exchange, CBC ciphers and DSA; enabling a legacy algorithm is explicit and logged on every connection (unit-tested). Keyboard-interactive authentication (4256) is unit-tested only |
| 8446, 9325 | TLS 1.3, TLS recommendations | ✅ TLS 1.2 minimum, 1.3 preferred. TLS 1.2 uses only ECDHE with AES-GCM or ChaCha20-Poly1305 by default |
Not supported
- NETCONF over SOAP or BEEP (4743, 4744) and the old TLS mapping (5539) are obsolete.
- X.509 certificates for SSH (6187): ssh2 doesn't support them. Use TLS for certificate authentication.
- RESTCONF (8040) is a different protocol.
On the radar
These drafts are expected to fit as extensions or transports, without changes to the core: private candidate datastores, transaction IDs, list pagination, NETCONF over QUIC, and the system datastore.