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

Alissa Cooper <alissa@cooperw.in> Mon, 20 March 2017 16:01 UTC

Return-Path: <alissa@cooperw.in>
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 1A158127B5A; Mon, 20 Mar 2017 09:01:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level:
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=tKJzsUKe; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=e57W2fKD
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 4GAaMkMDtthP; Mon, 20 Mar 2017 09:01:27 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33FC81314BA; Mon, 20 Mar 2017 09:01:23 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 84F1B20AF4; Mon, 20 Mar 2017 12:01:22 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Mon, 20 Mar 2017 12:01:22 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=QMAhmwPRWWW2PaOHp2 WBKUppbfi2XbCRGkY4n1i3kQc=; b=tKJzsUKepBBzM29SzNQKUgGPbEpEPshI1o RABB91bEUY3l/yi/YxgbMCwbyvONBv0G8vo8PM3BP7kEX90XkB99+2OiX00dRB4n V5PIWtHlLM9722cd6EqFI0PznM+haSL3Tz6ITqYItHVjyAmfDQeAGdYFLOZA1o5X YKriToKNcPW6XbJRFzQKMvGZOnZuvJLvcsKoMr/vqHUMXZmOkXJuZV1LlLHlfTr+ jQi5hDbHNoLcguHq8VO7IKWuteBldI0mYvnIMITinZpbFm1KzBMlil5vSh0Yif/C boWUmInuynAEgq/K3twVCjW4AKZgFccxYq+SEVw73SsI/8kEyamw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=QMAhmwPRWWW2PaOHp2WBKUppbfi2XbCRGkY4n1i3kQc=; b=e57W2fKD fQa6bIL0MJ5waabDeFEpDuyHOKT+kr2SGU4S7gGx1YnEbmTVqcX9M9pMdEZayLku mcAUHyDvGSr6hyDAxvZCX3VJFdRQ/5GO5fApFbNU7TY9ARF1kefCseINzRneJzU2 z1zoouaXQr/Vq0Y0I9ugVtOU6bo7tP1DCpyZ4MchM+mWy6Hv/PjSSSAgkrS76/4h ro/SuiWL5F6HHMjmHlMgIbVYTRR6rMHCkvq3PVZ2rC+5dHj+6hggzno9rGz5mIEw VPDmk8nnvpz2J0CdDuJVLTxyW31dsV1WaOObH/THHN/wELh7o5P7XWVsUMXF3fmW plwl5P+1gVQfUQ==
X-ME-Sender: <xms:0vzPWHxMet5cFvxs6W31CDrTMTG5Up-ONCcW9WUy0jw_Zg-RB-8luA>
X-Sasl-enc: uNEB6ryJGAR8lsoS6FZD+mV9b4TgwH+cin5Kbh6kb71Z 1490025682
Received: from sjc-alcoop-8812.cisco.com (unknown [128.107.241.169]) by mail.messagingengine.com (Postfix) with ESMTPA id DE884240A5; Mon, 20 Mar 2017 12:01:20 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <20170314090649.GB54939@elstar.local>
Date: Mon, 20 Mar 2017 12:01:19 -0400
Cc: Dan Romascanu <dromasca@gmail.com>, lmap-chairs@ietf.org, IESG <iesg@ietf.org>, draft-ietf-lmap-yang@ietf.org, lmap@ietf.org, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Content-Transfer-Encoding: quoted-printable
Message-Id: <19B46632-5DD0-434B-8393-84C97B30B702@cooperw.in>
References: <148916442967.6864.11561838065992971408.idtracker@ietfa.amsl.com> <20170314090649.GB54939@elstar.local>
To: =?iso-8859-1?Q?Mirja_K=FChlewind?= <ietf@kuehlewind.net>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lmap/_ASFuDdpB0vK0-eqpjokLuCfSCE>
Subject: Re: [lmap] =?iso-8859-1?q?Mirja_K=FChlewind=27s_Discuss_on_draft-iet?= =?iso-8859-1?q?f-lmap-yang-11=3A_=28with_DISCUSS_and_COMMENT=29?=
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: Mon, 20 Mar 2017 16:01:29 -0000

Hi Mirja,

Per our telechat discussion, could you provide clarification about what further information you need to be able to clear?

Thanks,
Alissa


> On Mar 14, 2017, at 5:06 AM, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> 
> 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/>
> 
> _______________________________________________
> lmap mailing list
> lmap@ietf.org
> https://www.ietf.org/mailman/listinfo/lmap