http://search.ietf.org/

The Border Gateway Multicast Protocol
(BGMP) maintains a group-prefix state in response to messages
from BGMP peers and notifications from M-IGP components. Group-shared
trees are rooted at the domain advertising the group prefixes
covering those groups. When a receiver joins a specific group
address, the border router towards the root domain generates
a group-specific Join message, which is then forwarded Border-Router-by-Border-Router
towards the root domain. BGMP Join and Prune messages are sent
over TCP connections between BGMP peers, and the BGMP protocol
state is refreshed by KEEP ALIVE messages periodically sent
over TCP.
BGMP routers build group-specific bidirectional forwarding state
as they process the BGMP Join messages. Bidirectional forwarding
state means that packets received from any target are forwarded
to all other targets in the target list without any RPF checks.
No group-specific state or traffic exists in parts of the network
where there are no members of that group.

Protocol Header Structure

 
0
 
1
 
2
 
3
 
 
0
1
2
3
4
5
6
7
8
9
0
1
2
3
4
5
6
7
8
9
0
1
2
3
4
5
6
7
8
9
0
1
0
Length
Type
Reserved

The description of
the protocol header is as follows:

Length
The total length of the message including the header in octets.

Type
The type code of the message. The following type codes are available:

1 OPEN
2 UPDATE
3 NOTIFICATION
4 KEEPALIVE

Popularity: -0% [?]