RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-03.txt

Ali Chanaui <ali_chanaui@yahoo.com> Sun, 26 May 2002 06:42 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17011 for <bridge-archive@odin.ietf.org>; Sun, 26 May 2002 02:42:46 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id CAA24990 for bridge-archive@odin.ietf.org; Sun, 26 May 2002 02:43:07 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA24983; Sun, 26 May 2002 02:43:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA24946 for <bridge-mib@optimus.ietf.org>; Sun, 26 May 2002 02:43:04 -0400 (EDT)
Received: from web13108.mail.yahoo.com (web13108.mail.yahoo.com [216.136.174.153]) by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA17004 for <bridge-mib@ietf.org>; Sun, 26 May 2002 02:42:43 -0400 (EDT)
Message-ID: <20020526064304.86416.qmail@web13108.mail.yahoo.com>
Received: from [194.90.136.135] by web13108.mail.yahoo.com via HTTP; Sat, 25 May 2002 23:43:04 PDT
Date: Sat, 25 May 2002 23:43:04 -0700 (PDT)
From: Ali Chanaui <ali_chanaui@yahoo.com>
Subject: RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-03.txt
To: alexr@nbase.co.il
Cc: bridge-mib@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: bridge-mib-admin@ietf.org
Errors-To: bridge-mib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <bridge-mib.ietf.org>
X-BeenThere: bridge-mib@ietf.org

Alex,
Why we cannot make the object dot1dStpPortState
read-write
for this purpose?
Ali

On Thu, May 23, 2002 at 05:14:24PM +0200, Alex Ruzin
wrote:
> It seems to me, that the object dot1dStpPortEnable
> doesn't reflect a *port
> state* as it is defined
> in "IEEE 802.1D-1998: Section 8.5.5.2"; rather it
> correspondents to "Force port state" from Section
14.8.2.2.
> I propose to discuss an option to:
> 1) do this object "MAX-ACCESS  write-only"
> 2) set possible values as
>        SYNTAX      INTEGER {
>                        forceBlock(1),
>                        forceDisable(2)
>                    }
> 3) change REFERENCE: "IEEE 802.1D-1998: Section
14.8.2.2"



__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

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