1 / 7

Unraveling Flow: Data-Driven Swarm Tactics in Network Evolution

Delve into the transformation of CDN evolution by dissecting flows over multipath, sourcing traffic in swarms, and addressing flow unit aggregation challenges. Explore the impact on edge rate adjustment and reliability mechanisms in this stimulating discourse.

hgaddis
Download Presentation

Unraveling Flow: Data-Driven Swarm Tactics in Network Evolution

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Undiscombobulating Un-Flows. Jon Crowcroft, University of Cambridge Currently IMDEA Networks. Jon.Crowcroft@cl.cam.ac.uk http://www.cl.cam.ac.uk/~jac22 @Snagstuhl

  2. Cdn v. swarm – matrix?

  3. What’s a Flow? • The idea of flow is being undone • We’re splitting flows over multipath • We’re sourcing traffic in swarms • At a point in the net, how do you tell? • Guilt by association used to be possible • C.f. ASM – Any Source Multicast • Flow ID was group address + Dst Port • Need to recover this identity • Eg. so net (re-)feedback works • Need to work out what appropriate rate is.

  4. Data Driven Demands • Next step in evolution of CDN • Is to make the swarm a building block • Still have higher level identifiers • Meta-data, pub/sub/interest etc • But no lower level id • Does statistical mux/drop in queue + • Rate adjustment at edge • Still add up to a sensible behaviour? • And what is the rate adjustment • Given there’s more than one edge?

  5. Lets dream we had ASM still • Could assign marks to a swarm • Based on group • Each receiver could assign weight to feedback • And each source could adjust aggregate rate to group to meet fair/efficient goal • Question 1: Does this new “flow unit” still aggregate the right way? • Question 2: does it still improve over multipath • Question 3: mech. Do mechanisms to assign flows to multipath subpaths still apply to this new type of flow unit

  6. Some more small nits • How to do reliability (recall srm) • We do now have fec and netcoding as first class building blocks…so maybe ok • But in the presence of packet drop as a CC feedback signal… • …fec level to add isn’t totally obvious

  7. Questions? • Just to make matters worse, • All the flows are short lived.

More Related