draft-ietf-mboned-pruning-01.txt   draft-ietf-mboned-pruning-02.txt 
INTERNET-DRAFT J. Hawkinson INTERNET-DRAFT J. Hawkinson
draft-ietf-mboned-pruning-01.txt BBN Planet draft-ietf-mboned-pruning-02.txt BBN Planet
Category: Best Current Practice 10 September 1996 Category: Best Current Practice 30 July 1997
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 a Best Current Practice for the Internet
Internet Community, and requests discussion and suggestions for Community, and requests discussion and suggestions for improvements.
improvements. Distribution of this memo is unlimited. Distribution of this memo is unlimited.
Internet Drafts Internet Drafts
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
skipping to change at page 1, line 35 skipping to change at page 1, line 34
material or to cite them other than as ``work in progress.'' material or to cite them other than as ``work in progress.''
To learn the current status of any Internet-Draft, please check the To learn the current status of any Internet-Draft, please check the
``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
ftp.isi.edu (US West Coast). ftp.isi.edu (US West Coast).
Abstract Abstract
This document mandates that the MBone will be free of non-pruning This document calls for the MBone to be free of non-pruning multicast
multicast implementations by 31 October 1996. as soon as possible, due to the high cost to the Internet of the
traffic resulting from them. Consensus is that [DATE 1 month from RFC
publication] is the goal date for elimating non-pruning multicast
routers.
It is a product of the Multicast Deployment Working Group in the It cites several ways to eliminate non-pruning multicast from a
network, allowing per-site flexibility.
This is a product of the Multicast Deployment Working Group in the
Operational Requirements area of the Internet Engineering Task Force. Operational Requirements area of the Internet Engineering Task Force.
Submit comments to <mboned@ns.uoregon.edu> or the author. Submit comments to <mboned@ns.uoregon.edu> or the author.
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
Expires 30 February 1998 INTERNET-DRAFT 30 July 1997
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 10 September 1996
group. Network paths between each source and each non-pruning router group. Network paths between each source and each non-pruning router
are thus forced to carry all multicast traffic from those sources. are thus forced to carry all multicast traffic from those sources.
This 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 [DATE], the MBone community will no longer accept such
such non-pruning implementations as a part of the MBone. 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). Bay Networks' implementation supports pruning in respectively). Bay Networks' implementation supports pruning in
version 9.00 and up. version 9.00 and up.
In the case where the existing infrastructure cannot be upgraded to
support pruning, sites may wish to consider deploying lightweight
multicast routers instead. For instance, popular free unixes (e.g.
FreeBSD, NetBSD, and Linux) that run on cheap PC hardware all support
pruning multicast using mrouted.
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.
References References
[IPMULTI] S.E. Deering, "Host extensions for IP multicasting", RFC1112, [IPMULTI] S.E. Deering, "Host extensions for IP multicasting", RFC1112,
1 August 1989. 1 August 1989.
[MREQ] R. Braudes, S. Zabele, "Requirements for Multicast Protocols", [MREQ] R. Braudes, S. Zabele, "Requirements for Multicast Protocols",
RFC1458, 26 May 1993. RFC1458, 26 May 1993.
Expires 30 February 1998 INTERNET-DRAFT 30 July 1997
[DVMRP] T. Pusateri, "Distance Vector Multicast Routing Protocol", [DVMRP] T. Pusateri, "Distance Vector Multicast Routing Protocol",
Work in progress (internet-draft). Work in progress (internet-draft).
Author's Address Author's Address
John Hawkinson John Hawkinson
BBN Planet BBN Planet
150 CambridgePark Drive 150 CambridgePark Drive
Cambridge, MA 02140 Cambridge, MA 02140
 End of changes. 

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