Virtual Internet Backbone for Mult
ICast IP.
IP-MultICast is the
class-D addressing scheme in
IP implemented by Steve Deering at
Xerox PARC. It was adopted at the
IETF March 1992 meeting and acquired the name MBONE after the July 1992 IETF meeting. IP Mult
ICast-based routing allows distributed appl
ICations to achieve
real-time commun
ICation over
IP {wide area network}s through a lightweight, highly {thread}ed model of commun
ICation. Each network-provider part
ICipant in the MBONE provides one or more IP mult
ICast routers to connect with tunnels to other part
ICipants and to customers. The mult
ICast routers are typ
ICally separate from a network' s production routers since most production routers don' t yet support IP mult
ICast. Most sites use workstations running the mrouted program, but the experimental MOSPF software for Proteon routers is an alternative. It is best if the workstations can be ded
ICated to the mult
ICast routing function to avoid interference from other activities and so there will be no qualms about installing kernel patches or new code releases on short not
ICe. Since most MBONE nodes other than endpoints will have at least three tunnels, and each tunnel carries a separate (un
ICast) copy of each packet, it is also useful, though not required, to have multiple network interfaces on the workstation so it can be installed parallel to the un
ICast router for those sites with configurations like this: +----------+ | Backbone | | Node | +----------+ | ------------------------------------------ External DMZ Ethernet | | +----------+ +----------+ | Router | | mrouted | +----------+ +----------+ | | ------------------------------------------ Internal DMZ Ethernet This configuration allows the mrouted machine to connect with tunnels to other regional networks over the external
DMZ and the phys
ICal backbone network, and connect with tunnels to the lower-level mrouted machines over the internal
DMZ, thereby splitting the load of the repl
ICated packets. The mrouted machine would not do any un
ICast forwarding. Note that end-user sites may part
ICipate with as little as one workstation that runs the packet audio and video software and has a tunnel to a network-provider node.
RFC 1112 gives the details.
FAQ . (1994-11-11)
In addition suitable contents:
[ 2 ] [ = ] [ ad ] [ address ] [ af ] [ ai ] [ al ] [ alt ] [ am ] [ an ] [ app ] [ applICation ] [ ar ] [ ARC ] [ arc ] [ as ] [ at ] [ au ] [ audio ] [ av ] [ B ] [ b ] [ ba ] [ backbone ] [ base ] [ be ] [ bo ] [ bon ] [ by ] [ C ] [ ca ] [ cast ] [ cat ] [ ch ] [ ci ] [ ck ] [ cl ] [ class ] [ co ] [ code ] [ com ] [ con ] [ connect ] [ cu ] [ D ] [ dd ] [ de ] [ ding ] [ DMZ ] [ do ] [ du ] [ E ] [ ec ] [ ed ] [ ee ] [ eg ] [ end-user ] [ er ] [ es ] [ ET ] [ et ] [ Ethernet ] [ FAQ ] [ FC ] [ fi ] [ file ] [ fo ] [ for ] [ forward ] [ fr ] [ function ] [ gh ] [ gi ] [ gr ] [ gu ] [ h ] [ hat ] [ hose ] [ hr ] [ ht ] [ id ] [ IE ] [ ie ] [ IETF ] [ il ] [ in ] [ inc ] [ int ] [ interface ] [ Internet ] [ io ] [ IP ] [ ir ] [ is ] [ it ] [ J ] [ ke ] [ kernel ] [ la ] [ ld ] [ Lex ] [ li ] [ like this ] [ load ] [ ls ] [ lt ] [ ly ] [ M ] [ ma ] [ machine ] [ MB ] [ ml ] [ mm ] [ mo ] [ mod ] [ mode ] [ model ] [ module ] [ MOS ] [ mp ] [ mr ] [ ms ] [ Mu ] [ mu ] [ MZ ] [ N ] [ na ] [ nc ] [ ne ] [ net ] [ network ] [ nf ] [ ng ] [ ni ] [ nn ] [ no ] [ node ] [ ns ] [ O ] [ om ] [ op ] [ OS ] [ OSP ] [ OSPF ] [ pa ] [ packet ] [ PARC ] [ pe ] [ ph ] [ physICal ] [ pl ] [ point ] [ port ] [ pr ] [ product ] [ program ] [ provider ] [ pt ] [ py ] [ Q ] [ query ] [ rc ] [ re ] [ real ] [ real-time ] [ regional network ] [ release ] [ RFC ] [ RFC 1112 ] [ ro ] [ route ] [ routed ] [ router ] [ routing ] [ ru ] [ run ] [ rw ] [ S ] [ sc ] [ se ] [ sh ] [ si ] [ sit ] [ so ] [ software ] [ SP ] [ split ] [ st ] [ su ] [ support ] [ T ] [ tc ] [ th ] [ thread ] [ tm ] [ to ] [ tp ] [ tr ] [ tt ] [ tw ] [ ua ] [ ug ] [ up ] [ us ] [ user ] [ V ] [ ve ] [ vi ] [ workstation ] [ ws ] [ X ] [ ye ] [ Z ]