Header Only - DO NOT REMOVE - Extreme Networks

RESTCONF API requirements

What are the mandatory RESTCONF API requirements to be complied by an application/server exposing RESTCONF API (with XML or JSON payload) ? FYI, I already gone through the draft-ietf-netconf-restconf-09.

Thanks in advance !


3 replies

Userlevel 7
Hi Anu,
Sorry to have kept you waiting on this one. It seems that is because there hasn't been a good answer to provide until recently.
I'm told that REST APIs are planned for a later release and are expected to follow the Open API (Swagger) model.
Userlevel 5
Hi Anu,

Add RESTCONF Reference Documentation:

Userlevel 7

I'd like to add a few links regarding RESTCONF and OpenConfig to help people who want to find out what this is all about:

IMHO slightly better URL to ExtremeXOS RESTCONF documentation than the above: https://rawgit.com/extremenetworks/EXOS_Apps/master/REST/docs/RESTCONF.html

RESTCONF entry point on Extreme Network's GitHub presence: https://github.com/extremenetworks/EXOS_Apps/tree/master/REST

ExtremeXOS 22.4.1 release announcement (announcing RESTCONF support) on The Hub: https://community.extremenetworks.com/extreme/topics/extremexos-22-4-1-is-now-available

ExtremeXOS 22.4.1 release notes section on RESTCONF: https://documentation.extremenetworks.com/release_notes/ExtremeXOS/22.4.1-Patch1-2/EXOS_Release_Note...

RFC 8040, RESTCONF Protocol: https://tools.ietf.org/html/rfc8040

OpenConfig: http://www.openconfig.net/

OpenConfig calls itself

Vendor-neutral, model-driven network management designed by users

I am quite excited to see Extreme implementing RESTCONF and OpenConfig support. 🙂