Skip to main content

The Use of SNTP as a Multicast Heartbeat

Document Type Expired Internet-Draft (mboned WG)
Expired & archived
Authors Dr. Bernard D. Aboba , Thomas Pfenning
Last updated 1996-10-28 (Latest revision 1996-10-24)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Expired
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


This document describes how the Simple Network Time Protocol (SNTP) can be used to provide a multicast heartbeat. Given the current state of the art in multicast diagnostics, use of a heartbeat may prove a useful diagnostic tool for operators as well as for applications developers. Operators may use the heartbeat to alert themselves to losses of multicast connectivity in portions of the network. Applications developers may use the heartbeat to determine whether to enable multicast features or to default to unicast operation. While it is likely that better diagnostic methods will become available in the long term, given the current state of the art, SNTP may be usefully employed as a multicast hearbeat.


Dr. Bernard D. Aboba
Thomas Pfenning

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)