Re: [pim] PIM yang model counter 64/32 bit

Stig Venaas <stig@venaas.com> Wed, 07 March 2018 17:31 UTC

Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4030612D885 for <pim@ietfa.amsl.com>; Wed, 7 Mar 2018 09:31:28 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=venaas-com.20150623.gappssmtp.com
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 eSJTlDxahava for <pim@ietfa.amsl.com>; Wed, 7 Mar 2018 09:31:26 -0800 (PST)
Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4C5A1200C1 for <pim@ietf.org>; Wed, 7 Mar 2018 09:31:26 -0800 (PST)
Received: by mail-qt0-x22b.google.com with SMTP id n9so3566207qtk.6 for <pim@ietf.org>; Wed, 07 Mar 2018 09:31:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=venaas-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=D4YZVpZhGIn9wyN1QP0WvfV4t9lD9Q2o5AR1X6Hm604=; b=fXNSIGHixZjWYk938ah9Z5+fCGehz8QB3avZBbVotNF/C05+pqPxPbG2BH7LscCP7y PEN7TVwB8opUl0vmzASk230iiL+fnmZBLpwwIW1ZKqI7ehiFkOcLruZUr5wz4qxh3rR5 XF/NikaMQ8f9dl6W38KLbbNQY9Krx1ybz3JpS5m6VDLsPFPIhXMicWb6tFL01tc0WY/J kEWuAyA7AO7D3uOslRGMdfCgR4hX6OVZkKL/FresXjdiskHfen1ANSMJw1W5q3VabHa0 ZEgZcTxM8QpX1pZN5N8SFjNl+Zh3f5wmZTChf8Bzxid2xP8svyy0YZu8UOlgKzQEyRN6 iBng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=D4YZVpZhGIn9wyN1QP0WvfV4t9lD9Q2o5AR1X6Hm604=; b=le7v1QhYM0ThyMcPYj4UsPounf3gAupGIcDbCYc1FushX6LTyMmo/8TtZDW5OrCLFm REyxnr9iUyyG3SpvInMUUuOaDLqQ4Qt3vnhvuLO+xmvBoKE3Xf0cfoH2ntjTd0BNI5Ae 1mwlsLURTdyapfTmTDfkwTKA2bX5g64A9JQmlMW+E1VgTEjsPcJAok1uLdnMe0/JQtUd cdlJBuX7xy1gd2ExgIr+jI2CUuxxjyS48qKuKVwt39Eu9LaOjbYevpqenqQUz5CA5vK2 j1y65BUwsTqVo5EHI9XRTUAtDZaoU6nIl7vBuZQ0UDVZPvuqtXAH+jz5lwXZzv9pjEhG wuSw==
X-Gm-Message-State: AElRT7Ga56WrDDC9BIxiDMZeAkIfBUf+kOOamT9/NiL/AgWLTfbRoOAk WLl5jpHUVCdpapQ3pNnZkeYLyMUCHTire1naSijVSA==
X-Google-Smtp-Source: AG47ELvcIdHqGdraw7k+1zeOhVVshCBEut9x+WC6r+6EW0ubnJVQOzhOEeEaA77w9yWvJy1a/m49CvFkqhTBOtGhntg=
X-Received: by 10.237.60.58 with SMTP id t55mr36464363qte.228.1520443885625; Wed, 07 Mar 2018 09:31:25 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.94.235 with HTTP; Wed, 7 Mar 2018 09:31:24 -0800 (PST)
In-Reply-To: <CAA6qS9oJe7tmmx0__=Lkq7=MnxQ+eeUxpR09ZW8u8MAHmrgXkQ@mail.gmail.com>
References: <CAA6qS9oJe7tmmx0__=Lkq7=MnxQ+eeUxpR09ZW8u8MAHmrgXkQ@mail.gmail.com>
From: Stig Venaas <stig@venaas.com>
Date: Wed, 07 Mar 2018 09:31:24 -0800
Message-ID: <CAHANBtLPw66x2us1dCmi3kpGTo5UOvMVPi3wtDoGOd3xPc4P7Q@mail.gmail.com>
To: Anish Peter <anish.ietf@gmail.com>
Cc: pim@ietf.org, Xufeng Liu <xufeng.liu.ietf@gmail.com>, Anish Peter <anpeter@infinera.com>, "Mahesh Sivakumar (masivaku)" <masivaku@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/ti58tMl9ppt7r19DxN8tTAn8n4w>
Subject: Re: [pim] PIM yang model counter 64/32 bit
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2018 17:31:28 -0000

Hi

To me it seems like a great idea to make the counters 64 bit. I expect
there will be pim implementations using 64 bit counters, and I don't
think backwards compatibility with 32 bit implementations is an issue
since the counters are read-only. If you do this for this draft,
please make a similar change in the other multicast YANG models
(igmp/mld/msdp/snooping).

Stig


On Wed, Mar 7, 2018 at 8:27 AM, Anish Peter <anish.ietf@gmail.com> wrote:
> Hello PIM group,
>  We are doing pim yang model and came across this question of whether to use
> a 64/32 bit counter for packet statistics. To the best of our knowledge all
> the vendor models support 32bit counters.
>  But given that we are having more scalable implementations, we had a
> feeling that a 32bit counter may rollover too fast. To give some examples.
>
> Right now now we have routers with more than 10K pim interfaces supported.
> In such case even if we consider them to be p2p always, then it would mean
> 10K pim nbrs. In this case even if an aggressive hello timer of 10 seconds
> is configured then it would transmit and receive about 60K pim hellos per
> minute. This leads to about 86.4million hello per day. This way a 32bit
> counter could roll over in less than 50 days. Half a decade back I had
> tested pim for 4K interfaces with 1s hello interval. With this the same
> counter may roll over in about 12 days time.
>
> Similarly a pim null register and register stop too for a scale of 15K group
> could easily roll over in less than 198 days.
>
>
> The vendor counters are 32 for historic reasons and may not directly get
> impacted by a stats model supporting 64bit.
>
>  Please share your opinion.
>
> Thanks,
> pim yang model authors
>
>