Privacy considerations for IP broadcast and multicast protocol designers

Document Type Expired Internet-Draft (individual)
Last updated 2017-03-27 (latest revision 2016-09-15)
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


A number of application-layer protocols make use of IP broadcasts or multicast messages for functions such as 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 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.)