Re: [Netconf] Representing URLs

Andy Bierman <andy@yumaworks.com> Sat, 07 December 2013 01:54 UTC

Return-Path: <andy@yumaworks.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A3D01AE098 for <netconf@ietfa.amsl.com>; Fri, 6 Dec 2013 17:54:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level:
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_64=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZoRvQN3tNXiL for <netconf@ietfa.amsl.com>; Fri, 6 Dec 2013 17:54:23 -0800 (PST)
Received: from mail-qe0-f46.google.com (mail-qe0-f46.google.com [209.85.128.46]) by ietfa.amsl.com (Postfix) with ESMTP id 7D6111AD942 for <netconf@ietf.org>; Fri, 6 Dec 2013 17:54:23 -0800 (PST)
Received: by mail-qe0-f46.google.com with SMTP id a11so1136293qen.5 for <netconf@ietf.org>; Fri, 06 Dec 2013 17:54:19 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=diYaXjXzQ/MMIYN9kwlsNq+mUU7u8laLYUFDQeSSM7g=; b=MbbLicWTKzXkzqaSBXtGMICqO/9vWZLb9+qbIbW+PeVjcdjLqV74PKJwY6vbvnxzOl UgPhvOg+4nLwtCPFN8okq20/g/qZaRvEqOoL0op5EOiPk+PYdXQs3scD/Uvuw7eI7P9E dGcn3rMuYToCeCv64wKnp0xBcq6/B+j/D4PqdPYPH8QzBtxAhle6c1Wmvi2/5cTwL1ga Y6XOZV5j3VWCSekIJdy1M6K9H4fcRadOl7pgaBIjLxGn/bPXyqgSfKnNa27jI7Ax9riL FGRWXdJFgfWqojuZZHa12zRQYiGiFQXmPGH1Q2EMzzOycZZCPT115acLk+iL5aqfCvPu 6Vnw==
X-Gm-Message-State: ALoCoQmC9XD30xcZwyDS62XbgJ/prMWN+zLKMIbl9+6X4y3UDbBXwkXtmue9TzaPBmvSvmd6nBaU
MIME-Version: 1.0
X-Received: by 10.229.194.1 with SMTP id dw1mr11675941qcb.20.1386381259307; Fri, 06 Dec 2013 17:54:19 -0800 (PST)
Received: by 10.140.48.75 with HTTP; Fri, 6 Dec 2013 17:54:19 -0800 (PST)
In-Reply-To: <20131206.222720.369437985.mbj@tail-f.com>
References: <E67E6E74-F554-4D5A-ABFE-0C567A9743B3@nic.cz> <CAFFjW4iJVmPsoQLPMKJSJXWMbaAdpFcZvUcztqk2z+h0eFq0ww@mail.gmail.com> <CABCOCHRHYggkrm8jYa1wjWCY7zJG-QcVjbDguQGdK8xDduOvMQ@mail.gmail.com> <20131206.222720.369437985.mbj@tail-f.com>
Date: Fri, 6 Dec 2013 17:54:19 -0800
Message-ID: <CABCOCHR8eB+NkFhYKOaiWo_RGa4DLpObkWz2-gfnmEkRm+-0cA@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Martin Bjorklund <mbj@tail-f.com>
Content-Type: multipart/alternative; boundary=001a11c2c7367c4ac204ece80af4
Cc: Netconf <netconf@ietf.org>, draft-bierman-netconf-restconf@tools.ietf.org
Subject: Re: [Netconf] Representing URLs
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Dec 2013 01:54:24 -0000

On Fri, Dec 6, 2013 at 1:27 PM, Martin Bjorklund <mbj@tail-f.com>; wrote:

> Andy Bierman <andy@yumaworks.com>; wrote:
> > Hi,
> >
> > You have raised an important RESTCONF issue, which is the
> > client processing of server resource URIs.  I think the
> > client should be able to use the Location header URI for
> > all CRUD access to the data resource.
> >
> > That's why the /restconf/config and /restconf/operational split
> > is broken. In order to retrieve operational data, the client
> > has to parse the URI and change it -- not too REST-ful ;-)
>
> RESTCONF's uri scheme is already not too REST-ful.  The uri's are
> deterministic and known by both client and server.  The Location
> header only works when the client has created a resource, but it
> cannot be used to discover uris on the server.
>
> The split into config and operational does not change this.
>
>
OK, but the split was supposed to get rid of the config query param
but it didn't.  Now config=true|false applies only to the /restconf/data
resource, not the /restconf/config resource.

I think we are better off without the /restconf/config resource and
just have /restconf/data + content=enum (config|operational|both)
[default:config]
The ETag and Last-Modified values are only returned when content=config.
They are only maintained for config=true data nodes.




>
> /martin
>


Andy