I performed an OPS-DIR review of draft-ietf-softwire-mesh-mib-11 to see if I found any operations related issues This ID defines a part of the MIB to be used in monitoring managing "software mesh” setups - setups that provide for connectivity between clouds of IPv6 or IPv4 over connections of the other protocol. Since MIBs are designed to provide operational disability into network or device state it is rare that they would present any operational issues b=y themselves, particularly if the guidance to not define MIBs with writable variables is followed, as it is in this case. I did not find any operations issues with the document. But I did find what appears to be an inconsistency: section 5 says: 5. Structure of the MIB Module The softwire mesh MIB provides a method to configure and manage the softwire mesh objects through SNMP. which implies that there are writable variables (which would be needed to configure or manage) but I did not find any writable variables and the security considerations says there are none There are no management objects defined in this MIB module that have a MAX-ACCESS clause of read-write and/or read-create. So, if this MIB module is implemented correctly, then there is no risk that an intruder can alter or create any management objects of this MIB module via direct SNMP SET operations. thus section 5 seems to be incorrect Scott