Border Gateway Multicast Protocol (bgmp) Concluded WG

Note: The data for concluded WGs is occasionally incorrect.

WG Name Border Gateway Multicast Protocol
Acronym bgmp
Area Routing Area (rtg)
State Concluded
Charter charter-ietf-bgmp-01 Approved
Dependencies Document dependency graph (SVG)
Personnel Chairs Bill Fenner 
Bradley Cain 
Jeremy Hall 
Mailing list Address bgmp@ietf.org
To subscribe http://www1.ietf.org/mailman/listinfo/bgmp/
Archive https://mailarchive.ietf.org/arch/search/?email_list=bgmp

Charter for Working Group

As IP multicast is being more widely deployed and used, the
existing multicast routing algorithms have demonstrated several
limitations which make them unsuitable for deployment globally
or among multiple provider domains. Protocols like DVMRP and
PIM Dense Mode that rely on broadcasting and pruning leave
state in parts of the network that are not on the multicast
delivery tree. Protocols like CBT and PIM Sparse Mode use a
centralized resource to learn of multicast sources. Service
providers are reluctant to maintain state for multicast groups
that have no receivers in their domain or use a centralized
resource in another domain that they cannot control.

BGMP is a scalable multicast routing protocol which addresses
these problems. Like CBT and PIM Sparse Mode, BGMP chooses a
global root for a delivery tree. However, the root is a domain,
not a single router, so if there is any path available to the
domain connectivity can be maintained. BGMP builds a bidirectional,
shared tree of domains. Similarly to the unicast EGP/IGP split,
BGMP is used as the inter-domain or external protocol, while
domains can run any multicast IGP internally (such as CBT or
PIM Sparse Mode), and can build source-specific shortest-path
distribution branches to supplant the shared tree where needed.

The BGMP working group is chartered to complete the protocol
specification and follow it through the Internet standards
track. It will also help to design a transition mechanism
from MSDP (the Multicast Source Distribution Protocol, an
interim interdomain solution that is unlikely to scale for
the long term) to Internet-wide BGMP.

Milestones

Date Milestone
1 Jul 2003 Submit final version of protocol specification Internet Draft
1 Nov 2000 Produce applicability document
1 Nov 2000 Finalize MIB
1 Jul 2000 Oversee interoperability experiments
1 Jul 2000 Guide the development of a reference implementation
1 Mar 2000 Design a transition architecture from PIM-SM/MSDP to BGMP
1 Mar 2000 Produce initial version of MIB
1 Mar 2000 Produce revised protocol specification based upon simulations and evaluations
1 Nov 1999 Evaluate forwarding rules and transient behavior under a wide range of topologies under simulation
1 Nov 1999 Evaluate interoperability with multicast IGPs in more detail and identify any relevant optimizations and/or implementation issues.
1 Nov 1999 Consider monitoring and measurement (e.g. multicast traceroute) and evaluate support for existing and/or new monitoring and measurement tools and protocols.
1 Nov 1999 Develop security portion of spec

Done milestones

Date Milestone
Done Resolve multi-access LAN forwarding mechanisms