Re: [lmap] Mirja Kühlewind's Discuss on draft-ietf-lmap-yang-11: (with DISCUSS and COMMENT)

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Tue, 14 March 2017 09:06 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: lmap@ietfa.amsl.com
Delivered-To: lmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2ED01294E0; Tue, 14 Mar 2017 02:06:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 NaUedOe50_3p; Tue, 14 Mar 2017 02:06:55 -0700 (PDT)
Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A092F129529; Tue, 14 Mar 2017 02:06:48 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id 70EED7A2; Tue, 14 Mar 2017 10:06:47 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.205]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id z-iSGeZNzNXe; Tue, 14 Mar 2017 10:06:46 +0100 (CET)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Tue, 14 Mar 2017 10:06:47 +0100 (CET)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 0C2872003D; Tue, 14 Mar 2017 10:06:47 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id lOHLe1D-q-Ha; Tue, 14 Mar 2017 10:06:46 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 5C1C020014; Tue, 14 Mar 2017 10:06:46 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id BEBFB3EBBDAD; Tue, 14 Mar 2017 10:06:49 +0100 (CET)
Date: Tue, 14 Mar 2017 10:06:49 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Mirja =?iso-8859-1?Q?K=FChlewind?= <ietf@kuehlewind.net>
Message-ID: <20170314090649.GB54939@elstar.local>
Mail-Followup-To: Mirja =?iso-8859-1?Q?K=FChlewind?= <ietf@kuehlewind.net>, The IESG <iesg@ietf.org>, draft-ietf-lmap-yang@ietf.org, Dan Romascanu <dromasca@gmail.com>, lmap-chairs@ietf.org, lmap@ietf.org
References: <148916442967.6864.11561838065992971408.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
X-Clacks-Overhead: GNU Terry Pratchett
Content-Transfer-Encoding: 8bit
In-Reply-To: <148916442967.6864.11561838065992971408.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.6.0 (2016-04-01)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lmap/FxCf2NvTv68zD0UbEsyvejOSqAU>
Cc: Dan Romascanu <dromasca@gmail.com>, lmap-chairs@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-lmap-yang@ietf.org, lmap@ietf.org
Subject: Re: [lmap] =?iso-8859-1?q?Mirja_K=FChlewind=27s_Discuss_on_draft-ietf?= =?iso-8859-1?q?-lmap-yang-11=3A_=28with_DISCUSS_and_COMMENT=29?=
X-BeenThere: lmap@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: Large Scale Measurement of Access network Performance <lmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lmap>, <mailto:lmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lmap/>
List-Post: <mailto:lmap@ietf.org>
List-Help: <mailto:lmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lmap>, <mailto:lmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Mar 2017 09:06:58 -0000

On Fri, Mar 10, 2017 at 08:47:09AM -0800, Mirja Kühlewind wrote:
> 
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> This draft does not specify a bootstrapping process (see RFC 7594 5.1. 
> Bootstrapping Process) and says:
> "Pre-Configuration Information: This is not modeled explicitly since
> bootstrapping information is outside the scope of this data model."
> So when and where and how will this be specified?

There is work ongoing in NETCONF to provide different pieces for
bootstrapping.

- draft-ietf-netconf-keystore

  a model for managing keys
  
- draft-ietf-netconf-netconf-client-server

  a model for managing NETCONF client and server config

- draft-ietf-netconf-restconf-client-server

  a model for managing RESTCONF client and server config

- draft-ietf-netconf-ssh-client-server

  a model providing NETCONF over SSH config details

- draft-ietf-netconf-tls-client-server
 
  a model providing NETCONF over TLS config details

- draft-ietf-netconf-zerotouch

  a mechanism for loading bootstrapping information

> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Also it is not clear when and how to perform configuration actions. To be
> a fully function protocol more guidance is needed. Not sure if that is
> even the intention of this document but I don't see any other documents
> that serves this purpose in the lmap queue. (And the milesstones are not
> up to date and don't indicate with document maps to which milestone.)

When and how is up to the controller design. The fully functioning
protocol falls out of the YANG data model - once you have YANG data
model, you are ready to go. That said, there is a currently expired
WG document providing more details.

https://tools.ietf.org/html/draft-ietf-lmap-restconf-03

The idea here was just provide an explanation how the LMAP data model
works together with RESTCONF.

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