Re: [netconf] time to meet today after 5pm

[Kent Watsen <[e-mail]>]

>    What do you mean by "REST-like"?
> 
> With RESTCONF, the YANG models supported by the RESTCONF server result in it exposing RESTful or REST-like APIs to the RESTCONF client. You can view the RESTCONF server as supporting a set of REST APIs with some additional conventions/requirements on the structure on the URIs, such as the root of the RESTCONF API, use of specific HTTP response codes, etc.


The root of the API is discovered via /.well-known/host-meta, per https://tools.ietf.org/html/rfc8040#section-3.1.

As for what is RESTCONF, from Sections 1.2:

   RESTCONF is not intended to replace NETCONF, but rather to provide an
   HTTP interface that follows Representational State Transfer (REST)
   principles [REST-Dissertation] and is compatible with the NETCONF
   datastore model.


And Section 1.3:

   RESTCONF combines the simplicity of HTTP with the predictability and
   automation potential of a schema-driven API.  Knowing the YANG
   modules used by the server, a client can derive all management
   resource URLs and the proper structure of all RESTCONF requests and
   responses.  This strategy obviates the need for responses provided by
   the server to contain Hypermedia as the Engine of Application State
   (HATEOAS) links, originally described in Roy Fielding's doctoral
   dissertation [REST-Dissertation], because the client can determine
   the links it needs from the YANG modules.


Kent