Document Action: 'Border Gateway Multicast Protocol (BGMP): Protocol Specification' to Informational RFC
The IESG <iesg-secretary@ietf.org> Wed, 16 June 2004 13:56 UTC
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27293 for <ietf-announce-archive@ietf.org>; Wed, 16 Jun 2004 09:56:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BaatU-0003Av-Eh for ietf-announce-archive@ietf.org; Wed, 16 Jun 2004 09:56:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BaUmv-0002V9-00 for ietf-announce-archive@ietf.org; Wed, 16 Jun 2004 03:24:50 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1BaTy9-0001nK-00; Wed, 16 Jun 2004 02:32:21 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BaTtg-0000PT-R6; Wed, 16 Jun 2004 02:27:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BaSlt-000105-N3 for ietf-announce@megatron.ietf.org; Wed, 16 Jun 2004 01:15:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA24325 for <ietf-announce@ietf.org>; Wed, 16 Jun 2004 01:15:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BaSlr-0004p9-K1 for ietf-announce@ietf.org; Wed, 16 Jun 2004 01:15:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BaOpX-0000U1-00 for ietf-announce@ietf.org; Tue, 15 Jun 2004 21:03:07 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BaLQ8-0006zv-00; Tue, 15 Jun 2004 17:24:40 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by mx2.foretec.com with esmtp (Exim 4.24) id 1BaLQ8-00048b-77; Tue, 15 Jun 2004 17:24:40 -0400
Received: from apache by megatron.ietf.org with local (Exim 4.32) id 1BaLL6-0004Ct-Q5; Tue, 15 Jun 2004 17:19:28 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1BaLL6-0004Ct-Q5@megatron.ietf.org>
Date: Tue, 15 Jun 2004 17:19:28 -0400
Cc: bgmp mailing list <bgmp@ietf.org>, bgmp chair <bcain@mediaone.net>, bgmp@ietf-mx.cnri.reston.va.us, chair <jhall@maoz.com>, bgmp chair <fenner@research.att.com>, Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: Document Action: 'Border Gateway Multicast Protocol (BGMP): Protocol Specification' to Informational RFC
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
The IESG has approved the following document: - 'Border Gateway Multicast Protocol (BGMP): Protocol Specification ' <draft-ietf-bgmp-spec-06.txt> as an Informational RFC This document is the product of the Border Gateway Multicast Protocol Working Group. The IESG contact persons are Alex Zinin and Bill Fenner. Technical Summary 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 multicast address 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. Working Group Summary The community didn't have enough motivation to invest enough cycles in finishing the work on this protocol or its implementation. This document would be an archival snapshot of the work. Protocol Quality The specification was reviewed for IESG by Alex Zinin. RFC Editor Note: In section 10, in the second paragraph under the heading "OpenSent state:" OLD If the value of the Autonomous System field is the same as the local Autonomous System number NEW If the configured remote Autonomous System value for this peering is the same as the local Autonomous System number _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce