Re: [netconf] updates to client/server drafts

Martin Bjorklund <mbj@tail-f.com> Thu, 13 June 2019 14:17 UTC

Return-Path: <mbj@tail-f.com>
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 093B712030D for <netconf@ietfa.amsl.com>; Thu, 13 Jun 2019 07:17:24 -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, SPF_HELO_NONE=0.001, SPF_PASS=-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 z9yyXjpD-ZqL for <netconf@ietfa.amsl.com>; Thu, 13 Jun 2019 07:17:22 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 04C7912031A for <netconf@ietf.org>; Thu, 13 Jun 2019 07:17:22 -0700 (PDT)
Received: from localhost (unknown [173.38.220.61]) by mail.tail-f.com (Postfix) with ESMTPSA id 1C9AA1AE0331; Thu, 13 Jun 2019 16:17:20 +0200 (CEST)
Date: Thu, 13 Jun 2019 16:17:24 +0200 (CEST)
Message-Id: <20190613.161724.2062830463595047263.mbj@tail-f.com>
To: j.schoenwaelder@jacobs-university.de
Cc: kent+ietf@watsen.net, netconf@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <20190613111023.ngllkl22zj2vsowp@anna.jacobs.jacobs-university.de>
References: <20190613061155.mpuudt25lmze4bzk@anna.jacobs.jacobs-university.de> <20190613.130024.515576855897220606.mbj@tail-f.com> <20190613111023.ngllkl22zj2vsowp@anna.jacobs.jacobs-university.de>
X-Mailer: Mew version 6.7 on Emacs 25.2 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/g6xpAhGkIk8T8RjYgZTM3VY_Kw4>
Subject: Re: [netconf] updates to client/server drafts
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: Thu, 13 Jun 2019 14:17:29 -0000

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> On Thu, Jun 13, 2019 at 01:00:24PM +0200, Martin Bjorklund wrote:
> > Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> > > I am strictly against hiding actions by encoding 'verbs' in an ad-hoc
> > > data format. I rather not support creation of keys on the device.
> > 
> > Remember we had this cases:
> > 
> > 1.  upload of keys
> > 2a. generation of keys on the box that will go into hardware protected
> >     storage (and never be accessible)
> > 2b. generation of keys on the box that will be stored on disk
> >     (and never be accessible over the mgmt interface)
> > 3.  generation of keys on the box that become (protected) configuration
> > 
> > 
> > I think the previous version of the draft (with YANG actions) handles
> > 1 and 2 (a and b with trivial updates).
> > 
> > It is only (3) that we don't have a solution for that everybody
> > accepts.
> > 
> > So perhaps we should solve 1 and 2a and 2b, and publish that, and
> > leave 3 for the future?
> 
> This may be a way to move forward. In 2a and 2b, will there be a way
> to remove a generated key via the mgmt interface or do I have to take
> a bigger hammer to accomplish this?

If we can agree on this way forward, I think we can solve the life
cycle issue.  One action to create the key and one to delete it seems
reasonable.


/martin