[Tsvwg] Discontinuity timer for TCP-MIB counters
Rajiv Raghunarayan <raraghun@cisco.com> Fri, 06 February 2004 03:01 UTC
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25460 for <tsvwg-archive@odin.ietf.org>; Thu, 5 Feb 2004 22:01:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AowEr-0004xC-2m for tsvwg-archive@odin.ietf.org; Thu, 05 Feb 2004 22:01:05 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i16315P6019015 for tsvwg-archive@odin.ietf.org; Thu, 5 Feb 2004 22:01:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AowEn-0004wR-En; Thu, 05 Feb 2004 22:01:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AowEB-0004tn-AE for tsvwg@optimus.ietf.org; Thu, 05 Feb 2004 22:00:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25439 for <tsvwg@ietf.org>; Thu, 5 Feb 2004 22:00:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AowE8-0005ju-00 for tsvwg@ietf.org; Thu, 05 Feb 2004 22:00:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AowDC-0005iN-00 for tsvwg@ietf.org; Thu, 05 Feb 2004 21:59:23 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AowCQ-0005ev-00; Thu, 05 Feb 2004 21:58:34 -0500
Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-3.cisco.com with ESMTP; 05 Feb 2004 19:05:14 +0000
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id i162w3hk026648; Thu, 5 Feb 2004 18:58:03 -0800 (PST)
Received: from cisco.com (dhcp-128-107-165-142.cisco.com [128.107.165.142]) by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AQA60444; Thu, 5 Feb 2004 18:58:02 -0800 (PST)
Message-ID: <402302BA.4020000@cisco.com>
Date: Thu, 05 Feb 2004 18:58:02 -0800
From: Rajiv Raghunarayan <raraghun@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IPv6MIB <ipv6mib@ibr.cs.tu-bs.de>, IPv6 <ipv6@ietf.org>, TSVWG <tsvwg@ietf.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [Tsvwg] Discontinuity timer for TCP-MIB counters
Sender: tsvwg-admin@ietf.org
Errors-To: tsvwg-admin@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Hi Folks, This point came out of the IESG review of the TCP-MIB, and possibly requires wider discussion. Hence this mail to all the aliases. The current update to TCP-MIB (draft-ietf-ipv6-rfc2012-update-05.txt) does not define any special discontinuity objects, for a case when the counters in the mib experience a discontinuity. There is an implicit assumption that this would be represented by sysUpTime (SNMPv2-MIB). The IESG review suggested that we provide a discontinuity timer for the counters in the mib - could be via sysUpTime or a new discontinuity object. But we state it either way. There are issues to going either way: 1. sysUpTime: If any Counter, that uses sysUpTime as the discontinuity indicator, experiences a discontinuity, then it must reset sysUpTime (basically means a warm (re-)start). Therefore, all *other* counters that also use sysUpTime are going to look and be treated as if they also had a discontinuity. This may have performance implications, in terms of network management stations generating additional queries for these (unaffected) counters as well. 2. Add a new object for indicate discontinuity: This would necessitate adding a new (perhaps) unnecessary object, if sysUpTime can serve the purpose. In addition, systems would have an additional overhead of maintaining this information. Hence the question to folks here is: 1. Are there any known systems that can experience a discontinuity in the TCP counters without affecting the network management portion of the system. For e.g. are there systems that can restart the TCP portion of the system without restarting the network management portion of the system (or the whole system)? 2. Does anyone see any other case in which we might need to/want to maintain a discontinuity timer in the TCP-MIB? My assumption is that there might not be any systems that need an explicit discontinuity timer (but I could be wrong). Hence, would appreciate responses. Thanks, Rajiv. _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg
- [Tsvwg] Discontinuity timer for TCP-MIB counters Rajiv Raghunarayan
- [Tsvwg] RE: [ipv6mib] Discontinuity timer for TCP… Wijnen, Bert (Bert)
- [Tsvwg] Re: [ipv6mib] Discontinuity timer for TCP… Juergen Schoenwaelder
- [Tsvwg] Re: [ipv6mib] Discontinuity timer for TCP… Rajiv Raghunarayan