RE: [802.1] MSTP MIB - dot1dStpPathCostDefault & mstpGenPathCostDefault

Ali,

I am copying the Bridge MIB WG.=20

The object dot1dStpPathCostDefault was taken out of the RSTP MIB for the
last four iterations at least, while the document went through Working
Group Last Call and IESG Last Call. It was approved as a IETF Proposed
Standard, the announcement went out last night. The reason is that we
changed RFC1493bis
http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-bridge-brid
gemib-smiv2-10.txt to include both dot1dStpPortPathCost and
dot1dStpPortPathCost32.=20

If you want to make a proposal for the MSTP MIB, you should take it with
Alex Ruzin who is the editor of the MSTP MIB in the IEEE 802.1WG.=20

Regards,

Dan


=20
=20

> -----Original Message-----
> From: Ali Chanaui [mailto:[email protected]]=20
> Sent: Wednesday, August 31, 2005 12:11 PM
> To: Romascanu, Dan (Dan); [email protected]
> Subject: Re: [802.1] MSTP MIB - dot1dStpPathCostDefault &=20
> mstpGenPathCostDefault
>=20
> Dan,
> I see in draft-ietf-bridge-rstpmib-09.txt, that object=20
> dot1dStpPathCostDefault has been obsoleted, but it seems,=20
> that I missed the discussion about it, and I don't understand=20
> why this desision has been accepted.
> What do you think about mstpGenPathCostDefault in MSTP MIB?
>=20
> With great respect, Ali
>=20
>=20
>=20
> 	=09
> ____________________________________________________
> Start your day with Yahoo! - make it your home page=20
> http://www.yahoo.com/r/hs=20
> =20
>=20