IETF Logo Mail Archive

Re: [Netconf] netconf call home connection type

Martin Bjorklund <mbj@tail-f.com> Wed, 22 August 2018 08:59 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 6E288130EEF for <netconf@ietfa.amsl.com>; Wed, 22 Aug 2018 01:59:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 Oyj65QXA8uAb for <netconf@ietfa.amsl.com>; Wed, 22 Aug 2018 01:59:00 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 09D2B130ECD for <netconf@ietf.org>; Wed, 22 Aug 2018 01:59:00 -0700 (PDT)
Received: from localhost (h-80-27.A165.priv.bahnhof.se [212.85.80.27]) by mail.tail-f.com (Postfix) with ESMTPSA id 0A4461AE0388; Wed, 22 Aug 2018 10:58:59 +0200 (CEST)
Date: Wed, 22 Aug 2018 10:58:58 +0200
Message-Id: <20180822.105858.356632119713936966.mbj@tail-f.com>
To: kwatsen@juniper.net
Cc: netconf@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <95225F7A-6972-4A55-A5A2-0D287050A26D@juniper.net>
References: <20180821.141923.1666876004159297021.mbj@tail-f.com> <4EAB4AE6-9957-46C5-A811-D0187C605AF2@juniper.net> <95225F7A-6972-4A55-A5A2-0D287050A26D@juniper.net>
X-Mailer: Mew version 6.7 on Emacs 24.5 / 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/rQWcX5V4vS_a4X_CkntEvaOtdwU>
Subject: Re: [Netconf] netconf call home connection type
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Network Configuration WG mailing 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, 22 Aug 2018 08:59:02 -0000

Kent Watsen <kwatsen@juniper.net> wrote:
> 
> 
> 
> >> I also suggest that the default connection strategy either is 
> >> dropped, or changed to "on-demand".
> >
> > This was discussed at the IETF 102 meeting (see attached slide and
> > lines 329-335 in the minutes).  Essentially, folks want to add a
> > "periodic" feature enabling the initiating peer to optionally
> > support periodic connections.  As such, I don't think it should
> > be the default.
> 
> Adding onto this, we could drop the default, and make the parent
> "choice" be mandatory true.
> 
> Actually, since we're adding a feature for "periodic", we might
> want to also add a feature for "persistent".  This would be
> similar to how we're having features for both keystore-supported
> and local-keys-supported.  Thoughts?

I don't think that we need features for these mechanisms.  Both should
be quite trivial to implement.



/martin

v2.23.0 | Report a Bug | By Email