[evla-sw-discuss] MIB Data Port Spec revisions

[Barry Clark]

> are
> unequivocal and unambiguous in asserting that neither TCP
> nor UDP need concern themselves with fragmentation,
> and that fragmentation is handled at the IP layer.

Better ask James.  He has said that some switches do not do the right
thing with fragmented UDP messages (they request resends for the fragments,
so that it appears to work but generates excessive network trafic).  If
our switches are of this breed, I'd still say we should stick to within 
the MTU.

>     - the Antenna ID will be a STRING
>     - the Device ID will be a STRING

For MIBs, let's store these in the slot E-Prom with the IP address.  Saves
a lot of fooling around for the L30[12] devices.

>  A DDR with the alert asserted will be sent as
> soon as the alert condition is detected, and a DDR with the alert
> not asserted will be sent as soon as the alert condition is cleared.
> DDRs sent between these two transitions will 1) be sent at the
> current rate in effect for that monitor point, and 2) always
> indicate that an alert has been asserted, which implies that
> client software must always examine the DDR for asserted alerts.

Might also be nice to reissue alerts at some slow rate (~ once a minute).