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

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/