<Internet-Drafts <at> ietf.org>
2004-01-20 20:43:30 GMT
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Border Gateway Multicast Protocol Working Group of the IETF.
Title : Border Gateway Multicast Protocol (BGMP): Protocol Specification
Author(s) : D. Thaler
Filename : draft-ietf-bgmp-spec-06.txt
Pages : 45
Date : 2004-1-20
This document describes BGMP, a protocol for inter-domain multicast
routing. BGMP builds shared trees for active multicast groups, and
optionally allows receiver domains to build source-specific, inter-
domain, distribution branches where needed. BGMP natively supports
'source-specific multicast' (SSM). To also support 'any-source
multicast' (ASM), BGMP requires that each multicast group be associated
with a single root (in BGMP it is referred to as the root domain). It
requires that different ranges of the class D space are associated
(e.g., with Unicast-Prefix-Based Multicast addressing) with different
domains. Each of these domains then becomes the root of the shared
domain-trees for all groups in its range. Multicast participants will
generally receive better multicast service if the session initiator's
address allocator selects addresses from its own domain's part of the
space, thereby causing the root domain to be local to at least one of
the session participants.
A URL for this Internet-Draft is:
To remove yourself from the IETF Announcement list, send a message to
ietf-announce-request with the word unsubscribe in the body of the message.
Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
A list of Internet-Drafts directories can be found in
Internet-Drafts can also be obtained by e-mail.
Send a message to:
mailserv <at> ietf.org.
In the body type:
NOTE: The mail server at ietf.org can return the document in
MIME-encoded form by using the "mpack" utility. To use this
feature, insert the command "ENCODING mime" before the "FILE"
command. To decode the response(s), you will need "munpack" or
a MIME-compliant mail reader. Different MIME-compliant mail readers
exhibit different behavior, especially when dealing with
"multipart" MIME messages (i.e. documents which have been split
up into multiple messages), so check your local documentation on
how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the