Protocol Action: 'IGMP/MLD-based Multicast Forwarding ('IGMP/MLD Proxying')' to Proposed Standard
The IESG <iesg-secretary@ietf.org> Tue, 01 June 2004 16:54 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 MAA24980 for <ietf-announce-archive@ietf.org>; Tue, 1 Jun 2004 12:54:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BVCWm-0003Cn-Q8 for ietf-announce-archive@ietf.org; Tue, 01 Jun 2004 12:54:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BVCSH-0001t3-00 for ietf-announce-archive@ietf.org; Tue, 01 Jun 2004 12:49:38 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1BVCNL-0000Gd-00; Tue, 01 Jun 2004 12:44:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVBES-0004L0-Lu; Tue, 01 Jun 2004 11:31:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BTpo8-0003Ll-JC for ietf-announce@megatron.ietf.org; Fri, 28 May 2004 18:26:32 -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 SAA14054 for <ietf-announce@ietf.org>; Fri, 28 May 2004 18:26:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BTpo7-0001KY-4j for ietf-announce@ietf.org; Fri, 28 May 2004 18:26:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BTpn9-0000uV-00 for ietf-announce@ietf.org; Fri, 28 May 2004 18:25:32 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1BTpmJ-0000RX-00; Fri, 28 May 2004 18:24:39 -0400
Received: from apache by megatron.ietf.org with local (Exim 4.32) id 1BTpXF-00050H-6l; Fri, 28 May 2004 18:09:05 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Message-Id: <E1BTpXF-00050H-6l@megatron.ietf.org>
Date: Fri, 28 May 2004 18:09:05 -0400
X-Mailman-Approved-At: Tue, 01 Jun 2004 11:30:55 -0400
Cc: magma mailing list <magma@ietf.org>, magma chair <brian@innovationslab.net>, Internet Architecture Board <iab@iab.org>, magma chair <kouvelas@cisco.com>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: Protocol Action: 'IGMP/MLD-based Multicast Forwarding ('IGMP/MLD Proxying')' to Proposed Standard
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:
- 'IGMP/MLD-based Multicast Forwarding ('IGMP/MLD Proxying') '
<draft-ietf-magma-igmp-proxy-06.txt> as a Proposed Standard
This document is the product of the Multicast & Anycast Group
Membership Working Group.
The IESG contact persons are Margaret Wasserman and Thomas Narten.
Technical Summary
In certain topologies, it is not necessary to run a multicast routing
protocol. It is sufficient for a device to learn and proxy group
membership information and simply forward multicast packets based
upon that information. This draft describes a mechanism for
forwarding based solely upon Internet Group Management Protocol
(IGMP) or Multicast Listener Discovery (MLD) membership information.
Working Group Summary
This document is a work item of the MAGMA WG.
There is a discussion in the draft about the inability of the IGMP proxy
mechanism defined in this draft to detect "upstream loops", and it is
expected that administrators will either avoid configuring their networks
in loops or run a multicast routing protocol. This issue was discussed
within the MAGMA WG, and the WG did not choose to include any
mechanism (i.e. probes) for loop detection.
The WG chose to use the Querier Election mechanism described in the
draft to ensure that there will only be a single forwarder if there is more
than one proxy device on the same link, but this will not eliminate the
possibility of all types of loops, see section 3.0 of the draft for more
details about this.
Protocol Quality
This document was reviewed for the IESG by Margaret Wasserman.
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce