[CAP] technical data on CAP protocol
Linh H. Le
lhl02 at health.state.ny.us
Tue Nov 1 11:52:58 PST 2005
from network standpoint the problem you experienced shouldn't have anything
to do in particular with CAP since it's not a networking protocol. You
should look into the software package specs to see how the CAP is being
used and also check the size of the message. Maybe the message sender got
into an indefinite loop and keep sending out large messages, which chewed
up the network bandwidth
cheer
"John Minier"
<John.Minier at cent
ramedia.com> To
Sent by: <cap-list at lists.incident.com>
cap-list-bounces@ cc
lists.incident.co
m Subject
[CAP] technical data on CAP
protocol
11/01/2005 01:59
PM
I am a network technician in charge of monitoring traffic on our Wide
Area Network. Our monitoring software has reported a CAP protocol
consuming 29+ Megabits of bandwidth at various intervals. Due to
limitations in the software package, we are unable to verify that the
common alerting protocol is the source.
Does anyone know the mechanics of the process and how it relates to a
network from a communications protocol/bandwidth standpoint?
Thanks
_______________________________________________
This list is for public discussion of the Common Alerting Protocol. This
list is NOT part of the formal record of the OASIS Emergency Management TC.
Comments for the OASIS record should be posted using the form at
http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=emergency
CAP-list mailing list
CAP-list at lists.incident.com
http://eastpac.incident.com/mailman/listinfo/cap-list
This list is not for announcements, advertising or advocacy of any
particular program or product other than the CAP itself.
More information about the CAP-list
mailing list