Re: coex draft last call -- review of changes since RFC 2576

>                                       I understand the desire
> to clarify the meaning of "the SNMPv2 variable-bindings".  The
> same clarification should be applied to 3.1(4) and 3.2(6).

  I don't think there's any problem of clarity in 3.1(4).
The SNMPv1 variable-bindings (which are pretty obvious) are used as
the SNMPv2 variable-bindings (possibly with some stuff added).
That's straightforward enough.

  As far as 3.2(6) is concerned, I'm not that bothered about the exact
terminology.  What's important to me is that it is made crystal clear
that the SNMPv1 variable-bindings should *not* include the sysUpTime.0
and snmpTrapOID.0 bindings.   How this is phrased is irrelevant.


> "the SNMPv2 variable-bindings (excluding sysUpTime.0 and snmpTrapOID.0)" ?

would be fine by me - though I'd probably suggest

"the SNMPv2 variable-bindings (i.e. excluding sysUpTime.0 and snmpTrapOID.0)"

which acknowledges that these two varbinds are not strictly part of
"the SNMPv2 variable-bindings".   That would keep the terminology
consistent, avoid having to change 3.1(4), while still serving to keep
the unwary implementer on the right road.

Dave