RFC 5059: Bootstrap Router (BSR) Mechanism for Protocol Independent Multicast (PIM)
In plain English — editorial summary, not part of the RFC
This document specifies the Bootstrap Router (BSR) mechanism for the class of multicast routing protocols in the PIM (Protocol Independent Multicast) family that use the concept of a Rendezvous Point as a means for receivers to discover the sources that send to a particular multicast group. BSR is one way that a multicast router can learn the set of group-to-RP mappings required in order to function. The mechanism is dynamic, largely self-configuring, and robust to router failure. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5059
- Published
- January 2008
- Authors
- N. Bhaskar; A. Gall; J. Lingard; S. Venaas
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 42
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4610Anycast-RP Using Protocol Independent Multicast (PIM)Current
August 2006
- RFC 3618Multicast Source Discovery Protocol (MSDP)Current
October 2003
- RFC 3956Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast AddressUpdated
November 2004
- RFC 4412Communications Resource Priority for the Session Initiation Protocol (SIP)Updated
February 2006
- RFC 5060Protocol Independent Multicast MIBCurrent
January 2008
- RFC 5063Extensions to GMPLS Resource Reservation Protocol (RSVP) Graceful RestartCurrent
October 2007
- RFC 5065Autonomous System Confederations for BGPUpdated
August 2007
- RFC 5073IGP Routing Protocol Extensions for Discovery of Traffic Engineering Node CapabilitiesCurrent
December 2007
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?