Discontinuity timer for TCP-MIB counters

Rajiv Raghunarayan <raraghun@cisco.com> Tue, 30 March 2004 23:04 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 SAA24034 for <ipv6-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:04:15 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B8RjZ-0006Xa-B3 for ipv6-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:25 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i16BcrZi021032 for ipv6-archive@odin.ietf.org; Fri, 6 Feb 2004 06:38:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ap4Jw-0005Qq-Lb for ipv6-web-archive@optimus.ietf.org; Fri, 06 Feb 2004 06:38:52 -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 GAA21457 for <ipv6-web-archive@ietf.org>; Fri, 6 Feb 2004 06:38:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ap4Jl-0005Ya-00 for ipv6-web-archive@ietf.org; Fri, 06 Feb 2004 06:38:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ap4It-0005VT-00 for ipv6-web-archive@ietf.org; Fri, 06 Feb 2004 06:37:48 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1Ap4Ia-0005Rz-00 for ipv6-web-archive@ietf.org; Fri, 06 Feb 2004 06:37:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ap4IB-0004LT-QH; Fri, 06 Feb 2004 06:37:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AowEA-0004ti-N7 for ipv6@optimus.ietf.org; Thu, 05 Feb 2004 22:00:22 -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 WAA25436 for <ipv6@ietf.org>; Thu, 5 Feb 2004 22:00:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AowE7-0005jp-00 for ipv6@ietf.org; Thu, 05 Feb 2004 22:00:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AowDB-0005iF-00 for ipv6@ietf.org; Thu, 05 Feb 2004 21:59:22 -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>
Subject: Discontinuity timer for TCP-MIB counters
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ipv6-admin@ietf.org
Errors-To: ipv6-admin@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Id: IP Version 6 Working Group (ipv6) <ipv6.ietf.org>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
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
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.


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------