1 / 8

Self-Configuring Protocols: A UDT Case Study

Self-Configuring Protocols: A UDT Case Study. Panagis Magdalinos Eleni Patouni Nikos Andriopoulos and Nancy Alonistioti {panagis,elenip,nand, nancy}@di.uoa.gr University of Athens. Design Assumptions for Component-based Framework. Dynamic composition of protocol layers to form a

tefrain
Télécharger la présentation

Self-Configuring Protocols: A UDT Case Study

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. Self-Configuring Protocols: A UDT Case Study Panagis Magdalinos Eleni Patouni Nikos Andriopoulos and Nancy Alonistioti {panagis,elenip,nand, nancy}@di.uoa.gr University of Athens

  2. Design Assumptions for Component-based Framework • Dynamic composition of protocol layers to form a • protocol stack • Dynamic composition of component services in fully- • fledged protocol service • Dynamic runtime modification of the protocol stack. • Dynamic replacement of the functionality of concrete protocol layers • Dynamic replacement of distinct protocol components within these protocols. • Reliable and transparent reconfiguration execution • No loss of existing connections and data, • Minimum performance overhead

  3. Dynamic Configuration of Autonomic Protocol Components • Dynamic Binding of Autonomic Protocol Components

  4. Dynamic Configuration of Autonomic Protocol Components • Dynamic Replacement of Autonomic Protocol Components

  5. UDT Case Study • UDT is an application level data transport protocol for the emerging distributed data intensive applications over wide area high-speed networks (e.g., 1 Gb/s or above). • UDT uses UDP to transfer bulk data and it has its own reliability control and congestion control mechanism. This new protocol is not only for private or QoS-enabled links, but also for shared networks. • UDT is also a composable framework that can accommodate various congestion control algorithms. • UDT reliability and congestion control mechanisms exist entirely in user space (not kernel space) and thus protocol variables are accessible at run time. • UDT protocol configuration (congestion control algorithm selection) can only be done at compile time.

  6. UDT/CCC Architecture Figure 1. UDT/CCC Architecture In this layered architecture,the UDT layer is completely in user space above the networktransport layer of UDP, whereas the UDT layer itself providestransport for applications. Meanwhile, applications provideoptional control handlers to UDT as callbacks.

  7. Future Work • Check the possibility of incorporating the framework for dynamic binding and replacement of autonomic components with the UDT protocol. • Modify the congestion control part. • Three Possible Stages of Integration: • Identification of possible protocol components: a generic UDT component and the congestion control component • Dynamic Binding of protocol components • Dynamic replacement of protocol components during runtime operation and not at compile time. • Possible Demonstration Scenario: in a network/terminal initiated scenario, the congestion control component is dynamically replaced during runtime operation of the UDT protocol.

  8. Thank you!

More Related