RE: [802.1] MSTP MIB - mstpMapTable

["Wijnen, Bert (Bert)" <bwijnen@lucent.com>]

I would really be surprised if there are manager side SNMP
implementations that do not at least support up to 1472.

At some agent sides, I can understand so. But in the IEEE 802.1
space, I would think everyone works with the 1500 ethernet frame
no? And so 1472 should (in practicallity) not be a problem I
would hope.

Bert

> -----Original Message-----
> From: owner-mreview@ops.ietf.org [mailto:owner-mreview@ops.ietf.org]On
> Behalf Of David B Harrington
> Sent: Tuesday, September 06, 2005 17:46
> To: 'Mreview (E-mail)'
> Subject: FW: [802.1] MSTP MIB - mstpMapTable
> 
> 
> Hi,
> 
> I sent this comment to the 802.1WG as well.
> 
> dbh
> 
> -----Original Message-----
> From: IEEE 802.1 [mailto:hdk-0119.ckxbsg@att.net] On Behalf Of David B
> Harrington
> Sent: Tuesday, September 06, 2005 10:17 AM
> To: STDS-802-1-L@listserv.ieee.org
> Subject: Re: [802.1] MSTP MIB - mstpMapTable
> 
> Hi,
> 
> Let me provide a little further interpretation.
> 
> Because support of messages greater than 484 octets is not required,
> if you define an object that requires a message larger than 484
> octets, some standards-compliant SNMP applications may not be able to
> retrieve your object, and some standards-compliant SNMP agent
> implementations may not be able to send your object.
> 
> To ensure interoperability (and interoperability is why we define
> standards), it would be wise to limit the size of this object so that
> it can fit within a 484 octet message, so all standards-compliant SNMP
> implementations would be able to work with the MIB module. 
> 
> David Harrington
> dbharrington@comcast.net
> IETF MIB Doctor
>  
> 
> > -----Original Message-----
> > From: IEEE 802.1 [mailto:hdk-0119.ckxbsg@att.net] On Behalf 
> > Of Keith McCloghrie
> > Sent: Tuesday, September 06, 2005 8:45 AM
> > To: STDS-802-1-L@listserv.ieee.org
> > Subject: Re: [802.1] MSTP MIB - mstpMapTable
> > 
> > > 1. Divide one long OCTET STRING into 4 shorter
> > >     OCTET STRING. I don't see the reason for it.
> > 
> > The reason is the difference between "must" and "recommended".
> > Specifically, all the transport mappings in RFC 3417 say the
> > equivalent of:
> > 
> >    When an SNMP entity uses this transport mapping, it must be
> capable
> >    of accepting messages up to and including 484 octets in 
> > size.  It is
> >    recommended that implementations be capable of accepting 
> > messages of
> >    up to 1472 octets in size.  Implementation of larger values is
> >    encouraged whenever possible.
> > 
> > Keith.
> > 
> > IEEE 802.1 list:
> >  When forwarding, PLEASE DELETE this footer & list-related 
> > header items.
> >  http://www.ieee802.org/1/email-pages/pwdqq705.html
> > 
> 
> IEEE 802.1 list:
>  When forwarding, PLEASE DELETE this footer & list-related header
> items.
>  http://www.ieee802.org/1/email-pages/pwdqq705.html
> 
> 
>