FW: [802.1] MSTP MIB - mstpMapTable

["Romascanu, Dan \(Dan\)" <dromasca@avaya.com>]

This issue popped-up on the IEEE 802.1 WG list, around a OCTET STRING
object that would exceed 500 octets, and the authors decided to break it
into 'smaller pieces'. 
While watching this discussion I checked with the MIB review guidelines,
which do not say anything about a recommended size limiting of an OCTET
STRING, excepting the fact that it is recommended to be limited at some
size, especially when the OCTET STRING object is an index. See
http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review-guidelines
-04.txt Section 4.6.1.4. Is this OK? If so, how does this live together
with Keith's comment? 

Dan


 

-----Original Message-----
From: IEEE 802.1 [mailto:hdk-0119.ckxbsg@ATT.NET] On Behalf Of Keith
McCloghrie
Sent: Tuesday, September 06, 2005 3:45 PM
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