Telefon | +49 7071 29-70575 I work from home sometimes. Please send me an email when you can't reach me on the phone. |
benjamin.steinert @uni-tuebingen.de | |
Raum | B307 |
Anschrift | Lehrstuhl für Kommunikationsnetze Universität Tübingen Wilhelm-Schickard-Institut für Informatik Sand 13, 72076 Tübingen |
I'm a researcher and PhD student at the Chair of Communication Networks at the University of Tübingen. From 2014 to 2018 I studied Cognitive Science (B.Sc.) at the University of Tübingen. Afterwards, I changed my focus to Computer Science (M.Sc.) where I'm currently graduating in, also at the University of Tübingen.
2014 - 2018
B.Sc. Cognitive Science
Graduated at the Eberhard Karls University of Tübingen on 30.05.2018
2018-2021
M.Sc. Computer Science
Currently graduating at the Eberhard Karls University of Tübingen
2020 - today
Research Assistant
Researcher and PhD student at the Chair of Communication Networks at University of Tübingen
Research Interests
Software-Defined Networking
Network management is complex and error-prone. Software-Defined Networking (SDN) aims to eliminate maintenance processes and to provide simple network management. This is done by allowing explicit and centralized control over the networking devices. Benefits of SDN over classical networking include programmability, centralized control, network flexibility, improved performance, easy implementation, efficient configuration, and enhanced management.
P4: Programming Protocol-Independent Packet Processors
P4 is a domain-specific language for programming protocol-independent packet processors. With P4, the data plane functionality of forwarding devices such as routers and switches is not fixed, but can be specified programmatically. Custom headers and protocols can be declared in a P4 program together with a description of the forwarding behavior based on match+action tables. Thereby the P4 language is target-independent which means that a P4 program can be compiled for very different types of software and hardware, called P4 targets.
Network Function Virtualization
Network Functions (NFs) process network traffic and thereby provide functionality that is vital for today’s distributed networks. Examples are DPI, firewalls, load balancing or NATs. Packets traverse these functions in order to be monitored, analyzed, filtered, or processed otherwise. Traditionally, these NFs are supplied as hardware appliances that are manually set up by network operators. This involves manual configuration and wiring of the appliances. Network Function Virtualization aims to move the functionality from hardware appliances to software that can be run on COTS hardware.
Service Function Chaining
The process of chaining virtual service functions requires the configuration, deployment, and interconnection of the respective network function instances. The resulting ordered set of service functions is called a service function chain. Research in Service Function Chaining (SFC) aims to automate the process of provisioning network services as virtual service function chains.