--- 1/draft-ietf-mboned-pruning-00.txt 2006-02-05 00:20:48.000000000 +0100 +++ 2/draft-ietf-mboned-pruning-01.txt 2006-02-05 00:20:48.000000000 +0100 @@ -1,14 +1,14 @@ INTERNET-DRAFT J. Hawkinson -draft-ietf-mboned-pruning-00.txt BBN Planet -Category: Best Current Practice 09 August 1996 +draft-ietf-mboned-pruning-01.txt BBN Planet +Category: Best Current Practice 10 September 1996 Multicast pruning a necessity Status of this Memo This document specifies an Internet Best Current Practice for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited. Internet Drafts @@ -41,38 +41,39 @@ Discussion The MBone (Multicast Backbone) of the Internet is composed of a DVMRP backbone connected to regions that may be running other multicast routing protocols. DVMRP versions prior to 3 do not support pruning. Every multicast packet transmitted is delivered to every non-pruning router (subject to scoping rules), regardless of the presence of members of that -Expires 31 September 1996 INTERNET-DRAFT 09 August 1996 +Expires 31 September 1996 INTERNET-DRAFT 10 September 1996 - group. Network paths been each source and each non-pruning router are - thus forced to carry all multicast traffic from those sources. This - behavior is fundamentally incompatible with a scalable multicast + group. Network paths between each source and each non-pruning router + are thus forced to carry all multicast traffic from those sources. + This behavior is fundamentally incompatible with a scalable multicast backbone. Effective 31 October 1996, the MBone community will no longer accept such non-pruning implementations as a part of the MBone. Such implementations should be upgraded or disconnected from the MBone prior to that date. Service providers should assist their customers in these processes. DVMRP implementations that do not support pruning include mrouted versions prior to 3, and Cisco Systems IOS prior to version 11.0(3). 3Com's NETBuilder routers and LANplex switches have supported pruning as long as DVMRP has been available for them (releases 8.3 and 7.0, - respectively). + respectively). Bay Networks' implementation supports pruning in + version 9.00 and up. Within non-DVMRP regions, software that does not support DVMRP pruning but does support a similar mechanism of a different protocol (such as CBT, MOSPF, or PIM) is acceptable, as long as the border routers of such a region can translate that mechansism into DVMRP pruning. Security Considerations Security considerations are not addressed in this memo.