[pim] Re: I-D Action: draft-ietf-pim-multicast-lessons-lea rned-06.txt

Agree.

Dino

> On Nov 3, 2025, at 12:48 AM, Leonard Giuliano <[email protected]> wrote:
> 
> 
> Indeed, this is actually a side benefit of RPF- the source can influence 
> the path the traffic takes through the network by the way it advertises 
> it's own reachability in BGP.  While source-routing is fashionable these 
> days for unicast (SR/SRv6), multicast has always had this capability.
> 
> -Lenny
> 
> On Sat, 18 Oct 2025, Dino Farinacci wrote:
> 
> | 
> | > Aside from traffic engineering optimizations, ISPs as much as possible do “hot-potato” routing which tries to get the packet off their network as soon as possible. In contrast, multicast turns that on its head and causes “cold-potato” routing where the packet stays on the ISPs network as far as possible before exiting, thus sucking resources.
> | 
> | You can say this with absolute certainty since it depends on the reverse paths which are typically asymmetric. And if using MBGP routes, you can control the join-path. The join-path could be the shortest AS path from a joiner to source argubly providing a "hot potato branch" of the distribution tree.
> | 
> | Dino
> | 
> | _______________________________________________
> | pim mailing list -- [email protected]
> | To unsubscribe send an email to [email protected]
> |

_______________________________________________
pim mailing list -- [email protected]
To unsubscribe send an email to [email protected]