RFC 8386: Privacy Considerations for Protocols Relying on IP Broadcast or Multicast
In plain English — editorial summary, not part of the RFC
A number of application-layer protocols make use of IP broadcast 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 broadcast or multicast messages, a passive observer in the same broadcast or multicast domain can trivially record these messages and analyze their content. Therefore, designers of protocols that make use of broadcast or multicast messages need to take special care when designing their protocols.
Document record
- Document ID
- RFC8386
- Published
- May 2018
- Authors
- R. Winter; M. Faath; F. Weisshaar
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8638IPv4 Multicast over an IPv6 Multicast in Softwire Mesh NetworksCurrent
September 2019
- RFC 8114Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast NetworkCurrent
March 2017
- RFC 7411Multicast Listener Extensions for Mobile IPv6 (MIPv6) and Proxy Mobile IPv6 (PMIPv6) Fast HandoversCurrent
November 2014
- RFC 7161Proxy Mobile IPv6 (PMIPv6) Multicast Handover Optimization by the Subscription Information Acquisition through the LMA (SIAL)Current
March 2014
- RFC 5851Framework and Requirements for an Access Node Control Mechanism in Broadband Multi-Service NetworksCurrent
May 2010
- RFC 4291IP Version 6 Addressing ArchitectureUpdated
February 2006
- RFC 3513Internet Protocol Version 6 (IPv6) Addressing ArchitectureObsoleted
April 2003
- RFC 3306Unicast-Prefix-based IPv6 Multicast AddressesUpdated
September 2002
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?