Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Unless you're dealing with shapers or policers, you wouldn't normally concern your self with millisecond burstiness.
If your multicast traffic isn't particularly time sensitive, you would only need to insure your QoS policy provides enough bandwidth to satisfy the expected load with enough queue depth to handle bursts. If your multicast traffic is time sensitive, then you need to insure you can prioritize a burst so that it is not much queued, e.g. LLQ in CBWFQ.