Re: [netconf] time to meet today after 5pm

Kent Watsen <kent+ietf@watsen.net> Wed, 10 April 2019 13:50 UTC

Return-Path: <0100016a07840591-b6aa476d-1837-447f-907d-93c137a36ed7-000000@amazonses.watsen.net>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 301FB12039B; Wed, 10 Apr 2019 06:50:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com
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 PY4PM1zsjk4H; Wed, 10 Apr 2019 06:50:56 -0700 (PDT)
Received: from a8-88.smtp-out.amazonses.com (a8-88.smtp-out.amazonses.com [54.240.8.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A65101203A7; Wed, 10 Apr 2019 06:50:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1554904254; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:Feedback-ID; bh=WHt7v6dYPHsTe/G3XRJDaFDEMyU+ec6wxyVJidf8HBQ=; b=P/cwRVn1hGjnIdeXrZQvv4d2X7l1YuE8W2jhwS71EUuJypWIa/mItaS6pTKQg47V O+L8gUHBiVgSX1QZJOMOp5Hnr/150bxf/jjpQObv2riS5oTRFYwAQUhYVcb4JAltQj2 3EmMfK0EI28dHkTmDoTO3XvyDEfhQmuRQOxxpdZc=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Kent Watsen <kent+ietf@watsen.net>
In-Reply-To: <E0BA5C69-47A0-4280-B75D-D3B39AA78AC6@cisco.com>
Date: Wed, 10 Apr 2019 13:50:53 +0000
Cc: Mark Nottingham <mnot@mnot.net>, Patrick McManus <mcmanus@ducksong.com>, "httpbis-chairs@ietf.org" <httpbis-chairs@ietf.org>, "netconf-chairs@ietf.org" <netconf-chairs@ietf.org>, "netconf@ietf.org" <netconf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <0100016a07840591-b6aa476d-1837-447f-907d-93c137a36ed7-000000@email.amazonses.com>
References: <01000169def07790-5f902f1b-ddce-438b-8e05-d4b7e82818bc-000000@email.amazonses.com> <CAOdDvNoDFoa30tJ8XDz482_38rw8+ajwW4+dSx7s_psoFY7ukQ@mail.gmail.com> <56E946DC-A690-4B1E-8FB5-683473955C5D@gmail.com> <20190404.163346.857364419603319540.mbj@tail-f.com> <CAOdDvNq4bLXtdDD7WdXbH-e14-i_yy50ADm59YtOKW5buaCjOg@mail.gmail.com> <01000169e94f9d0d-7f85f47b-9f92-41a2-94b1-0061bb9bdb3d-000000@email.amazonses.com> <B21C3F25-221B-4EE3-A981-D4EE49864C06@cisco.com> <1783839F-4A70-46BA-8DC4-C386CE8A07C0@mnot.net> <E0BA5C69-47A0-4280-B75D-D3B39AA78AC6@cisco.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
X-Mailer: Apple Mail (2.3445.102.3)
X-SES-Outgoing: 2019.04.10-54.240.8.88
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/3qB5Saz-kuZ5EcvjCaCGdxj62W0>
Subject: Re: [netconf] time to meet today after 5pm
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Wed, 10 Apr 2019 13:50:58 -0000


>    What do you mean by "REST-like"?
> 
> With RESTCONF, the YANG models supported by the RESTCONF server result in it exposing RESTful or REST-like APIs to the RESTCONF client. You can view the RESTCONF server as supporting a set of REST APIs with some additional conventions/requirements on the structure on the URIs, such as the root of the RESTCONF API, use of specific HTTP response codes, etc.


The root of the API is discovered via /.well-known/host-meta, per https://tools.ietf.org/html/rfc8040#section-3.1.

As for what is RESTCONF, from Sections 1.2:

   RESTCONF is not intended to replace NETCONF, but rather to provide an
   HTTP interface that follows Representational State Transfer (REST)
   principles [REST-Dissertation] and is compatible with the NETCONF
   datastore model.


And Section 1.3:

   RESTCONF combines the simplicity of HTTP with the predictability and
   automation potential of a schema-driven API.  Knowing the YANG
   modules used by the server, a client can derive all management
   resource URLs and the proper structure of all RESTCONF requests and
   responses.  This strategy obviates the need for responses provided by
   the server to contain Hypermedia as the Engine of Application State
   (HATEOAS) links, originally described in Roy Fielding's doctoral
   dissertation [REST-Dissertation], because the client can determine
   the links it needs from the YANG modules.


Kent