Re: [Netconf] Fwd: I-D Action: draft-bierman-netconf-restconf-00.txt

[Andy Bierman <[e-mail]>]

On Wed, Sep 4, 2013 at 10:24 PM, Juergen Schoenwaelder <
[e-mail]> wrote:

> Hi,
>
> I am wondering whether the authors did consider approaches that do not
> require to construct complex URIs. See for example this I-D that
> provides some warnings:
>
>    http://tools.ietf.org/html/draft-nottingham-uri-get-off-my-lawn-02
>
>

It is a tradeoff whether the YANG-derived text is in the URI
or in the message body.  I do not agree that using a URI for this
purpose is a problem, any more than using YANG at all
is a problem.  Schema-based applications need stable (static) URIs.
Discovering the entire set of URIs on a device each session is
too inefficient.


Is .well-known really intended to be the root of a complex URI
> namespace for applications like RESTCONF? For example, RFC 5785
> says:
>
>    However, in keeping with the Architecture of the World-
>    Wide Web [W3C.REC-webarch-20041215], well-known URIs are not intended
>    for general information retrieval or establishment of large URI
>    namespaces on the Web.
>
> Does it make sense to run this proposal through some application area
> experts for early review and comment?
>

Probably -- we added .well-known because we thought it was needed.
If not, that saves 12 useless characters in every request.


>
> /js
>
>

Andy


> On Wed, Sep 04, 2013 at 05:03:46PM -0700, Andy Bierman wrote:
> > FYI,
> >
> > The initial RESTCONF protocol draft has been published.
> > Support for notifications has not been added yet.
> > See the change log for a summary of the updates
> > since the yang-api-01 draft.
> >
> >
> > Andy
> >
> >
> > ---------- Forwarded message ----------
> > From: <[e-mail]>
> > Date: Wed, Sep 4, 2013 at 4:59 PM
> > Subject: I-D Action: draft-bierman-netconf-restconf-00.txt
> > To: [e-mail]
> >
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> >
> >
> >         Title           : RESTCONF Protocol
> >         Author(s)       : Andy Bierman
> >                           Martin Bjorklund
> >                           Kent Watsen
> >                           Rex Fernando
> >         Filename        : draft-bierman-netconf-restconf-00.txt
> >         Pages           : 93
> >         Date            : 2013-09-04
> >
> > Abstract:
> >    This document describes a RESTful protocol that provides a
> >    programmatic interface over HTTP for accessing data defined in YANG,
> >    using the datastores defined in NETCONF.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-bierman-netconf-restconf
> >
> > There's also a htmlized version available at:
> > http://tools.ietf.org/html/draft-bierman-netconf-restconf-00
> >
> >
> > Please note that it may take a couple of minutes from the time of
> submission
> > until the htmlized version and diff are available at tools.ietf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > I-D-Announce mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > Internet-Draft directories: http://www.ietf.org/shadow.html
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> > _______________________________________________
> > Netconf mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/netconf
>
>
> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: [phone]         Campus Ring 1, 28759 Bremen, Germany
> Fax:   [phone]         <http://www.jacobs-university.de/>
>