IETF Logo Mail Archive

Re: [Bridge-mib] Draft-ietf-bridge-bridgemib-smiv2 Issues Resolution

John Flick <john.flick@hp.com> Wed, 12 January 2005 00:54 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22068; Tue, 11 Jan 2005 19:54:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CoX0b-00069H-QK; Tue, 11 Jan 2005 20:09:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CoWe3-0007hY-07; Tue, 11 Jan 2005 19:45:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CoWS7-0004xk-Qc for bridge-mib@megatron.ietf.org; Tue, 11 Jan 2005 19:33:35 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20595 for <bridge-mib@ietf.org>; Tue, 11 Jan 2005 19:33:32 -0500 (EST)
Received: from atlrel6.hp.com ([156.153.255.205]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CoWg0-0005hY-IS for bridge-mib@ietf.org; Tue, 11 Jan 2005 19:47:58 -0500
Received: from rosemail.rose.hp.com (rosemail.rose.hp.com [15.43.209.160]) by atlrel6.hp.com (Postfix) with ESMTP id 6973FB47B; Tue, 11 Jan 2005 19:33:32 -0500 (EST)
Received: from [127.0.0.1] (ros54018lap.americas.hpqcorp.net [15.255.5.21]) by rosemail.rose.hp.com (Postfix) with ESMTP id 1AB1D7FFF; Tue, 11 Jan 2005 16:33:32 -0800 (PST)
Message-ID: <41E46EFC.40107@hp.com>
Date: Tue, 11 Jan 2005 16:27:40 -0800
From: John Flick <john.flick@hp.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: dbharrington@comcast.net
Subject: Re: [Bridge-mib] Draft-ietf-bridge-bridgemib-smiv2 Issues Resolution
References: <200501112118.QAA01636@ietf.org>
In-Reply-To: <200501112118.QAA01636@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit
Cc: "'Wijnen, Bert (Bert)'" <bwijnen@lucent.com>, j.schoenwaelder@iu-bremen.de, bridge-mib@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>, <mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>, <mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit

Dave,

The tcWhile timer is an internal state variable to indicate the
time remaining for the bridge to send configuration messages with
the topology change bit set.  The added text in the description of
the TimeSinceTopologyChange object just specifies from what point
in the RSTP topology change state machine the topology change
time is measured.  The "meaning" of the object is actually
unchanged.  I'm not sure how this would break an application.

John

David B Harrington wrote:
> 2) I think the topologychange object has been changed in a way that
> could break existing (non-RSTP-knowledgeable) applications that are
> run against an RSTP-supporting agent, 


_______________________________________________
Bridge-mib mailing list
Bridge-mib@ietf.org
https://www1.ietf.org/mailman/listinfo/bridge-mib

v2.23.0 | Report a Bug | By Email