Re: [Netconf] RESTCONF and draft-ietf-appsawg-uri-get-off-my-lawn-04 (on the IESG telechat this week)

Andy Bierman <andy@yumaworks.com> Tue, 13 May 2014 00:40 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 98F341A07D4 for <netconf@ietfa.amsl.com>; Mon, 12 May 2014 17:40:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 Ez44dXeiJYqm for <netconf@ietfa.amsl.com>; Mon, 12 May 2014 17:40:22 -0700 (PDT)
Received: from mail-qg0-f43.google.com (mail-qg0-f43.google.com [209.85.192.43]) by ietfa.amsl.com (Postfix) with ESMTP id 4D2AD1A07D0 for <netconf@ietf.org>; Mon, 12 May 2014 17:40:22 -0700 (PDT)
Received: by mail-qg0-f43.google.com with SMTP id 63so8727371qgz.30 for <netconf@ietf.org>; Mon, 12 May 2014 17:40:16 -0700 (PDT)
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=BCSgcJZeeFXrsdmjEy/n9wvkriOzfKKVhJ/Gy7zafIA=; b=PbTYIzGA0zSyMVRdUEA3YMMzmazz7puVIdQ52ZtD1OM0r8RbwcVFG/d6FBZlxbGn5m 0i4LnS3qOYGguyOzmKuRczdtCrHrHqt3JFPcuYAyq8qTuhWvGdcepmaFOP0/Yeae3+yH /SXxBMN7Q3pklgkOrlLPsQpp6FgbgzJV7Ct8x9J/1rWiiFqEJY/tgW5DIs6o2yOb8V2k 73YWsQPWiaVFmA3QbARcYJPfaJiss0YeSRB+PGH8Nc5U/m5Yfj9x6+ISn5Au9pzqkZsk TVyZLWqPrlef1IgdiHhtx5V0bbiZzIpfiYg7XSeCH61IkEUUoNfmiA4YIB+1Wub7EEqy TQgw==
X-Gm-Message-State: ALoCoQm8xJPHz2GOVGfJzW/3M5kPhSIuREgEZlOio9R0jw6lbwSI+LdSGxHxGyrjeahSN6DP6U7d
MIME-Version: 1.0
X-Received: by 10.140.41.75 with SMTP id y69mr40638639qgy.34.1399941616017; Mon, 12 May 2014 17:40:16 -0700 (PDT)
Received: by 10.140.104.49 with HTTP; Mon, 12 May 2014 17:40:15 -0700 (PDT)
In-Reply-To: <CABCOCHQ4LoM_xcRH-j=3gYo_eBcOjnLmifed1HNa7mt5_k8xAQ@mail.gmail.com>
References: <53714FEC.2030709@cisco.com> <CABCOCHQ4LoM_xcRH-j=3gYo_eBcOjnLmifed1HNa7mt5_k8xAQ@mail.gmail.com>
Date: Mon, 12 May 2014 17:40:15 -0700
Message-ID: <CABCOCHTMRwSh32owC7E_XCmFm6abcVF4cRigPCz9nBo5R7nQcA@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Benoit Claise <bclaise@cisco.com>
Content-Type: multipart/alternative; boundary="001a11c126babab8ee04f93d4e05"
Archived-At: http://mailarchive.ietf.org/arch/msg/netconf/IhOtIYBzSvvfuzEto1t6cOeJG9A
Cc: NETCONF <netconf@ietf.org>
Subject: Re: [Netconf] RESTCONF and draft-ietf-appsawg-uri-get-off-my-lawn-04 (on the IESG telechat this week)
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: Tue, 13 May 2014 00:40:24 -0000

On Mon, May 12, 2014 at 4:06 PM, Andy Bierman <andy@yumaworks.com> wrote:

>
>
>
> On Mon, May 12, 2014 at 3:49 PM, Benoit Claise <bclaise@cisco.com> wrote:
>
>> Dear all,
>>
>> Please review the http://tools.ietf.org/html/draft-ietf-appsawg-uri-get-
>> off-my-lawn-04 BCP in light of RESTCONF and let me know.
>>
>>
>
> I think RESTCONF violates sec 2.3 wrt/ structure within the URI path.
> This is by design.  The document complains about ad-hoc mechanisms,
> and RESTCONF is in complete agreement with that.  The RESTCONF
> mapping of data nodes to resource identifiers is the opposite of ad-hoc.
> It allows multi-vendor naming without collisions and dramatically
> improved application efficiency.  (It is arguable that configuration
> management
> of complex routers would be impossible with a robust schema language
>

oops -- s/with/without/ in previous line


> like YANG).
>
>
> Regards, Benoit
>>
>>
> Andy
>
>