Re: dot1dStpPortPathCost32

On Tue, Nov 02, 2004 at 09:50:14AM +0000, Les Bell wrote:
> 
> Use of the 32-bit path cost was defined in both 802.1w (RSTP) and 802.1t.
> 802.1t was a collection of enhacements to Bridges, including those that support
> legacy STP.  So the 32-bit path costs do not just apply to RSTP.
> 
> I think you are right that dot1dStpPortPathCost32 should be conditionally
> mandatory, but for any Spanning Tree implementation that supports 32-bit path
> costs, not just for RSTP.

OK, I have created another group and this makes the support for
dot1dStpPortPathCost32 conditionally mandatory.
 
> Implementations that support 32-bit path costs should not use the 16-bit path
> cost object, dot1dStpPortPathCost, but I am not sure what is the best way to
> deal with this.  Are we allowed to allocate a special value to indicate it is
> not in use?  I think it would be safer to return an SNMP error indicating the
> old object is not supported.

dot1dStpPortPathCost is Integer32 (1..65535). Is there a value (e.g.,
65535) which can be picked for this purpose? What do implementation do?

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany