Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Liu, G. and L. Wei, "Protocol Independent Multicast (PIM): Motivation and Architecture", Work in Progress.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....protocol to allow for point to multipoint connections to group addresses, since the P NNI protocols will then need to generate a source rooted tree linking the source to each of the leaves. Such a protocol may build upon such existing multicast protocols as Protocol Independent Multicast (PIM) [Deering2]. 4.5 Public Network Internetworking One area in both the P NNI Phase 1 and IISP protocols that is still not fully specified is that of public network internetworking. The interconnection of private ATM networks across public ATM networks poses particular challenges because of the current lack of ....

....and NNI signaling play with respect to cell flows. RSVP is fundamentally built upon a multicast paradigm, and routes traffic flows along source rooted point to multipoint paths (with unicast handled as a special case of multicast) New multicast protocols like Protocol Independent Multicast (PIM) [Deering2], and their associated unicast packet routing protocols, will hence be closely coupled with RSVP, much as VC routing protocols are closely coupled with UNI and NNI signaling. Such protocols rely upon a flow specification [Partridge2] to characterize the expected traffic patterns for a stream of IP ....

[Article contains additional citation context not shown here]

Deering, S., et al.---"Protocol Independent Multicast (PIM): Motivation and Architecture," Internet Draft, January 1995.

....consistency is needed. Message delivery is not reliable and all the members of the group must be active to receive an update, because the distribution is done directly by the producer of the object. Multicast routing algorithms (e.g. CBT [Ballardie 93] DVMRP [Waitzman 88] MOSPF [Moy 94] PIM [Deering 96] etc. may be studied separately from the use of IP multicast. As ours is an application level problem it is not right to depend on the network level to solve it. Our proposal is to adapt routing techniques used on network level to application level. 3.1 Object Distribution Network (ODN) We ....

Deering, S.; Estrin, D.; Farinacci, D.; Jacobson, V., Liu, C., Wei, L. "Protocol Independent Multicast (PIM): Motivation and Architecture". <draft-ietf-idmr-pim-arch04. ps>. September 1996.

....truncated data packet broadcasts to all network routers that might serve group members and MOSPF, because it is a link state protocol, requires the entire network topology to be known at all routers. To overcome these problems, an algorithm termed Protocol Independent Multicast (PIM) [20] was introduced. PIM is distributed and may operate in either dense or sparse mode. Dense mode operation is similar to the data driven functioning of DVMRP and is restricted to intra Reservation Based Multicast 4 domain multicast for locally dense groups. While users may opt for this dense ....

....their information to a core router which then distributes the information over the tree to all receivers. The protocol requires less state overhead than PIM since only a single tree per group is built, as opposed to the potential for numerous source specific trees in PIM. However, it is noted in [20] that CBT may suffer from a traffic concentration problem, particularly if there is a large number of sources, as all the source traffic must travel on the shared tree which might congest the links and reduce performance. Source specific trees are advantageous in that (i) the traffic is ....

S. Deering, D. Estrin, D. Farinacci, V. Jacobson, C.-g. Liu, and L. Wei, "Protocol Independent Multicast (PIM): Motivation and Architecture," Internet Draft, January, 1995.

....However, this is an inelegant solution and requires co operation at both ends of the ISDN connection. What is required is for an explicit graft soft state rather than explicit prune soft state. Such a solution may be offered by the sparse mode model of the Protocol Independent Multicast (PIM) [17] approach. 5.3 An experimental set up The UPI is not multicast aware, so we must provide the multicast routing to the remote ISDN home teleworkers by the use of multicast tunnels. These use IP in IP encapsulation, wrapping the multicast packet up in a unicast packet to traverse the tunnel. ....

S. Deering, D. Estrin, D. Farinacci, V. Jacobson, C. Liu, L. Wei, "Protocol Independent Multicast (PIM): Motivation and Architecture", Work In Progress, InternetDraft (draft-ietf-idmr-pim-arh-01.ps) Jan 1995

....that can directly support IP multicast (such as ethernet LANs) linked by virtual point topoint links called tunnels . More recently, several vendors have supplied native IP multicast routing protocols. Multicast routing information was distributed using PIM (Protocol Independent Multicast) [16,17] Desktop video delivery was initially accomplished via the MBONE tool nv , with later migration to a newer video tool called vic which supported not only nv but also other video encodings and standards such as H.261 and JPEG. MBONE has been routinely used for some time to broadcast various ....

S. Deering, D. Estrin, D. Farinacci, V. Jacobson, C. Liu, and L. Wei. "Protocol Independent Multicast (PIM): Motivation and Architecture", Internet Draft, draftietf -idmr-pim-arch-00.txt, November 1994.

....protocol to allow for point to multipoint connections to group addresses, since the P NNI protocols will then need to generate a source rooted tree linking the source to each of the leaves. Such a protocol may build upon such existing multicast protocols as Protocol Independent Multicast (PIM) [Deering2]. 4.5 Public Network Internetworking One area in both the P NNI Phase 1 and IISP protocols that is still not fully specified is that of public network internetworking. The interconnection of private ATM networks across public ATM networks poses particular challenges because of the current lack ....

....and NNI signaling play with respect to cell flows. RSVP is fundamentally built upon a multicast paradigm, and routes traffic flows along source rooted point to multipoint paths (with unicast handled as a special case of multicast) New multicast protocols like Protocol Independent Multicast (PIM) [Deering2], and their associated unicast packet routing protocols, will hence be closely coupled with RSVP, much as VC routing protocols are closely coupled with UNI and NNI signaling. Such protocols rely upon a flow specification [Partridge2] to characterize the expected traffic patterns for a stream of IP ....

[Article contains additional citation context not shown here]

Deering, S., et al---"Protocol Independent Multicast (PIM): Motivation and Architecture," Internet Draft, January 1995.

....path is a routeing problem. A choice of routeing architecture is however a tradeoff between the ease of group management control and data cost. Different routeing architectures such as shared tree or source based tree each have their merit. Recent developments in the Internet community on the PIM[6] multicast architecture have further emphasised the importance of support for both tree types. One important characteristic of our multicast architecture is the support of both the shared tree and source based tree, with the use of the MC 2 . A multipointto multipoint group can either be ....

S. Deering, D. Estrin, D. Farinacci, V. Jacobson, C. Liu, and L. Wei, "Protocol Independent Multicast (PIM): Motivation and Architecture," Proc. ACM Sigcomm, August 1994.

....consistency is needed. Message delivery is not reliable and all the members of the group must be active to receive an update, because the distribution is done directly by the producer of the object. Multicast routing algorithms (e.g. CBT [Ballardie 93] DVMRP [Waitzman 88] MOSPF [Moy 94] PIM [Deering 96] etc. may be studied separately from the use of IP multicast. As ours is an application level problem it is not right to depend on the network level to solve it. Our proposal is to adapt routing techniques used on network level to application level. Networks have a physical and a logical ....

Deering, S.; Estrin, D.; Farinacci, D.; Jacobson, V., Liu, C., Wei, L. "Protocol Independent Multicast (PIM): Motivation and Architecture". <draft-ietf-idmr-pim-arch-04.ps>. September 1996.

....updates. The convergence times are not presented here because our definition of convergence time does not apply to sparse events, which seldom conflict with each other. 5 Related Work Multicast protocols have made significant progress in recent years, primarily in the Internet community [2, 3, 14, 15, 16] and for ATM networks [5, 7] In 1 2 3 4 5 6 7 8 50 150 250 350 Proposals per event Network Size average upper bound lower bound (a) proposals per event. 0.6 0.8 1 1.2 1.4 1.6 1.8 2 2.2 2.4 50 150 250 350 Flooding operations per event Network size average upper bound lower bound (b) floodings ....

S. Deering, D. Estrin, D. Farinacci, V. Jacobson, C. gung Liu, and L. Wei, "Protocol independent multicast (PIM): Motivation and architecture." Internet Draft draft-ietf-idmr-pim-arch-01.ps, January 1995.

....work. We re emphasize that the SAF protocols are independent of the particular SMC protocol used. Although we presented a specific SMC protocol in this paper, general purpose MC protocols can also be used adapted to construct spanning MCs. Examples include the CBT protocol [23] the PIM protocol [24], the C GMC protocol [11] and the D GMC protocol [10] The SMC protocol, a variation to the CBT protocol, has an advantage in automatic and dynamic core selection. Moreover, all of the above alternatives invoke some form of MC membership management, a task that is unnecessary for spanning MCs. In ....

S. Deering, D. Estrin, D. Farinacci, V. Jacobson, C. Liu, and L. Wei, "Protocol independent multicast (PIM): Motivation and architecture." Internet Draft draft-ietf-idmr-pim-arch-01.ps, January 1995.

No context found.

Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Liu, G. and L. Wei, "Protocol Independent Multicast (PIM): Motivation and Architecture", Work in Progress.

No context found.

Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Liu, C., Wei, L., Sharma, P., and A. Helmy, "Protocol Independent Multicast (pim): Motivation and Architecture", Work in Progress.

No context found.

D. Estrin, D. Farinacci, A. Helmy, D. Thaler, S. Deering, V. Jacobson, M. Handley, C. Liu, P. Sharma, L. Wei, "Protocol Independent Multicast (PIM): Motivation and Architecture", Proposed RFC, Oct 96.

No context found.

S. Deering, D. Estrin, D. Farinacci, V. Jacobson, C. Liu, and L. Wei, "Protocol Independent Multicast (PIM): Motivation and Architecture," Work in Progress (Internet Draft draftietf -idmr-pim-arch-00.ps), March 1994.

No context found.

S. Deering, D. Estrin, et al. "Protocol Independent Multicast (PIM): Motivation and Architecture". Internet Draft, January 1995.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC