RE: Draft-ietf-bridge-bridgemib-smiv2 Issues Resolution
"Romascanu, Dan \(Dan\)" <[email protected]> Wed, 12 Jan 2005 02:56:20 +0200
| Newsgroups | gmane.ietf.bridge |
|---|---|
| Message-ID | <AAB4B3D3CF0F454F98272CBE187FDE2F038A9FEB@is0004avexu1.global.avaya.com> |
>From the experts floor at the IEEE 802.1 interim meeting where I happen to be right now - the maximum number of ports on a 802.1D bridge is 4k-1. Thus the 512 bytes size limit is justified. Regards, Dan > -----Original Message----- > From: [email protected] > [mailto:[email protected]]On Behalf Of Juergen Schoenwaelder > Sent: 12 January, 2005 12:33 AM > To: David B Harrington > Cc: 'Wijnen, Bert (Bert)'; [email protected] > Subject: Re: [Bridge-mib] Draft-ietf-bridge-bridgemib-smiv2 > Issues Resolution > > > On Tue, Jan 11, 2005 at 04:17:28PM -0500, David B Harrington wrote: > > > 3) the range has been constrained in the revision. This is probably > > not a problem, but it is a semantic change. > > Does someone recall where the introduced size limit for > ...AllowedToGoTo > object comes from? The port index is restricted to 65535 and > from that > perspective the upper boundary would be 8K and not 512 bytes (which > is equivalent to a maximum of 4096 ports). Can some IEEE 802.1 expert > please explain this? > > /js > > -- > Juergen Schoenwaelder International University Bremen > <http://www.eecs.iu-bremen.de/> P.O. Box 750 561, > 28725 Bremen, Germany > > _______________________________________________ > Bridge-mib mailing list > [email protected] > https://www1.ietf.org/mailman/listinfo/bridge-mib >