Re: [Netconf] Verifing session consensus on RESTCONF as WG item with the maillist

[Juergen Schoenwaelder <[e-mail]>]

On Sun, Nov 24, 2013 at 02:16:36PM +0000, Ersue, Mehmet (NSN - DE/Munich) wrote:
> 
> Following text is proposed to use for the charter update:
> "  3. Develop a RESTful protocol (RESTCONF) that provides a programmatic interface for accessing data defined in YANG, using the datastores defined in NETCONF. The three parts concerning RESTCONF protocol, the transport binding over HTTP and the YANG patch operation will be prepared modular and in separate drafts. This enables to add a new transport binding at a later stage."
> 

Technical question:

I do wonder how you can separate the HTTP transport binding out of a
RESTful protocol without making the specification rather complicated
to read and understand. After all, you will make assumptions about
what HTTP provides in many places (e.g. what is carried in HTTP
message headers or HTTP mechanisms like etags are used). Is there an
example somewhere I can look at to understand what this separation is
going to look like? And which problem are we solving by separating
this out?

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1, 28759 Bremen, Germany
Fax:   [phone]         <http://www.jacobs-university.de/>