Re: [Netconf] configuration models status and timeline

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Wed, 18 July 2018 16:42 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
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 67E89130FEC for <netconf@ietfa.amsl.com>; Wed, 18 Jul 2018 09:42:37 -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, 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 rfMG-3QwI2V3 for <netconf@ietfa.amsl.com>; Wed, 18 Jul 2018 09:42:35 -0700 (PDT)
Received: from anna.localdomain (firewallix.jacobs-university.de [212.201.44.247]) by ietfa.amsl.com (Postfix) with ESMTP id 13A1E130F18 for <netconf@ietf.org>; Wed, 18 Jul 2018 09:42:35 -0700 (PDT)
Received: by anna.localdomain (Postfix, from userid 501) id 609BC235AB7A; Wed, 18 Jul 2018 18:42:32 +0200 (CEST)
Date: Wed, 18 Jul 2018 18:42:32 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Kent Watsen <kwatsen@juniper.net>
Cc: "netconf@ietf.org" <netconf@ietf.org>
Message-ID: <20180718164232.hrcxdbkm3sr33rxr@anna.jacobs.jacobs-university.de>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Kent Watsen <kwatsen@juniper.net>, "netconf@ietf.org" <netconf@ietf.org>
References: <20180718112108.hqgetzfebhqpdpsk@anna.jacobs.jacobs-university.de> <AD20F795-CBD3-4054-BD09-4F7DD45CFACB@juniper.net> <20180718150228.e2vcccd34sivmz3h@anna.jacobs.jacobs-university.de> <964B3A4A-E465-43CA-8460-1C07D8B46C8B@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <964B3A4A-E465-43CA-8460-1C07D8B46C8B@juniper.net>
User-Agent: NeoMutt/20180622
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/gvJ7XEp0SEdDmYw-9ndyAu1D5WQ>
Subject: Re: [Netconf] configuration models status and timeline
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, 18 Jul 2018 16:42:38 -0000

On Wed, Jul 18, 2018 at 03:57:11PM +0000, Kent Watsen wrote:
> 
> I do not recommend holding off publishing these documents for this.
> The folks asking for this said that, if IETF doesn't put something
> into the standard model, they would augment in what they need. 
> That said, I do think that we should perhaps switch to using an 
> enumeration or an identity so that such extensions can be mixed in
> easily in the future.  The only counterpoint might be that such 
> would disable the ability to do aliveness checks at multiple 
> protocol layers simultaneously, though I don't know if that would
> ever be desired or even, perhaps, not recommended.
>

Since liveness at layer N likely implies liveness at layers < N, one
think liveness test is good enough. One thing you may watch out for
are keep-alive parameters. I would not be surprised if the amount of
control an application has over the parameters varies widely. (But
perhaps that is then a matter of deviations.)

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>