[bgmp] I-D ACTION:draft-ietf-bgmp-spec-06.txt

Internet-Drafts@ietf.org Tue, 20 January 2004 20:46 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21053 for <bgmp-archive@odin.ietf.org>; Tue, 20 Jan 2004 15:46:12 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aj2kp-0008V7-RV for bgmp-archive@odin.ietf.org; Tue, 20 Jan 2004 15:45:43 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0KKjhlc032671 for bgmp-archive@odin.ietf.org; Tue, 20 Jan 2004 15:45:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aj2kp-0008Us-MF for bgmp-web-archive@optimus.ietf.org; Tue, 20 Jan 2004 15:45:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20988 for <bgmp-web-archive@ietf.org>; Tue, 20 Jan 2004 15:45:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aj2ko-0000aK-00 for bgmp-web-archive@ietf.org; Tue, 20 Jan 2004 15:45:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aj2jt-0000WD-00 for bgmp-web-archive@ietf.org; Tue, 20 Jan 2004 15:44:46 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1Aj2jV-0000Se-00 for bgmp-web-archive@ietf.org; Tue, 20 Jan 2004 15:44:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aj2jE-0007zu-NO; Tue, 20 Jan 2004 15:44:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aj2ij-0007yf-CM for bgmp@optimus.ietf.org; Tue, 20 Jan 2004 15:43:33 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20484; Tue, 20 Jan 2004 15:43:30 -0500 (EST)
Message-Id: <200401202043.PAA20484@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: bgmp@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 20 Jan 2004 15:43:30 -0500
Subject: [bgmp] I-D ACTION:draft-ietf-bgmp-spec-06.txt
Sender: bgmp-admin@ietf.org
Errors-To: bgmp-admin@ietf.org
X-BeenThere: bgmp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bgmp>, <mailto:bgmp-request@ietf.org?subject=unsubscribe>
List-Id: Border Gateway Multicast Protocol <bgmp.ietf.org>
List-Post: <mailto:bgmp@ietf.org>
List-Help: <mailto:bgmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bgmp>, <mailto:bgmp-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60

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:
http://www.ietf.org/internet-drafts/draft-ietf-bgmp-spec-06.txt

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
	"get draft-ietf-bgmp-spec-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-bgmp-spec-06.txt".
	
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
Internet-Draft.
ftp://ftp.ietf.org/internet-drafts/draft-ietf-bgmp-spec-06.txt"><ftp://ftp.ietf.org/internet-drafts/draft-ietf-bgmp-spec-06.txt>