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

Ali Chanaui <ali_chanaui@yahoo.com> Mon, 27 May 2002 06:17 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 CAA12726 for <bridge-archive@odin.ietf.org>; Mon, 27 May 2002 02:17:50 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id CAA21378 for bridge-archive@odin.ietf.org; Mon, 27 May 2002 02:18:13 -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 CAA21365; Mon, 27 May 2002 02:18:12 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA21333 for <bridge-mib@optimus.ietf.org>; Mon, 27 May 2002 02:18:10 -0400 (EDT)
Received: from web13103.mail.yahoo.com (web13103.mail.yahoo.com [216.136.174.148]) by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA12720 for <bridge-mib@ietf.org>; Mon, 27 May 2002 02:17:47 -0400 (EDT)
Message-ID: <20020527061808.85590.qmail@web13103.mail.yahoo.com>
Received: from [194.90.136.135] by web13103.mail.yahoo.com via HTTP; Sun, 26 May 2002 23:18:08 PDT
Date: Sun, 26 May 2002 23:18:08 -0700 (PDT)
From: Ali Chanaui <ali_chanaui@yahoo.com>
Subject: Re: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-03.txt
To: Michael MacFaden <mrm@riverstonenet.com>, bridge-mib@ietf.org
Cc: stds-802-1@ieee.org
In-Reply-To: <20020526221520.C2410@riverstonenet.com>
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

I have another question (it seems to me,
it dedicated rather to stds-802-1@ieee.org).

If Port has been done forceDisable(2) or
disabled(2) - does this Port take place in Active
Topology?
I mean: does it forward frames, leran addresses?
Does it participate in GVRP, etc.?

Ali


--- Michael MacFaden <mrm@riverstonenet.com> wrote:
> On Sun, May 26, 2002 at 09:20:20AM +0200, Alex Ruzin
> wrote:
> >Actually I only meant to make the definition for
> this
> >object *semantically* better. Are you agree with my
> proposition
> >"in general", except "MAX-ACCESS"? Do you think,
> that definition
> >of this object has to be improved?
> >If so, I propose
> >
> >    dot1dStpPortEnable OBJECT-TYPE
> >        SYNTAX      INTEGER {
> >                        dummyReadValue(0),
> >                        forceBlock(1),
> >                        forceDisable(2)
> >                   }
> >        MAX-ACCESS  read-write
> >        STATUS      current
> >        DESCRIPTION
> >            "'Force Port State' of the port. Both
> GET and GETNEXT operation
> >              always return value
> dummyReadValue(0). An attempt to write the value
> >             dummyReadValue(0) must cause an
> error."
> >        REFERENCE
> >            "IEEE 802.1D-1998: Section 14.8.2.2"
> >        ::= { dot1dStpPortEntry 4 }
> >
> >Your comments and/or proposition, please?
> 
> The operation of this object is clear but such a
> redefinition
> would not be allowed by IESG mib doctors as it is
> not backward compatible. 
> 
> If this definition were for a new object, then I
> don't see why there is
> a need for a dummyReadValue other than to create a
> write-only style access.
> The SMIv2 dropped write-only access for a purpose
> and as such most MIB 
> doctors would discourage its use.
> 
> I think dot1dStpPortEnable should be left as-is but
> the front matter
> should explain how this object was supposed to
> operate since it 
> is clear that many vendors did not implement it
> according to 
> the original authors intentions.
> 
> Mike MacFaden
> 
> _______________________________________________
> Bridge-mib mailing list
> Bridge-mib@ietf.org
> https://www1.ietf.org/mailman/listinfo/bridge-mib


__________________________________________________
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