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

Michael MacFaden <mrm@riverstonenet.com> Thu, 23 May 2002 18:16 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 OAA21453 for <bridge-archive@odin.ietf.org>; Thu, 23 May 2002 14:16:10 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id OAA09806 for bridge-archive@odin.ietf.org; Thu, 23 May 2002 14:16:30 -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 OAA09793; Thu, 23 May 2002 14:16:28 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA09762 for <bridge-mib@ns.ietf.org>; Thu, 23 May 2002 14:16:27 -0400 (EDT)
Received: from agile.yagosys.com (host60.riverstonenet.com [64.95.122.60] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA21425 for <bridge-mib@ietf.org>; Thu, 23 May 2002 14:16:05 -0400 (EDT)
Received: (qmail 1639 invoked by uid 10041); 23 May 2002 18:15:55 -0000
Date: Thu, 23 May 2002 11:15:55 -0700
From: Michael MacFaden <mrm@riverstonenet.com>
To: Arozin@Opticalaccess.com
Cc: Internet-Drafts@ietf.org, bridge-mib@ietf.org
Subject: Re: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-03.txt
Message-ID: <20020523111555.D1464@riverstonenet.com>
References: <200205231129.HAA04730@ietf.org> <003801c2026c$86d49f00$87885ac2@Alexr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <003801c2026c$86d49f00$87885ac2@Alexr>
User-Agent: Mutt/1.3.22i
X-Operating-System: GNU/Linux 2.4.18
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

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"

See RFC 2578 page 9, in SMIv2 MAX-ACCESS does not support "write-only "

Mike MacFaden


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