Skip to main content

Privacy considerations for IP broadcast and multicast protocol designers

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Rolf Winter , Michael Faath , Fabian Weisshaar
Last updated 2017-05-04 (Latest revision 2016-10-31)
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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:


A number of application-layer protocols make use of IP broadcasts or multicast messages for functions like local service discovery or name resolution. Some of these functions can only be implemented efficiently using such mechanisms. When using broadcasts or multicast messages, a passive observer in the same broadcast/ multicast domain can trivially record these messages and analyze their content. Therefore, broadcast/multicast protocol designers need to take special care when designing their protocols.


Rolf Winter
Michael Faath
Fabian Weisshaar

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