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

On 25 Nov 2013, at 10:15, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:

> 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?

Indeed, and also the use of HTTP methods is crucial.

IMO, what makes sense is to factor out YANG Patch because, in principle, other patch formats (media types) may be supported instead/in parallel.

Lada

> 
> /js
> 
> -- 
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf

--
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C