IETF Logo Mail Archive

Re: [Netconf] netconf call home connection type

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Fri, 24 August 2018 22:13 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 112F41274D0 for <netconf@ietfa.amsl.com>; Fri, 24 Aug 2018 15:13:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 GUZr4_vP_aj4 for <netconf@ietfa.amsl.com>; Fri, 24 Aug 2018 15:13:28 -0700 (PDT)
Received: from anna.localdomain (anna.eecs.jacobs-university.de [IPv6:2001:638:709:5::7]) by ietfa.amsl.com (Postfix) with ESMTP id 15A5012785F for <netconf@ietf.org>; Fri, 24 Aug 2018 15:13:27 -0700 (PDT)
Received: by anna.localdomain (Postfix, from userid 501) id 8F5CB2449543; Sat, 25 Aug 2018 00:13:24 +0200 (CEST)
Date: Sat, 25 Aug 2018 00:13:23 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Kent Watsen <kwatsen@juniper.net>
Cc: Martin Bjorklund <mbj@tail-f.com>, "netconf@ietf.org" <netconf@ietf.org>
Message-ID: <20180824221323.a3utpvsocz67ebin@anna.jacobs.jacobs-university.de>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Kent Watsen <kwatsen@juniper.net>, Martin Bjorklund <mbj@tail-f.com>, "netconf@ietf.org" <netconf@ietf.org>
References: <4EAB4AE6-9957-46C5-A811-D0187C605AF2@juniper.net> <20180822.104517.297330493199273368.mbj@tail-f.com> <20180822090253.zuutkbsoht3nnt2z@anna.jacobs.jacobs-university.de> <20180822.110708.634004471297704581.mbj@tail-f.com> <27A72A17-54BB-430D-A986-A229473B5561@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <27A72A17-54BB-430D-A986-A229473B5561@juniper.net>
User-Agent: NeoMutt/20180716
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/SCeIYhlHi_nabLnIhdjWwFqkQAI>
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: Fri, 24 Aug 2018 22:13:30 -0000

On Fri, Aug 24, 2018 at 09:52:59PM +0000, Kent Watsen wrote:
> 
> >> Is it not much easier to use a random offset instead to
> >> avoid synchronization?  In LMAP, we used a random-spread in seconds,
> >> which defines the size of the time interval from which random values
> >> are taken. This has the nice benefit that the config can be the same
> >> for a large number of devices and you still get a distribution over a
> >> time interval.
> >> 
> >> Perhaps you want an anchor-time, a period, and a random offset:
> >> 
> >> anchor-time:  2018-08-22T00:00:00+00
> >> period:       600 seconds (and yes timeticks seems overkill)
> >> random-spread: 60 seconds
> >> 
> >> So you get events at 00:00:00+rs, 00:10:00+rs, 00:20:00+rs etc. and
> >> with 1200 devices you get on average 20 requests per second and all
> >> 1200 devices have exactly the same config.
> >
> > This looks very nice!
> 
> Good for YP too, right?
>

Yes.

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

v2.23.0 | Report a Bug | By Email