Re: [pim] PIM yang model counter 64/32 bit
<N.Leymann@telekom.de> Thu, 08 March 2018 09:55 UTC
Return-Path: <prvs=598f02c95=N.Leymann@telekom.de>
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 DFED912426E for <pim@ietfa.amsl.com>; Thu, 8 Mar 2018 01:55:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.329
X-Spam-Level:
X-Spam-Status: No, score=-4.329 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de header.b=gi/58EW1; dkim=pass (1024-bit key) header.d=telekom.onmicrosoft.de header.b=QqhzY+EA
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 EQhJ5ensrvEp for <pim@ietfa.amsl.com>; Thu, 8 Mar 2018 01:55:09 -0800 (PST)
Received: from mailout23.telekom.de (MAILOUT23.telekom.de [80.149.113.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13FC11205F0 for <pim@ietf.org>; Thu, 8 Mar 2018 01:55:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1520502909; x=1552038909; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=a9Oh5TTK9LxeSNE1dhhcWfm7YIuocvqA1PUvWfOijwI=; b=gi/58EW1JSDCn39P1BKp6Ngi1G7hjySph8C84daZbR25UOcUpO0oSxLJ oLSXpqJIumijH0Htk75ZZPaanvS74vJvfwLVaBOhJIvSbWzRAkB+bv74F Z22BbsUxIW772OtZp+NDfoPUCdtYlv5Zp+LG1EKtoyEZO1xnhR4Xsq9ZV Lx4nyhaI1ztm7jGJWoGXhTZv4T1RHMVsQSkhEdiRREf5JqCQgK5xSXbL9 5+zko4viED1gzb55hwPM/bmWIOcl4oKyKqgLfiLKI2PGOA/BQBty0LrSU SWHVKloCdy30A1hqlCEu1GYwcToATD9t4KcWycZ5G1RV4QnM5Byc5Q+UP g==;
Received: from qde8e4.de.t-internal.com ([10.171.255.33]) by MAILOUT21.telekom.de with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Mar 2018 10:55:06 +0100
X-IronPort-AV: E=Sophos;i="5.47,440,1515452400"; d="scan'208,217";a="188088668"
Received: from he101953.emea1.cds.t-internal.com ([10.169.118.78]) by QDE8PP.de.t-internal.com with ESMTP/TLS/AES256-SHA; 08 Mar 2018 10:55:06 +0100
Received: from HE105870.EMEA1.cds.t-internal.com (10.169.118.67) by HE101953.emea1.cds.t-internal.com (10.169.118.78) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Thu, 8 Mar 2018 10:55:05 +0100
Received: from HE106564.emea1.cds.t-internal.com (10.171.40.16) by HE105870.EMEA1.cds.t-internal.com (10.169.118.67) with Microsoft SMTP Server (TLS) id 15.0.1365.1 via Frontend Transport; Thu, 8 Mar 2018 10:55:05 +0100
Received: from GER01-FRA-obe.outbound.protection.outlook.de (51.4.80.16) by O365mail01.telekom.de (172.30.0.234) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Thu, 8 Mar 2018 10:54:33 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.onmicrosoft.de; s=selector1-telekom-onmicrosoft-de; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=a9Oh5TTK9LxeSNE1dhhcWfm7YIuocvqA1PUvWfOijwI=; b=QqhzY+EARqBiy0VdnfDupjzcGHJ0jfzpeVbF9iTNF2DxX/IAENLsJQi9h96UPX+L958IACbhCo0XBWmekf/EfIre7o4n55PNUbUZK53/wMlEN254MVl1HTWcx9P5/Q+Q4m9lQJIXg7a0XuEklWhQudy+dH/YBLWcY2lnuibb8ag=
Received: from FRXPR01MB0407.DEUPRD01.PROD.OUTLOOK.DE (10.158.152.138) by FRXPR01MB0405.DEUPRD01.PROD.OUTLOOK.DE (10.158.152.136) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.567.14; Thu, 8 Mar 2018 09:55:04 +0000
Received: from FRXPR01MB0407.DEUPRD01.PROD.OUTLOOK.DE ([fe80::e842:28dd:b7ea:642a]) by FRXPR01MB0407.DEUPRD01.PROD.OUTLOOK.DE ([fe80::e842:28dd:b7ea:642a%14]) with mapi id 15.20.0548.016; Thu, 8 Mar 2018 09:55:04 +0000
From: N.Leymann@telekom.de
To: anish.ietf@gmail.com, pim@ietf.org
CC: anpeter@infinera.com
Thread-Topic: [pim] PIM yang model counter 64/32 bit
Thread-Index: AQHTtjEzG5cxqAUXM0W0jH0Es46aF6PGGlEA
Date: Thu, 08 Mar 2018 09:55:04 +0000
Message-ID: <FRXPR01MB04071427E7FFA9E270F8FFA798DF0@FRXPR01MB0407.DEUPRD01.PROD.OUTLOOK.DE>
References: <CAA6qS9oJe7tmmx0__=Lkq7=MnxQ+eeUxpR09ZW8u8MAHmrgXkQ@mail.gmail.com>
In-Reply-To: <CAA6qS9oJe7tmmx0__=Lkq7=MnxQ+eeUxpR09ZW8u8MAHmrgXkQ@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=N.Leymann@telekom.de;
x-originating-ip: [164.19.3.180]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; FRXPR01MB0405; 6:WRtQTv3XAkexdusPCjPhuOBQuoJf81lfewiW7Sgbld2IXlzMsYEvStUGxENQiSi+Gfa9dhIPKAgFPxCRmVSwQawgQiIUGE/e5na4npE86LtC6yZl+MdbxU5EWaIiIjoFAIRfza31HlxWqWZIJGXNzKErAs8aSd22AdyrJ9S+pfghK28XP5oZMVbpeko/TSf2l7aJHFJTMzLiNEofMr2PiDEOcH+iu22NCxy5Byxni9dDmAKsIkNcPVkr3XXsocJWn977Je3WsmxyeLC5so8+qoqEAuq7h42T8MpCfehVqBpIzdxxggQyRfL9ph2En7Gz0GZw40dAi3MyVPS+cLHEdOLDvTyTKZyT/2SQjM9BDA/aiGppwCG0O5cdrGGN7umK; 5:hzG85eDT+3FsM4cZWxsYnKZt91u7z+1L/4Hk+olfX1oAISVbh/tFjfudthGAEeS4yDe6A3cTLF/7bgCJkiZkNCe9q7aklREVpeQmsz9mhfxW1vA0mA/SirsW3LHMD0ec31ig2vWLgCTeExPZONF5eeaLhSc5H9WfN3/by05KnPA=; 24:obMyub4Zf60E/MB8vyqrPQEmdg5dso8mZc7JWHokHIIkXHUbpGlunRtZIm8VXBjHB4/3bCsN1GWKcp8L7CW/ktpY26vG7tn1IEjqUKfGqNg=; 7:OjILHPz/zdRjlqy+5Rjq3fYAK82KdKyTBhuYEoMS+be3KZ+KyefoS0Wr/PX83AVJk/NwlDECh5l2WRNYYeW6i+acR0VscIiXw00v/jVhiNaiGHuD17M9Hr4soZKtsDJ6TgKM9kz1qn0wKsAL1O5ZYnmT5XxwpC/1siOF3Bd53ZYEk6CPisH/moIvS+fRsXboKY5Zy/JAQc7skypeg3C8/LG6MYSeySFM3L94gcgZod+MSKNbx+goaStVnmshg4F1
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 6bb5a31a-2e39-43da-815b-08d584daaaa1
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:FRXPR01MB0405;
x-ms-traffictypediagnostic: FRXPR01MB0405:
x-microsoft-antispam-prvs: <FRXPR01MB0405D4D998FA300CD222263A98DF0@FRXPR01MB0405.DEUPRD01.PROD.OUTLOOK.DE>
x-exchange-antispam-report-test: UriScan:(28532068793085)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(8121501046)(5005006)(3231220)(944501244)(52105095)(3002001)(10201501046)(93006095)(93001095)(6041288)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123558120)(20161123562045)(6072148)(201708071742011); SRVR:FRXPR01MB0405; BCL:0; PCL:0; RULEID:; SRVR:FRXPR01MB0405;
x-forefront-prvs: 060503E79B
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(366004)(39380400002)(396003)(39860400002)(346002)(189003)(199004)(8676002)(81156014)(81166006)(8936002)(102836004)(97736004)(5660300001)(2950100002)(39060400002)(3660700001)(86362001)(76176011)(2906002)(59450400001)(478600001)(316002)(186003)(3280700002)(7696005)(110136005)(52396003)(26005)(14454004)(72206003)(68736007)(5250100002)(53936002)(3846002)(6116002)(790700001)(2501003)(2900100001)(55016002)(75402003)(9686003)(54896002)(6306002)(7736002)(74482002)(4326008)(105586002)(33656002)(106356001)(66066001)(76454003)(19627235001); DIR:OUT; SFP:1101; SCL:1; SRVR:FRXPR01MB0405; H:FRXPR01MB0407.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts)
x-microsoft-antispam-message-info: e32/lahCoDpjNQRaoq0sHK0oWVAwFNjp76AsjC1G0vMoqzdZszIrZLrmR1IlhAsKphzX8YI2gEIOQfrtsPRGbgsVsNSkX6E56Y8Z/bS8WkBmfC0vTwvt+IQQrVP6wIHP5EQLCi4XubioyKQnI4RAIGYhVYVc1BF3cyLfFbZA+Z2Z0ttYcWf+jyg3fxLMlr9Tel29pcnHAIA3yNRgq6R/aFr5c9756j8LddsWDDR008b1hIJzgLb4lMtCCB5PI3+hFLhh6bdnDXUvn1zQlpYxIhGbWwpQ9EH1RF/sRA/+jav7OGKQP1ek5TSYKiJeOp/VXBtLG+eBJ5SVxzALj4fcfw==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_FRXPR01MB04071427E7FFA9E270F8FFA798DF0FRXPR01MB0407DEUP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 6bb5a31a-2e39-43da-815b-08d584daaaa1
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Mar 2018 09:55:04.2772 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: FRXPR01MB0405
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/Pifg3ABQVgvsFWLTIsI9yLR6RXA>
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: Thu, 08 Mar 2018 09:55:13 -0000
Hi, I think it’s a good idea to move to 64 bit counters. Depending on the size (and configuration of certain timers) you might exceed a 32 bit counter quite fast. regards Nic Von: pim [mailto:pim-bounces@ietf.org] Im Auftrag von Anish Peter Gesendet: Mittwoch, 7. März 2018 17:27 An: pim@ietf.org Cc: anpeter@infinera.com Betreff: [pim] PIM yang model counter 64/32 bit 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
- [pim] PIM yang model counter 64/32 bit Anish Peter
- Re: [pim] PIM yang model counter 64/32 bit Stig Venaas
- Re: [pim] PIM yang model counter 64/32 bit N.Leymann