1. Is the 'strict' SNMP terminology intentionally avoided in Section 4.2
and associated diagrams, and why? Meaning why do we say 'SNMP get
message' instead of 'SNMP GetRequest PDU', etc. ?
2. Section 5.3.1
> The MIDCOM MIB module does not require a middlebox to implement
further specific MIB modules for supported middlebox functions, such
as, for example, the NAT MIB module [RFC4008].
This should probably be 'further specific middlebox (NAT devices,
firewall) MIB modules'
3. Object midcomRuleAdminStatus
> midcomRuleAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
reserve(1),
enable(2),
notSet(3)
}
...
When retrieved, the object returns the last set value. If
no value has been set, it returns one of the two possible
values."
DEFVAL { notSet }
I do not understand what are the 'two possible values'. What happens of
a retrieval happens before the object is set for the first time?
4. Several DESCRIPTION clauses (e.g. midcomRuleAdminStatus,
midcomRuleStorageType) include SNMP-specific error messages when
describing the behavior of the object. This is OK, as the MIDCOM-MIB is
designed to be used with SNMP as MIDCOM protocol, yet I would include a
note on this subject because this is not customary within other MIB
documents which are written with a protocol-independent orientation.
5. What happens with the object midcomRuleObjectTime when
midcomRuleObjectType is permanent(4)? The DESCRIPTION clause of the type
object suggests that time is read-only. With DEFVAL 0 this means
automatic destruction of the row at the end of the transaction. Is this
the desired behavior, or did I mis-understand something?
6. I do not feel comfortable with the DESCRIPTION clause of
midcomRuleError RECOMMENDing values for this object without defining
what behavior each message is supposed to cover. This type of object is
not interoperable, and this would be made clear if it was said that
these are examples rather than RECOMMENDations.
7. Another side-effect of the midcomRuleObjectType being permanent(4) is
that the permanent rules cannot be applied to interfaces, so they can be
only global. Same about transport protocol and other read-write objects.
8 . There is no DEFVAL for midcomRuleFlowDirection
9.
> Valid values for midcomRuleTransportProtocol
other than zero are defined at:
http://www.iana.org/assignments/protocol-numbers
Does this need a new type of registry from IANA? There is nothing in the
IANA considerations about this.
10. What notification needs to be sent when midcomConfigIfEnabled is set
to false? Neither the DESCRIPTION of the object nor the one of the
notifications do provide any clue.
> -----Original Message-----
> From: The IESG [mailto:iesg-secretary@xxxxxxxx]
> Sent: Thursday, August 03, 2006 8:09 PM
> To: IETF-Announce
> Cc: midcom@xxxxxxxx
> Subject: Last Call: 'Definitions of Managed Objects for
> Middlebox Communication' to Proposed Standard (draft-ietf-midcom-mib)
>
> The IESG has received a request from the Middlebox
> Communication WG to consider the following document:
>
> - 'Definitions of Managed Objects for Middlebox Communication '
> <draft-ietf-midcom-mib-08.txt> as a Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and
> solicits final comments on this action. Please send any
> comments to the iesg@xxxxxxxx or ietf@xxxxxxxx mailing lists
> by 2006-08-17.
>
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-midcom-mib-08.txt
>
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@xxxxxxxx
> https://www1.ietf.org/mailman/listinfo/ietf-announce
>
_______________________________________________
Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf