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, 21 March 2017 11:55 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 EBE9D1297BE; Tue, 21 Mar 2017 04:55:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=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 7SoPczLcXgza; Tue, 21 Mar 2017 04:55:20 -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 DBEE71297A5; Tue, 21 Mar 2017 04:55:19 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id A981C6BA; Tue, 21 Mar 2017 12:55:18 +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 a_XFRkgiGZP2; Tue, 21 Mar 2017 12:55:17 +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, 21 Mar 2017 12:55:18 +0100 (CET)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id 3FF5520038; Tue, 21 Mar 2017 12:55:18 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id M3WtSYLILZrl; Tue, 21 Mar 2017 12:55:17 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id B35D720036; Tue, 21 Mar 2017 12:55:17 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 59EAA3EF125C; Tue, 21 Mar 2017 12:55:22 +0100 (CET)
Date: Tue, 21 Mar 2017 12:55:22 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
Cc: Dan Romascanu <dromasca@gmail.com>, lmap-chairs@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-lmap-yang@ietf.org, lmap@ietf.org
Message-ID: <20170321115522.GA35872@elstar.local>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>, Dan Romascanu <dromasca@gmail.com>, lmap-chairs@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-lmap-yang@ietf.org, lmap@ietf.org
References: <148916442967.6864.11561838065992971408.idtracker@ietfa.amsl.com> <20170314090649.GB54939@elstar.local> <0AEF216F-3B1D-46FE-96B5-38165D6C1308@kuehlewind.net> <20170320172731.GA33917@elstar.local> <2A9728CD-7ACA-4D49-A754-EC7A06070963@kuehlewind.net> <20170321064636.GA34900@elstar.local> <FBFBCEE9-D3E9-47B9-99B1-10A9C9831937@kuehlewind.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
X-Clacks-Overhead: GNU Terry Pratchett
Content-Transfer-Encoding: 8bit
In-Reply-To: <FBFBCEE9-D3E9-47B9-99B1-10A9C9831937@kuehlewind.net>
User-Agent: Mutt/1.6.0 (2016-04-01)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lmap/Sg2lEb3VI3IoBFhsIckCSbEasGk>
Subject: Re: [lmap] Mirja Kühlewind's Discuss on draft-ietf-lmap-yang-11: (with DISCUSS and COMMENT)
X-BeenThere: lmap@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
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, 21 Mar 2017 11:55:22 -0000

On Tue, Mar 21, 2017 at 09:11:09AM +0100, Mirja Kuehlewind (IETF) wrote:
> Hi Jürgen,
> 
> thanks for you replies. I went back an had another look at the framework document which answered some of my questions. I guess the minimum you can do is to make the reference to RFC7594 normative (as well as the reference to I-D.ietf-lmap-information-model as Benoit mentioned in this comment). I guess without trying to implement it, I will not be able to figure out if there is anything missing or if I’m missing something and as such I will clear my discuss now.

To me, it feels a bit strange to make RFC 7594 normative but if there
is IESG consensus that RFC 7594 should be normative I will implement
the change and hold my breath.
 
> I still think that it could be good to give some further guidance on how connectivity is established. Something like, in most cases the controller will connect the MA and the controller should make sure that it reconnects frequently based on the timeout configuration of the MA. If the MA e.g. is behind a NAT, the MA must establish the initial connection and try to reconnect when the timeout expires. Btw. is it enough to open a transport connection or do you mean by checking connectivity that there also should be some data transmitted to ensure that the controller is no only reachable but also active?

Depends to some extend on the protocol used. I think it is more than a
TCP connection, you also need to successfully authenticate (I
think). And then some protocols immediately become chatty - NETCONF
has a <hello> exchange, with RESTCONF things could be silent but I
would assume a controller will likely fetch some status information.
(When you kid returns home, you likely ask how it is doing. ;-)

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